Depending on combination of S.Port sensors there are still a lot of telemetry errors with the current ACCST V2.1.x and ACCESS V2.1.x FrSky Firmware, even the new Archer GR8 is affected.
see the details on Github: https://github.com/FrSkyRC/Firmware-Test/issues/83
Is it possible that this errors or some if this errors happen on TX side? ISRM, OpenTX?
I don't think so, but I'm not sure because I don't know the details. Enable or Disable the vario in the G-RX6 makes a big difference, so I really think the error is in the RX.
Is there a "simple" debug function in OpenTX which would help to locate the error?
Has the data 0x1A or 0x0100101A a special meaning in the telemetry stream?
Reto
wrong telemetry data with ACCST + ACCESS V2.1.x
Re: wrong telemetry data with ACCST + ACCESS V2.1.x
I found out a little bit more how this telemetry errors could occur. 2 parts of different telemetry messages are mixed up, probably because messages are read out of a stream buffer before the message was written completely into it. And so the second part of the telemetry message contains "random" old telemetry data from last buffer use/cycle. I still think this happens in the RX.
The last time requested data 0x0100101A is Little-Endian the "SPort-encoded" Message from the internal Alt sensor of the RX.
See the Details on Github: https://github.com/FrSkyRC/Firmware-Tes ... -683060859
If somebody has a TX with enabled debug/trace functions running, it would be interesting if or how many times the message "sportProcessTelemetryPacket(): checksum error " appears.
Bench testing with perfect rf conditions a G-RX6 (FW-ACCESS_G-RX6_v2.1.0_200519) and 3 sensors (MLVSS, RB10, SM GPS-Logger 3) genreates about 7 "not detected" errors/hour. So I assume the checksum prevents a lot more.
But I hope FrSky will fix it soon ...
Reto
The last time requested data 0x0100101A is Little-Endian the "SPort-encoded" Message from the internal Alt sensor of the RX.
See the Details on Github: https://github.com/FrSkyRC/Firmware-Tes ... -683060859
If somebody has a TX with enabled debug/trace functions running, it would be interesting if or how many times the message "sportProcessTelemetryPacket(): checksum error " appears.
Bench testing with perfect rf conditions a G-RX6 (FW-ACCESS_G-RX6_v2.1.0_200519) and 3 sensors (MLVSS, RB10, SM GPS-Logger 3) genreates about 7 "not detected" errors/hour. So I assume the checksum prevents a lot more.
But I hope FrSky will fix it soon ...
Reto
Re: wrong telemetry data with ACCST + ACCESS V2.1.x
I tested with some debug/trace functions. In OpenTX arrive no telemetry data with wrong checksum or out of sync data. (As far as I have understand and tested.) So the wrong telemetry data are packet together in the TX module or RX.
Re: wrong telemetry data with ACCST + ACCESS V2.1.x
Hope this gets looked into,I also received spurious sensor data.