Support for walkera telemetry.

Vlad_vy Thank you!
I look forward to your response.

Mind posting a picture of your installs? I have two of my heli's with the telemetry modules and figure for about $8 I might as well add rpm too.

I also would not mind seeing how you did it, bought the Walkera telemetry module months back but never installed it on the V450

I have tested the Walkera WK-CTLO1-D telemetry unit on both the Original Dev08s Firmware and the latest Deviation source build from PB's repository for the Devo8s using all the available sensors, including GPS.

The good news:

1. All the Telemetry information arrives at the Devo std firmware
2. All the same Telemetry information arrive at the Deviation firmware
3. Any of the Telemetry parameters can be shown in boxes on the main page and it updates correctly as the parameter changes

From this result it is clear the Deviation implementation of telemetry protocol and interpretation is correct (GPS included).

The BAD news:

The telemetry parameters on the Deviation Telemetry Monitor page do not all update continuously, given the impression some of them don't work:

1. RPM1 and RPM2 always shows zero, however when mapped to a Main Page box both work and update continuously
2. Temp1, Temp2, V2, V3 and the GPS information does not update, but update if you exit the Telemetry Monitor page and go back in. When mapped to a Main Page box they all work and update continuously

(It could be that RPM1 and RPM2 also update when you go into the page, however I don't have enough hands to do the check.)

I'll file a bug report on Bitbucket for this.

FDR wrote: Vlad! Could you confirm RandMental's findings, that they are not updated on the telemetry monitor page, if they are not in a main page box too.

Hi FDR,

just to clarify - my tests showed that all telemetry parameters are shown correctly when mapped to a box on the main page - I have mapped then one for one, and then each one updated as the telemetry value changed. This to me means the reception and updating of the Telemetry values are correct.

I have not yet had a look at the code, but it looks to me as a Telemetry Monitor page refresh issue, and not a telemetry issue.

As indicated earlier V1 and V3 updated and refreshed on the Telemetry page as I changed them, the other parameter fields stayed the same unless I exited the page and go back to it. Then all the fields updated to their latest values, but becomes static after that again.

vlad_vy wrote: I will check this again (with all sensors). In my case RPM and V1 values updated at Telemetry Monitor page, but I always opened this page after Tx power on and auto-bind with telemetry module.

My test also involved the (normal) binding process:

TX on, Devo Protocol, 8 Channels; Cancel auto bind, go to bind/re-init page
Telemetry model on, wait for its LED to start flashing
Click the re-init/bind button on the TX (I did not used a fixed ID)
Telemetry module LED becomes solid red
Goes to the TX's Telemetry Monitor page
V1 and V3 starts updating after a few seconds
Other parameters stays on the value when the page was opened.

Hopes this help to duplicate the results I get or help my if I have the process wrong. Using the same bind process with the original Devo Firmware, all the telemetry parameters update, I am thus confident it is not a test process or bind issue.

(And when I go to the TX main page, the non responding parameters mapped to boxes on the main page, do show the updated values as they change)

No problem at all, I appreciate that you and Vlad are also testing. My additional posts are purely to make sure you guys understand how I tested and the results I get.

Edit:
Also originally thought nothing works, that's why I went back to the other Devo8s running the Devention firmware. That proved all inputs were working, so I started the Deviation test understand why only some fields are updating.