[SOLVED] Telemetry problem with Tribunus and FrSky

[ZeXx86]

Hello,

there were updates in FrSky receiver firmwares that introduced several incompatibilities. Also new ACCESS receivers were working little bit differently.
For this reason we have had to make it compatible again and now it should work well with all of their receivers and the latest firmware.
This apply for 3.3.1 Spirit firmware.

[Airbo]

Thanks a lot for the clarification, this answers my question
M.

[Airbo]

Still "Sensor Lost" with v3.3.1

Hello,

I updated my Spirit (black unit) to v3.3.1, and the Archer R8 pro to v2.1.8. Unfortunately, there are still many, many "Sensor Lost" messages. I then made a cross-check using an RX6R with v2.1.7 (also ACCESS). This worked perfectly, with no "Sensor Lost" messages.

So it seems there is still an issue with the Spirit-connection to some Archer receivers (only the receivers, not the ACCESS protocol itself).

Regards
Airbo

[azaz44]

I updated my stuff to Spirit 3.3.1 and recently released Archer 2.1.8.

It is much better than Archer 2.1.7 -- no sensors lost anymore. But it still has problems, just like early versions of Archer firmware. It looks like this:

https://youtu.be/P7eM71Q1ja0

So works, but telemetry is interrupted sometimes for some seconds.

On FrSky side they closed the issue with comment "Spirit System has fixed the issue on F.port.", although it happens over S.Port.. https://github.com/FrSkyRC/Firmware-Test/issues/121

Is this a problem in Spirit or in FrSky?

[ZeXx86]

Hello,

thank you for the message.

Is the issue happening also with other sensors disconnected?

We have not found any issue at our side sadly. We have made only few improvements, because ARCHER receivers are behaving differently than others for no reason.

[azaz44]

Hello,
Is the issue happening also with other sensors disconnected?

I'm not sure what you mean, but I have no other sensors. There are additional telemetry counters for VSpd and Alt, but this is included in the receiver, because Archer GR8 has a variometer. Maybe 2 extra counters to send is what makes a difference? I don't have any other Archer receiver to try.

[Airbo]

Hello,

as it seems that I have a similar problem as azaz44 I would like to add my observations:

with the setup as described some messages above (latest firmware for Spirit and Archer) I got frequent "sensor lost" messages. As a test I connected an additional voltage sensor in parallel to the Spirit unit, and - surprise, surprise - no more "sensor lost" messages, nor for the voltage sensor nor for the Spirit unit.

I then disconnected the voltage sensor, a corresponding "sensor lost" message appeared, and some seconds later also "sensor lost" for the Spirit showed up.

In a next step I reconnected the voltage sensor, and all "sensor lost" disappeared.

This behaviour was fully reproducible.

So it seems that as long as a second sensor is connected to the Archer in parallel to the Spirit, all works fine.

Airbo

[azaz44]

I just upgraded my Kraken with Archer GR8 and I updated Spirit to latest 3.3.2. The problem is still there. Telemetry works, but with interruptions. Same as in my other Heli which also has Archer GR8, but Spirit 3.3.1.

Will this problem be ever fixed? How can we help??

[ZeXx86]

Thank you for the message.

We will be sending Spirit units to FrSky because we can`t find any error at our side.

[azaz44]

Great, thanks for info. Awaiting results then...