Devo 12S DSMX Range and Telemetry Questions

I've been flying a 7e with v4.0.1-92e1705 for months with several small planes and a 450 heli. It is a mixture of DSXM DSM2. One is a lemon DSM2 6ch, one is a Spektrum DSMX 6ch. And the heli uses only orange DSMX sats to a vbar. I have had all three lose connection at least once during flight and not reconnect. I recently built a large plane and rolled the dice with a Spektrum ar6210 DSMX and luckely did not lose connection. I did 4 flights and estimate a range of over 1000ft.
Regardless, i will be grounding my Devo. My modles are becoming too big to risk. Would be nice to have reliable build though as range seems to be good.

I confirmed a while back that the 4.01 build has a bug to cause RF power locked up while using DSM2/X protocol.

Go and get Indigo's (a big thanks again) build that fixes this and don't forget to disable Telemetry option and you will get a rock solid flight.

In fact, do disable Telemetry for whatever protocol (not even Devo) you are using for a safe flight. Don't ask me how I know..

cmPang

Hello guys, I went thru this thread after a while I've not been here and if I understood well, Indigo, you've fixed the bug in the firmware and the range issues have been solved? If yes, that's really great!!!! And thank you so much!!!
I love my Devo tx (now I have Devo 10) and I'm considering to buy Devo 12 later on and will leave Devo 10 for my son

I've been little bit sad, due to the range issues, bcoz I will buy 700 heli and I don't wanna to ground my favourite powerful Devo TX.

So is it rock solid with the Indigos' firmware? And what about the patch, which I found on download page - what is it for?

PS I'm not using the telemetry.
Thank you so much, guys for keeping the amazing devo alive!

Range issues may have been solved, because Devo telemetry was transmitting data immediately after switching from receive mode back to TX mode. If the PA takes time to reach full strength then that would effect range. Now that TX mode is enabled earlier before transmitting data that might be the fix.

However, I've only just published today, and no one has tested and reported back yet...

The SkyArtec.patch is attempting to fix tx power level has no effect... which is a different tx module, unrelated to Devo and DSMX protocols.

What can i do to help. I have a:
Devo 7e with range mod Tested to over 1000ft I will flash with your current firmware.
I have a Spektrum 6210 Rx (DSMX)
Spektrum 6200 Rx (DSM2)
Lemon DSM2
and some OrangeRx R110X DSMX Sats.

I could put them in my biggest plane as just payload and bound to the devo and fly the plane with my Taranis as far out as i can and then check the led's on return.

Indigo wrote: Range issues may have been solved

Did this also affect systems with disabled telemetry?

I have not installed the patch yet since i forgot how it works. Sucks to be old
TX power measurements were exactly the same in dsm2, dsmx and devo modes. The thing measures peak power, not average, so it does cope with the pulse type transmissions.

I wonder if i should remove that bandpass to test. Downside is i can remove it, but not reinstall it, its tiny.

Or then install this $12 PA-module i got and punch out 600-900mw.
www.banggood.com/2_4G-2W-Bi-Transceiver-...Module-p-940549.html

I have been using this module in one of my 7e for quite some time now.. it works .

However, the "Telemetry" issue is not related to range (not a power output level issue). It is the "Telemetry" that forces the module into "Receiving" mode. and locks out the usual power output.

So, turn "Telemetry" option to "OFF" for a safer flight..

cmPang

Ok, last update hasn't fixed range issue or Devo Telemtry tx power lockout issue.

However, I have good news.

This morning I experimented with the code the discards bad telemetry data. And by checking buffer full bit 1st then data received bit 2nd, I now have it working just as well^, only now I get twice the range I had before. Yes, true. This confirms the reported range issue.

With telemetry ON or OFF, I now get twice the range.

^ There is now a bug I need to fix in that sometimes telemetry display stops updating, but that shouldn't be hard to fix.

So in next update you should see an improvement in DSMx range.

Hi Indigo,

as written in DSM telemery thread www.deviationtx.com/forum/protocol-devel...port?start=200#30238 I am having FrameLoss > 155 / 255 issues with deviation-devo10-v4.0.1-70993a8. Even 1-2 holds.

For sure only because of the MicroHeli carbon frame and antenna orientation problems. It seems that the bottom carbon platter blocks (not open on that point).


I am sorry, I get lost again with all that telemetry ON/OFF DSMx and multiple versions stuff.


