Devo10 DSMX and Oranage/Lemon Rx issues

Hello,
I have been using the Devo 10 with 4.0.1 and been seeing blinking red LEDs on my Rx. This happens within 50-100 feet at 150mW. If I turn the radio down to 100 uW then I can see blinking red led on my 6CH PPM Lemon Rx with a Satellite within 1 foot.

I believe this is a software issue. When I fly my quad I can tell it is not receiving commands for a second or 2 then it will respond fine for a little while until it happens again. This is mainly with DSMX. I have better range with DSM2 but there are a lot of better features in the DSMX protocol.
Has anyone else been seeing this issue?

I'm getting this issue on both of these receiveres.
Lemon 6Ch PPM Rx
www.lemon-rx.com/shop/index.php?route=pr...th=72&product_id=118

Orange 6Ch Rx R615x
orangerx.com/2014/05/20/r615x-spektrumjr...hz-receiver-wcppm-2/

Video of issues

DSMX - I should have videoed the Rx but it blinks at a short range test.


DSM2 - No blinking at the same range test.

Hi,

I have 7 Orange RX's, three R615x, two R800x, and two R415x.

ALL OF THEM show signs of connection issues. this has grounded my entire fleet, as I'm scared to fly them when the RX is flickering.

they are setup as DSMX. I have done these things so far in attempt to resolve this issue.

-Opened brand new RX's, which flash randomly right out of the pack
-Updated to the lastest nightly TX firmware from the latest stable
-replaced my 2.4 internal module with a new out of the box module from walkera ( www.banggood.com/Walkera-WK-DEVO-S-MOD-U...8S-12S-p-922596.html )be aware this module has the same part number and revision dates as the one that came out of my devo. the only difference was this one had green pcb and the original had black pcb.
-verified multiple times the antenna lead is in good shape, and connected properly.

I borrowed a Taranis, and an orange module, and my worst TX was solid link on the first bind, and was solid link light for the remainder of the night (I flew sim with it)

here is a video of two of the many orange RX I have.

R615X number 1
R615X Number 2

these are 2 different RX, connected to different things, on the same TX.

I would gladly send my TX and an RX to someone more qualified to help resolve this.

I have a Devo 10 and DSMX satellites on two different receivers, plus a Blade copter with AS3X that uses DSMX. It's been a while but I remember changing telemetry and number of channels to get them working. Currently flying with no issues, but the location doesn't have room to fly further than 150m.

Telemetry should be off unless you have telemetry installed on the aircraft.

I remember number of channels set to 7 caused issues, but maybe only with telemetry on? (memory fading). I currently set channels to 8. Check the comments in this thread .

I have a camera copter on an orangerx DSMX SBUS receiver that flies 350+ meters far and 200 high without issue. My OrangeRX DSM2 sats sometimes trigger the signal loss alarm on KK boards, but I never actually had control issues. With lemonRX receivers I never had any issue at all.
I do have major issues with orangeRX CPPM receivers, though. On several of them (3 I own, R410X and R415X), all channels show as centered on a KK board, but the yaw is constantly drifting. The yaw channel actually can not be centered, when subtrimming, it can be -1 or +2, but never 0. Even with a deadzone set, the copters will constantly turn slowly. Switch to DSMX/DSM2 satellites, no issue whatsoever.
I thought it was down to the receivers alone, but I just found out someone else has the same issues with another orange CPPM (R615x) and a Devo 10.. he has a video here: www.rcgroups.com/forums/showpost.php?p=30609777&postcount=5987
Also see here for my report to RC911 on the problem:
www.multikopter.co.uk/forum/topic/1714-k...1/page-47#entry20900
If you are not registered there, here's what he noticed:

Thanks for testing. Can't see any significant drift on your rudder channel (assuming it is channel 4). In fact all channels seems very stable, but the frame/sync length has varied quite a bit. Do these two numbers jump constantly while looking at the "live" (first) screen or do they just drift slowly?

So maybe there is some issue with the DSM protocol, going out of synch or something.. at least with orangeRX receivers?

