Support for walkera telemetry.

Yes, something wrong with telemetry update at Telemetry Monitor page. It has place with the latest build (ddf6350 from 2013-07-06).
Almost all telemetry values have red background. Short white flash has place in time updating value. But something messed here:
if I touch T1 sensor, Temp1 has short white flash and changed,
if I touch T2 sensor, Temp3 has short white flash and nothing changed,
if I touch T3 sensor, Volt1 has short white flash and nothing changed,
if I touch T4 sensor, Volt3 has short white flash and nothing changed,
if I change V3, GPS 'Speed' has short white flash and nothing changed,
and so on.
Boxes at Main page works fine.

Intermediate build works fine, at Main page and Telemetry Monitor page. I think the problem started after last change for DSM telemetry.

P.S. For DSM telemetry all the same. With the latest build Telemetry Monitor page not works.

vlad_vy wrote: Devo 12s, almost latest build (e5d75984334d), RPM sensor works fine.

Exactly, the problem started after this build (from 2013-07-02). At next 2 days PB made changes in DSM telemetry.

89bdbeb Update telemetry handling in preparation for dsm work 2013-07-03
4e4bb31 Add data-structures and code partitioning to support full DSM telemetry 2013-07-03
a68d214 Initial DSM Telemetry display 2013-07-04

PB, can you fix telemetry update at Telemetry Monitor pages for Devo and DSM protocols?

It should work properly now. There was an extra 'i++' that was screwing everything up.

PB, can you disable commit '24f9836 - Make Devo telemetry more robust'? With this commit Devo telemetry works very unstable. Without this commit Devo telemetry works as usual (fine).

bitbucket.org/PhracturedBlue/deviation/i...ble#comment-10807746

please figure out which of the 2 parts of the patch causes issues for you. These were added to reject bogus packets due to user feedback of corrupt telemetry data.

It seems that is the second part of the patch.

With second part of the patch only, Devo telemetry periodically shows wrong value 19.6V (on white background) instead 3.3-4.1V.

With first part of the patch only, Devo telemetry works fine.

PB, can you delete or review the second part of the patch?

I have reviewed it and it should be fine. what that line does is to ensure that we have a complete packet and that the CRC is ok (i.e the data is not corrupt). This was added based on feedback of telemetry instability and it seemed to resolve the issue. I've re-read the documentation, and the following should probably be added:But that doesn't explain why you see more spurious data with the current code. The current code will update telemetry less frequently, not more-so (since it has better error detection). Everything that is parsed by the current code would also be parsed by the old code.

It does not help. With both my Walkera Ladybird telemetry voltage periodically freezed on red background. Without second part of the patch all works fine.