Would you say that if I turn OFF telemetry on your latest test build deviation-devo10-v4.0.1-887aaac that it may get no holds / better DSMx (100mw) range?

Did I get you right?

I was flying the 200QX before on V4.01, V4.01 normal head/trunk deviation-devo10-v4.0.1-92e1705 and your testing versions deviationTX-devo10-v4.0.1-c0b203a / deviation-devo10-v4.0.1-70993a8 or just fine with the HH 200QX
plastic case. However I can not remember checking the concrete FrameLosses with it.


So according to your 1st/2nd bit feedback the DSMx telemetry range bug is in in all versions???


Nevertheless would be interested in improvements.
Probably will try to throw away board 200QX antenna and solder something longer for better orientation into the board hole

Thomas

good news...

I don't understand you....

I am using Deviation 4.0.1 DEVO and DSMX protocol without telemetry (telemetry OFF). If I flash new firmware, then range will be increased 2 times for DEVO and DSMX Protocol ??!!

Short answer: NO, only improves reliability with Telemetry ON.

Actually range is not increased as much as first thought (if at all). Most of the difference must be environmental, because I tried earlier versions and could achieve similar range.
So my original claim was overly optimistic

On minimum power setting 100uW and telemetry ON, I used to get only about 5m reliably indoors before loss of binding. I now find I can get up to 10m, it's not 100% reliable at that distance but it definitely has improved. Most of the time a hold is now only a fraction of a second and hardly noticed but I can still get a hold that lasts for several seconds and results in a crash.

The change really only reduces Holds occurring telemetry ON and improves rebind time when they occur. I hope that telemetry ON is now as reliable as having telemetry OFF.

Indigo wrote: Short answer: NO, only improves reliability with Telemetry ON.



On minimum power setting 100uW and telemetry ON, I used to get only about 5m reliably indoors before loss of binding. I now find I can get up to 10m, it's not 100% reliable at that distance but it definitely has improved.

This is right with your latest build, but somewhat mysterious. Tested v4.0.1-72057cf with my 7e and achieved with telemetry ON a little more range than with telemetry OFF(only 1.2m but....)
Due to rain I tested at first indoors, tx 100uW ( different room), distance 8m, one or two walls...The RX615x with dsm2/X does only little flickering when I moved in front off it and it binds immidiately after a power on.
The Storm s603 all solid....so no more testing with this rx.

Somewhat later I did a range test in the garden.
with the sensitive RX615X and got 12 m with telemetry off and 13.2m with telemetry on...??? The flickering only starts half a meter befor loosing bind...? All antennas were in optimal rf beam position.

Did this test last week with the same equipment and got only 8 meters, so 50%
plus now.

So Telemetry ON range issue now appears fixed.

Excellent, thank you.

@Indigo..
Did you change the audio routines for DEVO in this build or did you put code from someone else into it?

The annoying buzz sound is back!

You can kill it currently by selecting the WK protocol and then back to Devo.
But after cold start it is back.

EDIT: Before this, I had your second patch (Devo/telemetry on/off for 7e) from January 30th on the tx. No build ID.

Unlikely anything I've done.

I updated to latest nightly 3 days ago so any changes there are also in my build. Could you please test the recent nightly builds and see if the problem is there? Thanks.

..e1a3b14?
Ok, will test this today, but now I have to get some sleep...

It must be global for the CYRF because the same occures with DSM2/X.
Only a protocol switching can stop it for the moment.

Ok, with --deviation-devo7e-v4.0.1-2765f0d-- the last nightly, the tx
keeps quiet again

But there is no option to select telemetry on/off for DSM2/X...
With the Devo protocol the option persist.

Indoors the range with the RX615x is not as good as yesterday, but outside the house it seems to be the same.

With the new rangetest I have less range as if I would power on the tx at 100uW...??...which should make no difference.
But due to Internet and Wlan time at my residence, I will test this later on at an unoccupied place.

Does your patch bring back the telemetry option for DSM2/x ?

BTW, in my opinion the code for the usb menue is wasted rare code place on the
7e, but this is only my thought.
The ext/ent button was ok for me, but most likely not for people who do not read manuals.

i think indigos patches are at the moment not in the team nightlies

@aMax: Wrong DL address.
Indigo test rls for telemetry: bitbucket.org/Indigo1/deviation/downloads

Version as of 03/26: 72057cf