Devo10 DSMX and Oranage/Lemon Rx issues

I hadn't used my orangerx r615 (dsm2) rx's much and didn't realise what the blinky light meant, but have just started using them a bit in planes and cars and after reading this did some experimentation.

When set to 7 or 6 channels, on a 4 channel plane, I would get a solid light when using the bind plug, but when I removed the plug and restarted (fixed ID) I'd get a blinky. Seems when I've reduced the channels to 4 it now gets a solid light all the time (not range checked).

On my other 4 channel plane I've got the throttle on channel 5 as supposedly it draws less current there, so when set to 5 channels output it seems to stay solid.

When I set to 8 channels I think I only got an output on channel 1.

Haven't tried it on a car yet, would be interesting to see if only having two physical channels connected makes a difference to how it binds. Pretty certain I was getting blinkies when it was set to 7 channels...

I'll be keeping an eye on this, as I had a loss of control of my main plane for a second or two, might be the culprit (before I changed the channels to 4)

so,

I have tested as seen previously, r800,r410,r615 and I get flickering on all of them. my control goes in an out on severe flickering.

I was unable to fly a majority of my models. I couldn't even fly my sim reliably (I could see the channels in the test section, and was getting odd behavior.

I bought a taranis. I bought an Orange DSMX module. all of the flickering is gone. this is on 5 different models. I am not really well versed on what the lights on a tx do, but I would assume the orange light indicates intermittent link loss, while the flashing red light indicates a failsafe.

I have had no issues with failsafe, but it appears that it takes a different condition (or a long flicker off) to make the failsafe happen.

on mine, when I loose control during a flicker, the RX holds the last received signal, but not respond to input. this is very short intervals. at most 1 second long.

johnzm wrote: I have tested as seen previously, r800,r410,r615 and I get flickering on all of them. my control goes in an out on severe flickering.
...
I bought a taranis. I bought an Orange DSMX module. all of the flickering is gone. this is on 5 different models.

Unfortunately, this doesn't mean the problem between deviationTx and the OrangeRx Rx's is with deviationTx. If OrangeRx's DSM implementation is broken the same way on both ends, you'd get this behavior.

Of course, there's no official specification for DSM and that both DeviationTx and and OrangeRx DSM gear have problems talking to JR & Spektrum hardware. So they both have issues, it's just not clear which set of issues is causing this problem .

Is there any data taken with a RF Power Meter for the different Devo models?

johnzm wrote: so,

I have tested as seen previously, r800,r410,r615 and I get flickering on all of them. [...] I am not really well versed on what the lights on a tx do, but I would assume the orange light indicates intermittent link loss, while the flashing red light indicates a failsafe.

In case you mean the receivers things are like that (DSMX on R800X): Correctly bound = orange LED always on. Signal lost once = orange LED off, red LED blinking 1, 1, 1, a.s.o and if signal is right back the orange LED is always on again with the red LED keeps blinking. If the signal gets lost a second time, the red LED will blink 1-2, 1-2, 1-2, a.s.o.. So the way the red LED blinks indicates the number of signal losses.

My latest build now includes a 2nd Telemetry "On" option. The normal Telemetry ON setting should work for most models. If you still have trouble try changing ON setting to "B2".

For those who have problems with Telemetry ON, try downloading my latest version from here:
bitbucket.org/Indigo1/deviation/downloads

Not sure, if this fits into this thread, but I have noticed problems in connecting my Devo 7e to a lemon DSMX 6 channel dsmx receiver.

I tried many things and in the end, it seems that it only works if deviation is set to 8 or more channels (even if the receiver is only 6 channels). This may have something to do with 11ms or 22ms frames, but I don't know.

Anyway, doesn't seem right or intuitive that one needs to choose more channels than the receiver can operate on to be able to get a working connection.

Hi Neuer_User,

The DSM protocols go wonky if you have 8 or more channels. This is documented in the manual. Since LemonRx is another reverse engineering of the protocol, it may have issues across that boundary as well.

Can you tell us what version of DeviationTx you are running? And maybe try some of Indigo's test builds (let him recommend one)?

Hi mwm

I tried several nightlies and also one build of indigo, which I am currently running (db5dcb3 of March 30th).

Interestingsly, it seems that in this case it only works with 8 channels or more. So that going wonky is the only way to get it to work, strangely. (Although I have to say, I have only tested binding and the LED status of the rx, not the proper functioning of all channels, as I am still waiting for my first diy kit.)

Yeah, it might be problematic because of all the reverse engineering that was necessary that someone might easily miss some important details in some special configuration.

Neuer_User wrote: Interestingly, it seems that in this case it only works with 8 channels or more.

When using DSMX with less than 8 channels, you now have the choice of 2 Telemetry ON settings, A1 or ON. One of those should work for you.

Indigo wrote:

Neuer_User wrote: Interestingly, it seems that in this case it only works with 8 channels or more.

When using DSMX with less than 8 channels, you now have the choice of 2 Telemetry ON settings, A1 or ON. One of those should work for you.

Hi and thanks for providing these nice settings.

Concerning the compatibility problem between my Devo 7e and the lemon 6ch DSMX these settings, however, do not make a difference. If the devo is set to less than 8 channels, the connection does not work (blinking LED), irrespectable of whether telemetry if "off", "on" or "A1". Only setting more than 7 channels does give a solid red led.

Then this probably may only be an issue of the Orange/Lemon RXs?!

With 2-3 of Indigos nightly versions I tried to re-bind to
- Spektrum AR600
- Spektrum AR6210

I had setting "6 channels" active.

With A1 flag this did not even work, so Indigo re-wrote the firmware nightly to use again B2 for <7/8CH but provide A1 option.

I could successfully (new) re-bind with ON / B2 + 6CH setting.

But I have to re-test one of the latest...I expect it to work.


Indigo is programming faster than we can download and test his nightlies

I just tested with an old OrangeRX 6 channel Rx. Seems like running in B2 mode doesn't work quite as well, but it would bind no matter what.
However, the dialog about "binding" is being weird. It wasn't appearing when I bound with telemetry off, or with telemetry on B2, but it bound either way.

Neuer_User wrote:

Indigo wrote:

Neuer_User wrote: Interestingly, it seems that in this case it only works with 8 channels or more.

When using DSMX with less than 8 channels, you now have the choice of 2 Telemetry ON settings, A1 or ON. One of those should work for you.

Hi and thanks for providing these nice settings.

Concerning the compatibility problem between my Devo 7e and the lemon 6ch DSMX these settings, however, do not make a difference. If the devo is set to less than 8 channels, the connection does not work (blinking LED), irrespectable of whether telemetry if "off", "on" or "A1". Only setting more than 7 channels does give a solid red led.

If not binding with telemetry "off" or "on" then problem is not telemetry related.

The binding process in deviation is rather simplified and needs to be fully implemented. With all the reports of binding problems, I think binding will be the next thing I'll work on.