Bug: Protocol change problem (from DSM2 to WK)

More
26 Jan 2013 19:19 - 26 Jan 2013 19:22 #5547 by Tom_ate
Hi,

I found a reproducable bug in DeViation with my Devo10:

Here is what I did:
- I flew a model with DSM2-protocoll and fixed ID.
- Than I changed to another model with WK-Protocoll (without fixed ID).
- Than the model does not bind.
- In that case only if you power off and then on again (both TX and Heli) than it works.
- also, if I flew a Devo- or another WK-Heli before changing to a WK-Heli, than it works (it only doesn't work wen "coming" from a DSM2-Heli)
- It is not necessary to really fly the DSM2-Heli before: Simply load a DSM2-Model and then load a WK-Model afterwards, than binding won't work.

Kind regards,

Matthias
Last edit: 26 Jan 2013 19:22 by Tom_ate.

Please Log in or Create an account to join the conversation.

More
26 Jan 2013 19:34 #5548 by sbstnp
Not sure that's bug. Both Devo and DSM use the same chip. That's why there is a Re-Init button on the model page.

Devo 10 + 4in1
Spektrum Dx9
FrSky Taranis + TBS Crossfire

Please Log in or Create an account to join the conversation.

More
27 Jan 2013 16:29 #5579 by RandMental
Replied by RandMental on topic Bug: Protocol change problem (from DSM2 to WK)
If we have a button to re-init after a protocol change, why not automate it and do it on every protocol change?

Please Log in or Create an account to join the conversation.

More
27 Jan 2013 16:43 #5580 by Tom_ate
There isn't a "re-init" Button if you are using the WK-Protocoll without Fixed ID - there is only a "bind" button.

And you can use that button as often as you like - it won't work until you power the TX completely off an on.

So I am quite sure it is a bug - because it works properly if you "come" from a devo-model (otherwise this shouldn't work either)

Kind regards,

Matthias

Please Log in or Create an account to join the conversation.

More
27 Jan 2013 17:17 - 27 Jan 2013 17:17 #5581 by domcars0
Replied by domcars0 on topic Bug: Protocol change problem (from DSM2 to WK)
Tom_ate is right.. I've just tested it :
A ) Bind my Nano CPX (DSMX)
B ) Change model to my 4#6S (WK240xProtocol).... binding failed ...
even "Reinit" does not bind...
I have to turn Off/On the TX to bind my 4#6S
This is a "small" bug.

Devo 10 (+7e) owner. It's mine, please don't touch it with your big fingers :angry:
Last edit: 27 Jan 2013 17:17 by domcars0.

Please Log in or Create an account to join the conversation.

More
27 Jan 2013 22:32 - 27 Jan 2013 22:33 #5592 by MikroHeliPilot
Replied by MikroHeliPilot on topic Bug: Protocol change problem (from DSM2 to WK)
I also can confirm this. Coming from DSM2 (Blade Nano CPx) there is no other way than powercycling to bind walkera 2401 (beloved 4#3b ;-)).

Not a big issue but worth fixing imho.

Regards,
MikroHeliPilot
Last edit: 27 Jan 2013 22:33 by MikroHeliPilot.

Please Log in or Create an account to join the conversation.

More
28 Jan 2013 14:14 #5618 by Tom_ate
As this is stated now to be a "real" bug, what is the right procedure now (I am not familiar with programming and debugging things...)?

Do I have to open a "task" on that bitbucket-site - or was it sufficient to report this bug in this threat?

Kind regards,

Matthias

Please Log in or Create an account to join the conversation.

More
28 Jan 2013 14:17 #5619 by vlad_vy

Please Log in or Create an account to join the conversation.

More
28 Jan 2013 22:13 #5682 by MikroHeliPilot
Replied by MikroHeliPilot on topic Bug: Protocol change problem (from DSM2 to WK)
It is known as Bug #219 now (whoever created it):
bitbucket.org/PhracturedBlue/deviation/i...-bug-from-dsm2-to-wk

MikroHeliPilot

Please Log in or Create an account to join the conversation.

Time to create page: 0.042 seconds
Powered by Kunena Forum