[SOLVED] Telemetry problem with Tribunus and FrSky

[ZeXx86]

Thank you very much for the link.

We are awaiting FrSky developer to contact us, since we have no contact to them. It would be very helpful, because I have no idea about 100ms.
Data are sent within 5ms always after request, while telemetry is sent at 85ms period.

[azaz44]

Thank you very much for the link.

We are awaiting FrSky developer to contact us, since we have no contact to them. It would be very helpful, because I have no idea about 100ms.
Data are sent within 5ms always after request, while telemetry is sent at 85ms period.

Speaking about times, do you think it is possible to take advantage of faster telemetry rates in ACCESS? If integration scripts would work faster, that would be a great advantage.

[ZeXx86]

With F.Port telemetry is working much faster already. We have no documentation from FrSky that is describing a faster communication with ACCESS.

[nenno]

Hi there...

i have the same issues with a Frsky Archer R6. I think all Archer-Receivers have this problem except the Archer RS.
Until now I still haven't dared to fly like this. Would be great if this problem is fixed.

With F.Port telemetry is working much faster already.

The spirit already supports f.port?

Regards - Nenno

[swash23]

Hi there...

i have the same issues with a Frsky Archer R6. I think all Archer-Receivers have this problem except the Archer RS.
Until now I still haven't dared to fly like this. Would be great if this problem is fixed.

With F.Port telemetry is working much faster already.

The spirit already supports f.port?

Regards - Nenno

The Spirit GT does support f.port https://www.rc-batteri.no/spirit-gt.html . The GT is not yet available, but can be preordered.

[nenno]

The Spirit GT does support f.port https://www.rc-batteri.no/spirit-gt.html . The GT is not yet available, but can be preordered.

Is this Function planned for the Spirit Pro too?

Regards - Nenno

[azaz44]

Thank you very much for the link.

We are awaiting FrSky developer to contact us, since we have no contact to them. It would be very helpful, because I have no idea about 100ms.
Data are sent within 5ms always after request, while telemetry is sent at 85ms period.

@Thomas did FrSky contact you about this issue?

[Airbo]

Hello,

we recommend to not fly because apparently signal is lost randomly. New firmware resolved the issue it seems.

Is this statement obsolete now with firmware 3.3.0 ?

Thanks

[azaz44]

Hello,

we recommend to not fly because apparently signal is lost randomly. New firmware resolved the issue it seems.

Is this statement obsolete now with firmware 3.3.0 ?

Thanks

I think he meant FrSky firmware, not Spirit.
@Thomas: did you get in contact with FrSky?

[azaz44]

Ok, I see there are updated in newer firmware which could fix this issue. I'll check first. Unfortunately need to rebuild the heli after crash first...