DSM2/DSMX lost binding during operation

Hi All
I experienced about 3time lossing radio control ( the motor cut off and no control)for secds of my model then the control then the control returns .
It was in about 50 metr range so I dont think it is transmitter rang problem.
l am using devo 7e with range mod and deviation 4.0.1 and origenal spectrum receiver
Is this simptom known as the DSM2/DSMX lost binding during operation ?
And fixed in v 5.0.0 Or I should look for other problem

I had the same problem, with range-modded Devo 7e and Deviation 4.0.1, on a LemonRx DSMX Satellite
I upgraded to Deviation 5.0.0 with latest protocols , and it cleared the problem

Hr wrote: Hi All
I experienced about 3time lossing radio control ( the motor cut off and no control)for secds of my model then the control then the control returns .
It was in about 50 metr range so I dont think it is transmitter rang problem.
l am using devo 7e with range mod and deviation 4.0.1 and origenal spectrum receiver
Is this simptom known as the DSM2/DSMX lost binding during operation ?
And fixed in v 5.0.0 Or I should look for other problem

Too few information., but a range modded 7e should have above 200m with the genuine antenna and above 330m range with a
well oriented swivel antenna.at 100mW setting. This is at least what I got with a 615x two years ago.
You might have had badly polarized antennas.

In additions to upgrade to v5.0.0 I thaink for being in the safe side I will do the antenna mod.
Thank for yours answer

Thank you l will update to v5.0.0

Don´t expect too much, maybe your mod is not working correctly.

Hi
So how can I test my range mod to be shure it works ok?
By the way, last night I installed to my DEVO 7E v5.0.0 but used my old hardware.ini file that was used in my transmiter with
previous 4.0.1 version,last nightly builds becouse the new hardware.ini file (that is with v5.0.0) didnot work correctly 'the extra swiches didnot work.

That is normal since every hardware.ini file from a downloaded distribution has to be edited to your own needs.
Do at least a ground test with a test rig. (rx/ bat/ servo on throttle channel)....and walk until the failsafe kicks in.

Ok Thank you

DSM release 5.0.0 does NOT already include the CYRF reset code which Vlad later introduced in his "5.0 with latest protocol" test builds, which later went into 5.0-nightly-builds (developer master).

So the lost binding durinig opertion is not fixed yet in v5.0.0???

I had several successful DSMx tests flys on 4.0.1-nighty-builds and 5.0.0 release before (450er heli, 200QX, etc.).

I had not any DSMx binding / connection signal loss with those versions - never - even not with DSMx telemetry turned on (it only happend on 1-2 older Indigo's test-builds, but not on other test builds (had not tested latest), on the desk, where I only could actually get the binding back working when turning off/back on the Devo10 transmitter).

---

4.0.1-nightly-build (trunk/master repository) + release 5.0.0 only contain Walkera DEVO protocol CYRF reset code, but not for DSMx.

If you run into the very rare "connection loss / signal loss / bindling loss" of the DSMx <=4.0.1-nightly build I strongly recommend that you upgrade to Vlad's release 5.0 test build.
I flew my EPO glider multiple times on his test-builds with DSMx telemetry turned on, and it works as good as all other previous DeviationTX versions.

If you want to use the latest "5.0-nightly-build" it might work too (Vlad commited some (all??) of his work to the trunk/master/default source repositiory) but those developer nightly-builds are NOT as much deeply tested as Vlad's "5.0 latest protocol release" which is based on 5.0.0 stable release.
There are way too many source changes for 5.0-nighty-builds (including GUI).


YES, you should upgrade and not use the 5.0.0 "stable" release anymore.

If you want to understand more about the DSMx protocol development and it's DSMx state within 4.0.1-nightly-build / release 5.0.0 , Vlad's 5.0 test builds have a look at my summary and linked questions: www.deviationtx.com/forum/protocol-devel...port?start=400#54363

Hi
Reng test update
So I processed ground test and get about 290 meter of full control on my umx carbon s .
So I belive the control probelm I experienced is the DSM bindinig lost.

Which RX are you using? Many have quite a high brownout voltage, eg. drop below 4.0V and it dies.
I had quite a few problems originally, always thinking it was a radio issue, but turns out I was overtaxing the ESC's built-in BEC; when I started including cheap stand-alone BECs (eg. 3Amp) the issues went away.