My findings, also from that thread:

Quick video of the issue. Sorry for the bad tracking of the quad, but it causes a lot of turbulence in a small room.. but I think it's fairly visible. Especially if you watch the lasers against the wall, you can tell how it spins slowly left.

And since I'm a QA tester anyways, some more things I checked:

- When bound in DSM2 mode, the exact same thing happens, so it's not down to protocol between my transmitter and receiver

- Yaw P/I to 75/70: No change

- Yaw P/I to 30/25: No change

- Tried binding as 6 channel receiver (I had originally bound as 7), no difference.

- Swapped back and forth 4 more times on the same battery within 1 minute of each other: Zero drift with Sat, bad drift with CPPM.

The drift also seems to get randomly (?) worse. When I started the test earlier with a fresh 3S battery, the drift was slow and paused occassionally. Now the battery is ~1/3rd down and it starts rotating even while lifting off already.

Had used normal PWM DSM2 receivers some months back with no issue then either.

I think the issue may be related to how the Yaw channel is always either -1 or +2 depending on subtrim, but can't seem to hit 0.

I've seen similar behaviour to the OP with the OrangeRX DSMX satelite on one of my mini-quads. The range is only a few meters when bound as DSMX, but when bound with DSM2 it works fine. I only have one of these, so I had thought it was a dud RX. Maybe it's a protocol issue with the DSMX implementation in Deviation? The behaviour is the same with both my Devo12S and Devo10.

hexfet wrote: I have a Devo 10 and DSMX satellites on two different receivers, plus a Blade copter with AS3X that uses DSMX. It's been a while but I remember changing telemetry and number of channels to get them working. Currently flying with no issues, but the location doesn't have room to fly further than 150m.

Telemetry should be off unless you have telemetry installed on the aircraft.

I remember number of channels set to 7 caused issues, but maybe only with telemetry on? (memory fading). I currently set channels to 8. Check the comments in this thread .

i just got home, first thing i did was re bind my worst blinking rx to the devo, and attempt to adjust these settings.

i checked -telemetry=off (was never on)
channels- 6/7/8
all of this on a 6 channel rx.

i will say when set to 6 and 7 channel on the tx, the flickering was somewhat constant, but when set to 8 channel the rx light would never come on.

i sure hope someone can figure it out.

mikemacwillie wrote: I've seen similar behaviour to the OP with the OrangeRX DSMX satelite on one of my mini-quads. The range is only a few meters when bound as DSMX, but when bound with DSM2 it works fine. I only have one of these, so I had thought it was a dud RX. Maybe it's a protocol issue with the DSMX implementation in Deviation? The behaviour is the same with both my Devo12S and Devo10.

this is what I'm thinking is going on. It may or may not be related to CPPM mode but I think we have enough interested posters here to test further.

What i am missing most, is the build version these guys are using.

Just after I saw the first video in this topic, I was alarmed and did a test
outdoors with exact this rx. /OrangeR615X/

Plain sight, power 100uW, protocol DSMX, tx Devo7e, v4.0.1-92e1705
The distance I achieved was eight meters, with DSM2 little more solid
depending on the antenna direction but not more distance..

Later on....
Since I was not able to deactivate the telemetry with my build, I flashed an old nightly and did a test inside the house. Placed the rx at the window and went into the kitchen. Distance exactly seven meters straight line distance and placed the tx upright on the table.

Now there were two walls ( chimney)left half and a fridge and one wall on the right half between tx and rx.
Even then the rx stayed bind with little flickering while I was moving around.
And....exactly the same behavoir, a little more stability with telemetry off.
At 300uW output there was no difference anymore and the rx rock solite.

If the weather does allow, I will repeat this outdoors.
...v4.0.1-ac4f0b2 (2014-03.30)..

For the record I have had this issue with the FW 4.0.1 stable on the webpage as well as 2 newer nightly builds from December of last month. I updated to a nightly for the multi-module code but found that there is an issue with the FrSky module on the MM so I just wired up the cc2500 module in the Tx and decided to wait for the code to get finished after PB's hiatits.

