V120d02s-V2 lost binding mid flight

I am waiting for the Nightly's to update, but there is still
fe45d83 2014-02-24

Is there anything wrong with the automatic building process?

Some feedback on Nightly build 47f4800
1. No corrupted telemetry data anymore, but that was expected - right

2. I had at least one incident with "loss of binding", but it seems to be more difficult to trigger this. I will do more tests on this, but that is very time consuming, thus will take a little longer.
I am still wondering if my Devo10 might have a hardware problem, because of the poor range for telemetry. ~10m at best with MiniCP (dropouts way before)

3. Now I am having a new issue with data logging:
I tried to log all telemetry related data - regardless if supported by RX or not.
While with V4.0.1 all values showed up in the log, now I don't see any data at all. (at least datalog2csv.py doesn't show them)
No problem logging only Temp1 and Volt2
Could this be related to #531?

4. In telemetry monitor one sees invalid data displayed inverted resp. red.
I am not aware of a way to see in the log if the data is invalid.
Would be nice if one could recognize invalid data in the datalog.

PhracturedBlue wrote: My guess is that fixing this is as easy as checking the RXE (receive error) bit and rejecting bad packets, but I have a feeling that I tried that when I originally implemented telemetry and ran into issues.

Me too with 4161437
Still suspecting a hardware fault of CYRF6936 in my Devo10 I invested 20.-EUR in a new "telemetry module from Walkera" which I will call Module-2 now.

Test results:
First Module-1 (original in my TX):
1a) Module-1 with V4.01
- bogus telemetry packets
- likely loss of binding with MiniCP within ~4h of operation
- range of telemetry poor ~7m at best

1b) Module-1 with Nightly 4161437
- no bogus telemetry packets anymore
- loss of binding very unlikely, but happened.
- range of telemetry poor ~7m at best

Now Module-2 (which I bought new)
2a) Module-2 with Nightly 4161437
- no bogus telemetry packets
- I wasn't able to trigger loss of binding.
- range of telemetry still poor ~7m at best, but worse in some way:
Once out of telemetry range, the telemetry values hardly came back even if TX close to RX.

2b) Module_2 with V4.01 !!!
- range of telemetry at least 50m (about the same as conrtol at 10mW)
- no bogus telemetry anymore
- With New-V120d02s I am getting range for telemetry comparable to WLAN.
(going through 1-2 walls)


Edit: see
#533 #525

I dont know if it is the same issue but I get a loss of control after about 3mins with a mini cp and master cp using devo 10.
slow prio seems to get the gyro out of whack and death spiral into a tree, car, ground soon ensues. controls no longer work.
re=power either tx or kite and you fly again.

You can also get slow responses to controls or delayed responses and differing values while flying.
in that I can roll but the roll is slow then back to centre. roll again and it is quick. dunno if it is Heli or Tx or devention.
Just something I have observed with 2 walkera's and the devo 10.
I have also tried simple mixer to see if that has anything to do with it. it doesnt.

As I havent seen others report this, I put it down to local.

p.s. I dont have telemetry on (cant find out how to enable it)

glenby wrote: slow prio seems to get the gyro out of whack and death spiral into a tree, car, ground soon ensues. controls no longer work.
re=power either tx or kite and you fly again.

You can also get slow responses to controls or delayed responses and differing values while flying.
(cant find out how to enable it)

I have the same problem with Devo 7e (with installed 911 module) using a wltoys 912. Latest nightly build. It doesn't happen periodically. I don't think it's the gyro. Servos are extremely sticky, reacting with a time lack of some micro- to whole seconds. Turning off and on Tx and Rx is the solution.

suzali wrote:

glenby wrote: slow prio seems to get the gyro out of whack and death spiral into a tree, car, ground soon ensues. controls no longer work.
re=power either tx or kite and you fly again.

You can also get slow responses to controls or delayed responses and differing values while flying.
(cant find out how to enable it)

I have the same problem with Devo 7e (with installed 911 module) using a wltoys 912. Latest nightly build. It doesn't happen periodically. I don't think it's the gyro. Servos are extremely sticky, reacting with a time lack of some micro- to whole seconds. Turning off and on Tx and Rx is the solution.

Hi suzali, hi glenby,
I don't think that your issues are in any way related to mine.
When you read my posts 21247 and 21524 you will see that "my" issue is:
a) related to telemetry
b) associated with a defective TX-Module
c) could lead to "loss of binding" (usually indicated by the RX with a flashing LED) i.e. not any reaction of the heli anymore.

