Have to rebind wltoys v2xx everytime?

Recently updated to 4.0.1 but noticed that I'm having to rebind to my wltoys v2** quads whenever I power off either the quads or the tx, Don't remember it behaving like this before so what's changed or am I just remembering wrong

Personally, I have a WLToys v252 micro quad and I have always had to manually re-bind every single time. I was using a nightly build of 3.0.x I have just upgraded to v4.0.1 in the last day and still have to bind manually every time to the v252. I just create a shortcut key in the model settings to get me there quicker.

It's been different with my Hubsan X4's since it will Auto-bind as soon as I turn on the transmitter which makes it nice and easy.

Shanman3us

From my experience w/ my devo 7e on release 4.0.1 and v252/JD385:
case 1) if I power off my micro quad and turn it back on, it will automatically bind to my devo 7e instantly without any problem.

case 2) if I power off my devo 7e and turn it back on, I will have to manually re-bind. And YES I also create a shortcut key with DN button to jump there.

case 3) if I power off my devo 7e and want to bind my v252/JD385 w/ ANOTHER devo remote, I need to turn off my micro quad as well.
Seems that the micro quad will remember the last binded remote and stick w/ it until power down.

Hope this helps!

I'll have to give your "Case 1)" a try. After flying my v252 I always switch to another quad to give the motors a chance to cool down making it so that I can fly back to back. I'll have to make a point of tying this on the bench to see if it works for me too.

Shanman3us

I experience similar results with my 252 & 202. I wouldn't mind it so much if one of the up/down buttons could be mapped to the "bind" function.

This was discussed earlier and rejected, because you might accidentally invoke the bind process and loose control over your heli / quad for some time.

Well it is bad UI. Having to click 5/8 times (1 long press, 4 down clicks or 7 up clicks) to access a common function is absurd. In er9x I can hold the trainer switch while turning the TX on and it engages the bind process. In Deviation a user performs a similar button sequence to enter USB mode (hold ent + power on tx). Clearly the firmware can handle detecting a button state upon tx power up. This button sequence would be impossible to "accidentally trigger" during flight.

I understand this functionality was already discussed, but was it proposed to use a button+power on combination?

If it was already rejected, then how can I patch or compile a build that uses exit+power to enter bind mode?

Do you have Fixed Id set for your model? And can you check V202 (I don't have V252), is it behaving the same way?

@Jefte: Exit + Power on enters the programming mode (for all tx but Devo12).
Some protocols do auto-binding with a fixed id set, some go to bind mode when the tx is powered on (of course depending on the model selected).
You should be able to select the wanted page as quickpage so you save some clicks.
It should be in general possible to detect a keypress when powering on the same way as it is done for USB mode. Some keys are free...

Fixed IDs on both.

Just today I struggled to get a friends 202 to bind. Three battery pulls later (and 27 clicks later) I realized his tx was still on. Ugh.

None of my 2xx series auto bind on power on. Nor do they persist bind through tx power offs.

So far the only complaint I have about Deviation is the v2xx binding procedure.

The capabilities of the firmware are amazing! And the quality and control of the Devo 10 is a vast improvement over the RTF stuff that came with my models. But it definitely seems like an oversight to have to go deep into model setup and then watch a countdown every time you want to bind. I presume most people have other models with fixed IDs and whatnot so they don't experience this as much. I have several v2xx models that I rotate between so the motors have a chance to cool. The 1 second procedure of power cycle and up/down throttle on the RTF remotes is their only redeeming quality.

Surely there must be a reasonable approach to dealing with any auto-bind safety concerns. It seems like throttle all the way down is enough, and some sort of quick key combo or moving the Bind option to the main menu.

I realize I am free to fork and make changes myself, but it seems like something of general applicability and appeal.

I am not comfortable with full throttle up as a binding gesture - what if you accidentally have a heli, bound and turned on? I can take a look into implementing another gesture, say throttle down and right - similar with MultiWii arming gesture.

Wow a gesture to bind without power cycling the tx, for all those micros that need to be bound each time the battery is changed.

Something that could be enabled at the model level would be really cool, this would beat the shortcut to model setup.

say throttle down and right - similar with MultiWii arming gesture

This has my vote.

Just about any approach is better than the current one

Agree that the throttle max is not a particularly clever gesture... not sure why the RTF units work that way.

Even without any special stick gestures it would be great just to have another shortcut option the same as the current one to model setup, but that navigates directly to "bind" already selected. That makes it a long press to get to the menu, and ENT to confirm binding.

I don't really understand the purpose of the countdown dialog, but there is obviously a reason given the effort put into it. I'm sure my perception is skewed by micro-sized models where the dangers are pretty trivial. Maybe imminent binding is a bigger deal on something huge. Still, 3 seconds seems a long time when you purposefully pushed the button and want the action to take place. For my sole Walkera model it was a 10s countdown, but at least it was a one-shot deal.

marcoose wrote: J
Even without any special stick gestures it would be great just to have another shortcut option the same as the current one to model setup, but that navigates directly to "bind" already selected. That makes it a long press to get to the menu, and ENT to confirm binding.

This is exactly what happens today, if and only if you don't power cycle the TX. As I always buy two same model, one flies while another is cooling it's less annoying for me.

i.e. if you bind your plane/helo, the bind button will stay selected. When you shortcut to it say LONG+Up (for the model menu) then you only have to press ENT to bind.

But if you cycle trough some models while you flying session, I can see how annoying it can be, to have to shortcut then 7 clicks, then bind.

My concern about the use of shortcut to bind is merely button fatigue, as I fly mostly micros, I fear that sometime soon I'll have to replace the micro-switch, not the time it takes to go to the bind button.

As in my opinion sticks are more resilient than the micro-switches, it would be a nice addition.

If someone don't propose this as an enhancement, I'll do it. We'll then see what PB thinks of it.

Wow, dumb of me not to catch that. I guess when switching models I have always powered off the TX to save some battery and as I fiddle with the tiny battery connectors on the next model and put the first out of harms way. I do have a couple Walkera models, but now that I know about this I'll be sure to sort everything by protocol in my rotation

I never really thought about the micro switches wearing out... but regardless a stick gesture would be even faster and requiring throttle off would be an added safety bonus. Given that it should be a pretty deliberate gesture, hopefully we can reduce or eliminate the binding countdown timer.

How do you manage to create the shortcut key? I have no idea.

mazi wrote: How do you manage to create the shortcut key? I have no idea.

Chapter 8.7 deviationtx.com/user-manual/user-manual-7e-10