- Posts: 65
- Forum
- News, Announcements and Feedback
- Feedback & Questions
- Can you force a 'RE-INIT" or "BIND" at startup?
Can you force a 'RE-INIT" or "BIND" at startup?
- John-Boy
- Topic Author
- Offline
Setting up my Devo 7e to run my old Walkera 4G3 and 4G6's. During this setup and refurbishing the heli's, I need to turn things on & off multiple times.
I have it setup with the standard GUI, and using the 2801 protocol. I have set the ID to none (the receivers cannot hold an ID) and RE-INIT everytime I power-up the heli.
So, is there a setting where I can power-up the heli, then turn on the 7e and have it do the RE_INIT on power-up without thumbing through all the menus?
Sure would save a bunch of time...
Thanks
John L.
Please Log in or Create an account to join the conversation.
- HappyHarry
- Offline
- Posts: 1136
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- linux-user
- Offline
- Posts: 271
John-Boy wrote: Hi All,
So, is there a setting where I can power-up the heli, then turn on the 7e
Hi John,
you should first turn on the 7e and then power-up the heli ALWAYS!
And switch off the other way.
Other ways there might happen nasty things. Imagine someone in your neighbourhood switching on a Transmitter just before you power on your heli.
Please Log in or Create an account to join the conversation.
- John-Boy
- Topic Author
- Offline
- Posts: 65
I can appreciate your concern, that's how the older Walkera worked... I wished I could find someone else with a Walkera to share heli's with....
Please Log in or Create an account to join the conversation.
- John-Boy
- Topic Author
- Offline
- Posts: 65
I have the 2801 protocol selected, id set to 'none' and it does not re-init on power-up.
To bind to properly, the heli has to be 'on' 1st and blinking, then select 're-init' on the radio, 2-4 seconds later the esc beeps and the unit connects, ready to fly.
Remember, these older Walkera recvrs do not store an id so they must bind every powerup.
Thanks
John L.
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
do you get the 'Binding model' dialog when you turn on your Tx?
Please Log in or Create an account to join the conversation.
- John-Boy
- Topic Author
- Offline
- Posts: 65
During power- up the standard Deviation splash comes up, not the Binding count-down screen I see if I do the 're-init'.
Thanks...
Please Log in or Create an account to join the conversation.
- rbe2012
- Offline
- So much to do, so little time...
- Posts: 1433
Please Log in or Create an account to join the conversation.
- John-Boy
- Topic Author
- Offline
- Posts: 65
I understand if either is powered down, bind is lost and the proceedure starts over...
Please Log in or Create an account to join the conversation.
- linux-user
- Offline
- Posts: 271
I just tried to reproduce this with my Devo10 V4.01
- Changed protocol to WK2801 or WK2601
- TX off
- TX on
Binding MiniCP ...
Press ENT to stop
8...7...6...5 seconds left
So the binding seems to start.
The only difference I could see to Devo protocol was, that there the countdown starts at 11 instead of 8
Please Log in or Create an account to join the conversation.
- John-Boy
- Topic Author
- Offline
- Posts: 65
Please Log in or Create an account to join the conversation.
- linux-user
- Offline
- Posts: 271
2.2 Upgrade Notes
Note for Devo7e owners only: For Devo7e users, there is an additional step that needs to
be completed every-time after installing the firmware. The firmware also includes a set
of ‘.mod’ files in the protocol directory. The entire protocol directory must be copied to
the transmitter. This must be done each time the firmware is upgraded, otherwise the
firmware will not work properly and an error message will appear when switching the
transmitter on.
Have you done this?
You must do this with the exact same files that came with your firmware - with every upgrade!
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- John-Boy
- Topic Author
- Offline
- Posts: 65
Please Log in or Create an account to join the conversation.
- HappyHarry
- Offline
- Posts: 1136
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- John-Boy
- Topic Author
- Offline
- Posts: 65
I also have a Devo 8 and tested it. It attempts to bind when powered-up just as it should. No problems there..
Thanks!
Please Log in or Create an account to join the conversation.
- HappyHarry
- Offline
- Posts: 1136
PhracturedBlue wrote: I think it has something to do with the stick-move code not playing well with the modules. The wk protocols are the only ones with stick-move abort, and I think this is likely where the bug lies. I haven't actually found the smoking gun yet though.
i've just tried the latest code (9686f9e) and it still doesn't bring up the bind screen on boot automatically for any of the WK* protocols,
i can make it happen with WK2601 and WK2401 if i hold the aileron stick hard (mode2) left and keep it there while powering on, but now to make it happen when choosing re-init in the menu i also have to hold the aileron stick hard left.
pressing the bind button in the menu for WK2801 still works as expected but no matter what i try it doesn't appear at power on time
Please Log in or Create an account to join the conversation.
- Forum
- News, Announcements and Feedback
- Feedback & Questions
- Can you force a 'RE-INIT" or "BIND" at startup?
- Home
- Forum
- News, Announcements and Feedback
- Feedback & Questions
- Can you force a 'RE-INIT" or "BIND" at startup?