linux-user wrote: summarize: see issue #525
- No issue with telemetry switched off

- Corrupted telemetry data could lead to a loss of binding.
I am able to reproduce this with MiniCP and Devo10 most likely within 3h of operation.

- The "loss of binding" is related in some way to quality of telemetry data.
With a distance RX<->TX of 20cm I am not able to trigger the issue.

- If binding (and thus control) is lost and you do the following:
1.) switch telemetry off => control is back instant.
2.) load a different model and then same model again => control is back within a few seconds.
3.) power cycle TX => most likely control comes back within a few seconds.
4.) press "Bind" button => this doesn't help.
5.) power cycle RX while leaving TX on => this doesn't help.

With the attached log files I tried to log all devo telemetry data at 10s interval.
Note that MiniCP only supports Volt2 and Temp1

datalog20-all.bin is at a distance RX<->TX of ~20cm
datalog300-all.bin is at a distance RX<->TX of ~300cm

datalog300-all.bin actually catches the issue at ~59min
At ~64min telemetry was switched off and control was back instantly.

linux-user wrote: Still suspecting a hardware fault of CYRF6936 in my Devo10 I invested 20.-EUR in a new "telemetry module from Walkera" which I will call Module-2 now.

Test results:
First Module-1 (original in my TX):
1a) Module-1 with V4.01
- bogus telemetry packets
- likely loss of binding with MiniCP within ~4h of operation
- range of telemetry poor ~7m at best

1b) Module-1 with Nightly 4161437
- no bogus telemetry packets anymore
- loss of binding very unlikely, but happened.
- range of telemetry poor ~7m at best

Now Module-2 (which I bought new)
2a) Module-2 with Nightly 4161437
- no bogus telemetry packets
- I wasn't able to trigger loss of binding.
- range of telemetry still poor ~7m at best, but worse in some way:
Once out of telemetry range, the telemetry values hardly came back even if TX close to RX.

2b) Module_2 with V4.01 !!!
- range of telemetry at least 50m (about the same as conrtol at 10mW)
- no bogus telemetry anymore
- With New-V120d02s I am getting range for telemetry comparable to WLAN.
(going through 1-2 walls)

I tried using telemetry today for the very first time. I never tried it before even with V2 and V3 firmware.

The telemetry worked well for me, no problems or issues.
I am using the Devo 10 and tested telemetry with my Walkera Ladybird V1, Mini CP BL, and V120D02S V2. I'm using V4.0.1 firmware.
I used the 10mW transmitter output setting.
No fixed ID for the helicopters or quad.


Edit: I did some range tests.


1mW transmitter output setting

Distance: 52 feet and 72 feet. Measured with my 100' tape measure.


10mW transmitter output setting

Distance: 52 feet and 72 feet. Measured with my 100' tape measure.



100mW transmitter output setting

Distance: 52 feet and 72 feet. Measured with my 100' tape measure.



Range tests done with my Walkera Ladybird V1 and Mini CP BL.

Results: Telemetry worked correctly, no issues.





PhracturedBlue,

You posted that "telemetry is definitely buggy. I can see random values on the telemetry screen when adjusting the throttle."

"I believe I've resolved the issue with corrupt Telemetry".

Is there a bug in the firmware using telemetry and you have resolved it in the nightly build which we all should be using if we want to use telemetry?

Hi Tom

100mW transmitter output setting

Distance: 52 feet and 72 feet. Measured with my 100' tape measure.

Did you really get the exact same distance with all 3 power settings?

RM

Hi RM,

I tapped down the hel and quad to a heavy wood block so they would fully function
and I can check telemetry under different loads (throttle). At that distance they were to small to see if I tried to fly them.

At 1mW transmitter output setting I was expecting not to have any functions let alone telemetry readings but everything worked.
The helicopter fully functioned at both 52 feet and 72 feet with the 1mW transmitter output setting. I could throttle it, change flight modes, engage throttle hold, and fully move the swashplate.
I repeated this with the 10mW setting and 100mW setting. I know I would have had much more range but I couldn't go any further in my back yard, 72 feet was the limit.

If this was a range test of the deviation I would have went to the park I fly at to film my videos which is about 800-900 feet or more long and tested each transmitter output setting for how far it can go to.
I also did range tests there for the Devo F7 to see how far the video could be transmitted from my quad to the transmitter and the result was 325 feet.