Advanced Search

rklunder wrote: Count me in with issues with the F12E and nightly builds. I have not been able to get one to work as of yet. How do you manually copy the devo.fs over? I dont see a download for the F12E in the stable folder, is that not available yet?

vlad_vy wrote:

hexfet wrote: I don't see sign to distinguish DD.DDDDDD from DD MM.MMMM.

Yes doesn't seem to be any way to detect this. I have been looking at videos online from users using the stock firmware and it seems that the GPS is being sent like this for all Walkera models. Here is an example video from someone using Walkera Tali H500. The latitude degree minute in the video is 69 which is not normalized.

Tali H500

Maybe it would be possible to add a configuration for the GPS format, so that we can select either DDMM.MMMM or DD.DDDDDD?

hexfet wrote: Thanks that's very helpful.
kbg, what is your actual GPS longitude (from cell phone or other source)? Maybe the QR-X350 is not normalizing the value correctly for some reason. In the images you posted the latitude is the same in deviation and stock firmware.

The altitude is bouncing around 3-4 meters. Is that correct?

The speed data is "9999.90000.0". Not obvious how to decode that. Is it possible to record some data with the aircraft moving?

The timestamp telemetry doesn't have any data - all nulls. Was the GPS "locked" with enough satellites for a good link?

hexfet wrote: The longitude telemetry string is "02186.3545W".

    if (packet[0] == 0x32) {
        update = gpslongpkt;
        Telemetry.gps.longitude = text_to_int(&packet[1], 3) * 3600000
                                + text_to_int(&packet[4], 2) * 36000;
                                + text_to_int(&packet[7], 4) * 36 / 10;
        if (packet[11] == 'W')
            Telemetry.gps.longitude *= -1;
    }

    if (packet[0] == 0x33) {
        update = gpslatpkt;
        Telemetry.gps.latitude = text_to_int(&packet[1], 2) * 3600000
                               + text_to_int(&packet[3], 2) * 36000;
                               + text_to_int(&packet[6], 4) * 36 / 10;
        if (packet[10] == 'S')
            Telemetry.gps.latitude *= -1;
    }

kbg wrote: I have been trying to update my F12E with Deviation mainly to get persistant telemetry but it seems the current nightly builds are very much broken. Updating using Deviation Uploader 0.9.0 results in a broken filesystem, but I found this can be fixed by manually copying the devo.fs over. Going through the menu sometimes results in getting stuck in submenus, and the only way to recover is to turn off transmitter. The GPS telemetry displayed seems way off, altitude is a large number and the current date is in the year 2048. The GPS coordinates also seem to be offset by a couple of km.

Is there any build available for F12E that is known to be working?