Byte 39 (after the error flags) is GPS_accH. The value is factor 20 compared to that what is shown in flight logs (telemetry).
bit5 and 6 in nsat should be GPS fix type but will not provided by Typhoon H. I saw it always as 0. Bit 7 (the highest) is "GPS used" as you have it already implemented. Error flags 1, 2 and 32 are common used, the other seems to depend on vehicle type. I saw a message about 8000ft limitation the Typhoon not has.
IMU status (byte 34), pressure_Compass_staus (byte 35) still needs some further investigations. My thoughts are in q500log2kml manual (chapter 3.3).
Need to check the reactions of the ST16 on the different values deeper soon. With the SR24 on Raspberry PI I have now a good tool to feed the St16 with all, also useless, informations an look whats going on. Flight logs will be created as soon as telemetry messages arrive.
----------------
@Pöllö: I use the latest FW for a long time without problems. But I have destroyed something due to bad battery. It is difficult to observe a fast drone during "sport flying" and look at the same time on the tiny voltage display.
That#s why I would like to have the Voltage Warnings on the ST16. ST16 ignores the voltage value and reacts only on the error flags.
This means:
BAT_LOW_THR --> Voltage warning 1; bit 0 in byte 38 of the telemetry message is 1
BAT_CRIT_THR --> Voltage warning 2; bit 1 in byte 38 =1
It would be very nice to send those error flags via telemetry. ST16 will be warn by vibration alarm.
br HE