Notice

The forum is in read only mode.

Support for walkera telemetry.

RandMental
Offline

26 Jul 2013 11:07 - 26 Jul 2013 11:07 #12523 by RandMental

Replied by RandMental on topic Support for walkera telemetry.

vlad_vy wrote: When I testing the telemetry last time, RPM and V1 values were working at both places - Main page boxes and Telemetry Monitor page. I will test this again with all sensors and all possible bindig variants.

Hi Vlad, perhaps an easier and more foolproof test - test the T1 - T4 telemetry temperature inputs, as I touched the sensors, T1 and T3 on the telematics screen update and show the increase in temperature, T2 and T4 do not.

Last edit: 26 Jul 2013 11:07 by RandMental.

vlad_vy
Offline

26 Jul 2013 14:02 - 26 Jul 2013 16:28 #12526 by vlad_vy

Replied by vlad_vy on topic 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.

Last edit: 26 Jul 2013 16:28 by vlad_vy.

vlad_vy
Offline

26 Jul 2013 16:03 - 26 Jul 2013 16:08 #12531 by vlad_vy

Replied by vlad_vy on topic Support for walkera telemetry.

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

Last edit: 26 Jul 2013 16:08 by vlad_vy.

ferreret
Offline

26 Jul 2013 16:50 #12532 by ferreret

Replied by ferreret on topic Support for walkera telemetry.

Hi!

I'm using the Walkera telemetry module, with rpm sensor and gps sensor working on a devo 8s. I have two questions:
- First, the speed is measured in m/s, but I think the unit is not correct, because on a trex500 with Hugues fuselage, the cruise speed is 20m/s(70km/h??), and the top speed is 40 m/s(140km/h????)I think is too much. I think the correct data is cruise speed 20 km/h and top speed is 40 km/h.
- The another questions is if possible include on the main page the possibility to include the data of the GPS(the other telemetry data is possible), because the only way the see the GPS data is with telemetry viewer.

Best regards

RandMental
Offline

27 Jul 2013 19:26 - 27 Jul 2013 19:32 #12556 by RandMental

Replied by RandMental on topic Support for walkera telemetry.

ferreret wrote: The speed is measured in m/s, but I think the unit is not correct, because on a trex500 with Hugues fuselage, the cruise speed is 20m/s(70km/h??), and the top speed is 40 m/s(140km/h????)

Why not take it for a drive (with a car)? Shall see if I can do some speed tests tomorrow...

Edit: Ferreret- what firmware are you using on the Devo8s?

Last edit: 27 Jul 2013 19:32 by RandMental.

ferreret
Offline

28 Jul 2013 20:54 #12576 by ferreret

Replied by ferreret on topic Support for walkera telemetry.

I'm using 2.1.1 firmware. Thanks for reply

vlad_vy
Offline

10 Aug 2013 06:25 - 10 Aug 2013 06:26 #12883 by vlad_vy

Replied by vlad_vy on topic Support for walkera telemetry.

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

Last edit: 10 Aug 2013 06:26 by vlad_vy.

PhracturedBlue
Offline

11 Aug 2013 14:15 #12906 by PhracturedBlue

Replied by PhracturedBlue on topic Support for walkera telemetry.

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

ferreret
Offline

13 Aug 2013 10:41 #12941 by ferreret

Replied by ferreret on topic Support for walkera telemetry.

Finally I check the speed with a car, and my Trex 500 with hugues fuselage can run at 70 km/h speed cruising, and a top speed of 140 km/h. The only mistake on software are the units. When I choose miles and feets, the miles units are a really km/h as I check.

RandMental wrote:
ferreret wrote: The speed is measured in m/s, but I think the unit is not correct, because on a trex500 with Hugues fuselage, the cruise speed is 20m/s(70km/h??), and the top speed is 40 m/s(140km/h????)

Why not take it for a drive (with a car)? Shall see if I can do some speed tests tomorrow...

Edit: Ferreret- what firmware are you using on the Devo8s?

ferreret
Offline

13 Aug 2013 10:47 - 13 Aug 2013 10:48 #12942 by ferreret

Replied by ferreret on topic Support for walkera telemetry.

Another think will the best, but I'm not sure if is possible, is to convert the Devo8s as a data logger using the telemetry. Only safe max speed, max altittude, will be very interested. Maybe use a little of the internal memory...

Best regards!

Last edit: 13 Aug 2013 10:48 by ferreret.

BitOne
Offline

13 Aug 2013 14:44 #12945 by BitOne

Replied by BitOne on topic Support for walkera telemetry.

Hi Ferret,

Did you have a look at the Data Logger ?:
deviationtx.com/forum/7-development/1925-datalogger

vlad_vy
Offline

20 Jun 2014 06:58 - 20 Jun 2014 08:13 #24162 by vlad_vy

Replied by vlad_vy on topic Support for walkera telemetry.

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

Last edit: 20 Jun 2014 08:13 by vlad_vy.

PhracturedBlue
Offline

20 Jun 2014 12:54 #24166 by PhracturedBlue

Replied by PhracturedBlue on topic Support for walkera telemetry.

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.

vlad_vy
Offline

23 Jun 2014 04:43 - 23 Jun 2014 04:47 #24185 by vlad_vy

Replied by vlad_vy on topic Support for walkera telemetry.

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.

Last edit: 23 Jun 2014 04:47 by vlad_vy.

vlad_vy
Offline

30 Jun 2014 16:51 #24314 by vlad_vy

Replied by vlad_vy on topic Support for walkera telemetry.

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

PhracturedBlue
Offline

01 Jul 2014 13:29 #24326 by PhracturedBlue

Replied by PhracturedBlue on topic Support for walkera telemetry.

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:

        if ((reg & 0x23) == 0x22)
        //if(CYRF_ReadRegister(0x07) & 0x20)
        { // this won't be true in emulator so we need to simulate it somehow
            if((CYRF_ReadRegister(0x07) & 0x01) == 0) {
                CYRF_ReadDataPacket(packet);
                parse_telemetry_packet(packet);
                delay = 100 * (16 - txState);
                txState = 15;
            }
        }

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.

vlad_vy
Offline

02 Jul 2014 04:22 #24345 by vlad_vy

Replied by vlad_vy on topic Support for walkera telemetry.

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.

linux-user
Offline

27 Jul 2014 19:31 #24856 by linux-user

Replied by linux-user on topic Support for walkera telemetry.

Hi,
I can confirm that telemerty isn't working anymore. See #533 .
The original issue #525 was at least partly related to a defektive HW-module.

Aziris
Offline

22 Aug 2014 18:51 #25352 by Aziris

Replied by Aziris on topic Support for walkera telemetry.

Hi,

You say telemetry in not working (connection/precision issue).
On 4.0.1 I see that telemetry is disabled. Is there a way to enable it and see if its any better for me, or its disabled for good in this firmware ?

Aziris
Offline

22 Aug 2014 20:25 #25353 by Aziris

Replied by Aziris on topic Support for walkera telemetry.

Sorry, it is working (on table)...

I loaded MiniCP model from this site model files and there was telemetry set to off (went into USB mode and changed value directly in the model ini file)

Time to create page: 0.190 seconds

Re-enable mobile display