Hello,
usually it is enough to enable ESC telemetry and then scan for new sensors in the radio.
Please note some receivers have limited FPort support. So with some it might not work and can be used only for channel transmission.
These receivers are limited by memory so FrSky maybe was unable to implement it fully.
Using SPort or different receiver can resolve the problem.
We found that X4SB has limited FPort for example.
[SOLVED] No telemetry variables by FPort1 use
Spirit System developer
Hi rburrow87,
today the flashing works with the original Radiomaster cable (changed polarity (Plus and Minus) temporarily) in the external module bay of the TX16S, also I made an extra model with external and internal Module deactivated (off) and that works great
Regards
Matthias
today the flashing works with the original Radiomaster cable (changed polarity (Plus and Minus) temporarily) in the external module bay of the TX16S, also I made an extra model with external and internal Module deactivated (off) and that works great
Regards
Matthias
Hello Tomas,
today I have flashed sucessfully the Radiomaster Reciever R161 to LBT Firmware for F.Port use - D16 v2.1.0 with the original Radiomaster cable (changed temporaryily polarity plus an minus) and with the TX16S in the external module bay - And now all telemetry variables are visible !
Regards
Matthias
today I have flashed sucessfully the Radiomaster Reciever R161 to LBT Firmware for F.Port use - D16 v2.1.0 with the original Radiomaster cable (changed temporaryily polarity plus an minus) and with the TX16S in the external module bay - And now all telemetry variables are visible !
Regards
Matthias