Protocol Stacks

FDR wrote:

PhracturedBlue wrote: Another weird thing. I can't seem to get my RX1202 to unbind. I've tried the unbind-plug in every position, but it doesn't seem to want to unbind from its current configuration.
Luckily enough I know the ID it is bound to, so I can still use it.

The page 29 of the DEVO 12 manual says:
"Fixed ID cancellation
Insert the assorted BIND PLUG into the output terminal of BATT before the receiver is powered on, and then plug 5V DC power into one of the other terminals. The red light of receiver will flash slowly. This means the fixed ID code has been cancelled. Pull out the BIND PLUG."

Same method for the DEVO 10...

sutaburosu wrote:

PhracturedBlue wrote: Edit: I see you meant it actually did bind without unbinding....Not much I can say about that, it should not be able to do that because the encryption is wrong.

Indeed, hence my guess there must be some kind of packet to clear the rx's fixed-ID. If this is what is actually occuring, it might be a useful addition to Deviation to have the ability to clear an Rx's fixed ID without having to resort to using a bind plug; on my 250 the Rx1002 is truly inaccessible.

PhracturedBlue wrote:

sutaburosu wrote:

PhracturedBlue wrote: Edit: I see you meant it actually did bind without unbinding....Not much I can say about that, it should not be able to do that because the encryption is wrong.

Indeed, hence my guess there must be some kind of packet to clear the rx's fixed-ID. If this is what is actually occuring, it might be a useful addition to Deviation to have the ability to clear an Rx's fixed ID without having to resort to using a bind plug; on my 250 the Rx1002 is truly inaccessible.

Another possibility is a bug in the Rx firmware. I've read rumors of RXs unbinding (though I thought that was only the WK2801)

FDR wrote: The WK2401 and 2601 protocols don't show the binding message!

BTW I've put the label of the bind button into the language files...

PhracturedBlue wrote: Ok, I added the ability to get the full range on the 2401 using the algorithm we discussed before. I'll be quite interested in whether it works since I can only do limited testing in the emulator.