Seemed not to be that far in the video.
....already checked the antenna connection to the CYRF?
The RF emission should be better than on the 7e.

hum.... seems my finding may be right.. it is the telemetry ....

Not in my case or Johnzm's.

aMax wrote: Plain sight, power 100uW, protocol DSMX, tx Devo7e, v4.0.1-92e1705
The distance I achieved was eight meters, with DSM2 little more solid
depending on the antenna direction but not more distance..

Is 8m at 100uW good or poor? What numbers are expected? (still learning and this isn't a priority at my small field)

I am using 4.0.1-3b632a8, Devo 7e, Telemetry is off I believe. Is there even an option for the 7e to enable/disable it?
To sum it up, it appears that the OrangeRX receivers have massive frame drops or desynchs. The big question is, are they only happening with Deviation?
On the HK Reviews, two or three people reported similar issues. I just asked them what transmitter they use. If it's also a devo, it has to be an issue with the software.

Johnzm borrowed a Taranis from a friend with the DSM module and did not get blinking lights at low power range tests. So he bought a Tranis so he could trust his receivers until this is fixed. The Devo10 does have an advantage being 150mW vs the Taranis module being only 100mW.

Because of this we really think the issue is in the software for the DSMX protocol.

Thing is, the orange module may have some way to compensate for the problem, if the developer is aware of it. The real test would be to try an original Spektrum transmitter.

hexfet wrote:

aMax wrote: Plain sight, power 100uW, protocol DSMX, tx Devo7e, v4.0.1-92e1705
The distance I achieved was eight meters, with DSM2 little more solid
depending on the antenna direction but not more distance..

Is 8m at 100uW good or poor? What numbers are expected? (still learning and this isn't a priority at my small field)

Depends on what you compare it.
Last year I tested my new SCP and DEVO with these settings and obtained twice as much.....(v4.0.1-ac4f0b2)
You may believe it or not, the little A7105-D03, with its short wire, gained 18 meters with a simple V911 board.

The only question for me is how to deactivate telemetry for DSM2/DSMX in
v4.0.1-92e1705...?

I just tried www.deviationtx.com/forum/3-feedback-que...y-questions?start=40 this version where Telemetry can be turned off. No change. Flickers, rotates left, lots of frame and synch drops. Plug in the DSMX or DSM2 sat and it instantly flies fine again, no flickering there either.

To sum it up:
- Spektrum Satellites (both OrangeRX and Lemon) give me no flickering. On KK board, the Orange ones sometimes trigger signal loss (rarely), but never actually lose control.
- Spektrum PWM receivers (LemonRX 6 channel "Feather light") no flickering, no issues at all.
- Spektrum SBUS receiver (3 Channel DSMX, OrangeRX) never flickers, never loses signal.
- Spektrum CPPM receivers (OrangeRX R410X and R415X) keep flickering, show bad frame and synch drops, cause the KK board to yaw constantly.



These are the high/low values of the data the KK board reads from the CPPM receiver over a course of roughly 10 minutes. You can see that the frame and synch values drop very far.
What I can not test is how it behaves with an original Spektrum Transmitter.

Let me add a data point. I noticed that the Rx on my 200SRX was blinking instead of it's usual solid light. While this Rx is telemetry-capable, it doesn't report transmission issues, but provides vibration and setting reports from the flight control board.

When I bind this Rx with telemetry ON, I get a blinking light on the receiver. Turning telemetry off doesn't change that.

When I bind it with telemetry OFF, I get a solid light on the receiver. Turning telemetry back on doesn't change that.

Using 6 channels at all times.

This is on a Devo10 running the team nightlies (well, sorta - I've got some beta display code; no changes in the protocols directory, though).

So how can I help troubleshoot the issues we are having? Is there a way to log the signal from the Tx at the Rx? Just watching RSSI would only indicate the signal strength. We are looking for frame drops and other issues. How would one test/see this information?