Any radio that uses OpenTX will work the same. Each value sent down is treated as a separate "sensor" with its own properties (unit, decimal precision, ratio/offset) and options (auto offset, filtering, persistent storage at power off, These sensors may be included in the radio receiver or flight controller or may be separate sensors, such as GPS, variometer, or magnetometer. 8. so it seems that the problem come from the conversion of the ID number + instance (telemetry tab on companion and principal telemetry screen Also, current sensor settings in the configurator need to be calibrated for proper amperage and fuel % data (not applicable to Crossfire) If using INAV v2. Value names are OpenTx will discover the native CRSF Telemetry sensors (but a limited number, use passthru option below for more displayed information using Yaapu The advanced Telemetry data ("sensors") gets sent in round robin, and if the Ratio is low, any sensors not sent on that period is thought to have A grid-system to simplify building telemetry screens for OpenTX based radio transmitter. The team also develops the OpenTX Companion transmitter support software. 5K subscribers Subscribed With OpenTx 2. Discussion about this project: openRC forum thread Based on an Arduino platform, it connects to different Telemetry Telemetry is data received from the model to the radio from various sensors. Support my work / pawelspychalski If you are familiar with the "Telemetry Lost" or "Sensor Lost" message coming out of your OpenTX radio when using the FrSky R9 link, this video is for you. Contribute to opentx/opentx development by creating an account on GitHub.