Loss of binding on Devo Protocol about deviation HOT 3 OPEN

From this post:

I was able to duplicate the flashing led behavior with Devo10 nightly build and RX1002 receiver. The receiver is not losing binding and the packets are fine. The PWM outputs are stable and correct even when the LED flashes.

The behavior is triggered by short PWM outputs - less than about 920 microseconds. It only happens if a couple of channels have short output pulses. This makes me think the receiver is mis-interpreting the short output pulses as indicating some type of error condition, and blinking the LED as an indicator.

The PWM output is stable down to at least 900 microseconds on the RX1002. I'm hesitant to change the signal limit in the code, which is mentioned in the doc/Devo.txt file: "The sticks return '0' when centered and seem to max out at 0x640 at either end the upper-nibble of byte 9 indicates whether the channel value is positive/or negative I.e at the end of stick travel the value is 0x640 and bit 9.x indicates which end the stick is at".

I propose addressing the github issue by adding a note to the manual about this behavior.

from deviation.

Any news about this? I encountered the same problem with Devo 10 and blinking RX LED (Spektrum SPM4650 receiver) but don't know anything about PWM outputs or something. For me it happens when i want to add more than 7 channels.

from deviation.

Well it's not the same problem because this issue was about Devo protocol and SPM4650 looks to be DSMX.

If you haven't already done the freq-fine adjustment procedure, do that. Go to protocol options and move freq-fine up and down until bind is lost, then set it to a value in the middle.

If you still have issues try changing the other protocol options. Some receivers have had issues with those settings. I don't know about that particular receiver but you could search on the forum at deviationtx.com.

from deviation.