I have this Problem with binding to this rx (NEW 120D02S)
This RX can only fix-bind with current randomly generated id.
The problem is that in this FW I CANNOT KNOW what is the current random ID.
Is there a workaround to know this id ?

Obviously it is a WK bug, but so Deviation cannot bind with fixed-id to this heli.

Try to clear the fixed id with the bind plug, and assign an other later...

However if you mean, that you cannot clear the fixed id from that rx, but you have an original model config, which works, than the good news is that config file contains the right fixed id.
If it is a DEVO 8, than you can upload that file into my model configurator webapp (rc.fdr.hu/model.php), and it will display the configured fixed id.
Then you can set that same id in the deviation fw, and it should work...

FDR wrote: Thank you for your quick reply, but neither help.
I need to know the CURRENT RANDOM GENERATED ID to fix bind this RX.
Is it possible ?
(in the original FW YES !)
Thanks

It's known bug at V120D02S Rx, it can bind only with fixed ID that equal current randomly generated id.

I agree that will be nice to know current randomly generated ID at Deviation Tx. But I haven't idea where to display it.

Yep, that's what I'm talking about.
You can download the original fw's model config file with the dfuse tool (if you remember which model was it, but worst case you have to download all 12).
To tell the trouth I've never tried to download the old configs while deviation is installed, but it might work. (If you don't have it already downloaded)
If it doesn't work, then you have to restore the original fw, and not the fixed id of that model. Do not forget to save your deviation models before upgrading to the old fw and library, because they will overwrite them!

vlad_vy wrote:

EDIT: I don't understand. How do you use that rx, if it doesn't comply the protocol?

Yes, I agree.
Since I've never fixed binded with the original FW to retrieve the ID,
the only solution I think is:

1) Save all filesystem of your Deviation Config
2) Rewrite the original firmware
3) Fixed bind with the current random id genarated
3) READ it and write it down
4) Check that rx keeps it (Power off/on)
5) Reflash the Deviation Firmware
6) Restore filesystem
7) Power on tx and try to fixed bind with the previously written down id

Do you think it's worth it or better to keep random id binding ?
Personally I think it's not worth it.

So if I understand right, you used to use it with the original fw the following way:
1. Bind automatically first;
2. Go to the fixed id menu, turn it on (it displays the actual randomly generated id), then without sending the fixed id to the rx, use it with the fixed id left on?

BTW if you have a DEVO 8, if I were you I would still try to download the original model config, and get that fixed id from it with my webapp...

EDIT: ...or have you used it already auto binded with the deviation, so that "fixed" id is lost?

FDR wrote:
It's a problem with V120D02S Rx only. Maybe this will be corrected with next Rx firmware update, maybe not. But now as is:
1) you can clear ID
2) you can bind without fixed ID
3) with Devo Tx you can see random generated ID and use it as fixed ID
4) you can't bind with arbitrary fixed ID
5) with Deviation Tx you can't see random generated ID and can't use it as fixed ID

vlad_vy wrote: Thanks vlad you explained the situation better than me !

vlad_vy wrote:
So is the problem only that the fixed id doesn't work with some values?
Than it might be, that it won't always bind with deviation even in auto mode either, because we don't know the random generation algorythm used by Walkera...

I'm aware of this issue. The next release will provide the ability to see the current 'random' id

Also, Deviation uses the same id algorithm that Walker uses, so as a work-around, if you've bound your model using the Walkera Devention FW (on the same transmitter), you should be able to enter the same fixedID to Deviation and get it to work.

It's working. I can bind QR Ladybird with same fixed ID as I use with Devo.