Incorrect evaluation of CRSF_FRAMETYPE_LINK_RX_ID messages

[wimalopaan]

Is there an existing issue for this problem?

• I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

The value of "uint8_t uplink (sic) RF power index" is displayed as is.

Expected Behavior

The value of "uint8_t uplink (sic) RF power index" should be looked up in the power-index-lookup table

Steps To Reproduce

Use a device that produces that kind of telemetry messages and show the sensor in EdgeTx.

Version

Nightly

Transmitter

RadioMaster TX15

Operating System (OS)

No response

OS Version

No response

Anything else?

No response

[pfeerick]

Just a FYI, 2.12.0-RC does not exist yet.

…

On Sat, 20 Dec 2025, 12:54 am Wilhelm, ***@***.***> wrote: *wimalopaan* created an issue (EdgeTX/edgetx#6889) <#6889> Is there an existing issue for this problem? - I have searched the existing issues What part of EdgeTX is the focus of this bug? Transmitter firmware Current Behavior The value of "uint8_t uplink (sic) RF power index" is displayed as is. Expected Behavior The value of "uint8_t uplink (sic) RF power index" should be looked up in the power-index-lookup table Steps To Reproduce Use a device that produces that kind of telemetry messages and show the sensor in EdgeTx. Version 2.12.0-RC Transmitter RadioMaster TX15 Operating System (OS) *No response* OS Version *No response* Anything else? *No response* — Reply to this email directly, view it on GitHub <#6889>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJ66KK6OFU3TN3FPCFN4JD4CQGRVAVCNFSM6AAAAACPRSPFFKVHI2DSMVQWIX3LMV43ASLTON2WKOZTG42DONZZGIYDENI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[wimalopaan]

Just a FYI, 2.12.0-RC does not exist yet.
…

Well, I think it is not dependent on the version ...

[3djc]

How are we supposed to know the values in said tables? They might vary by device and or firmware on device (lbt/eu)

[wimalopaan]

How are we supposed to know the values in said tables? They might vary by device and or firmware on device (lbt/eu)

Should be the same as here:

edgetx/radio/src/telemetry/crossfire.cpp

Lines 275 to 280 in c795b76

	if (i == TX_POWER_INDEX) {
	static const int32_t power_values[] = {0, 10, 25, 100, 500,
	1000, 2000, 250, 50};
	value =
	((unsigned)value < DIM(power_values) ? power_values[value] : 0);
	}

[wimalopaan]

The enums are defined: https://github.com/crsf-wg/crsf/wiki/CRSF_FRAMETYPE_LINK_STATISTICS

[3djc]

Unsure what we are talking about here, where in CRSF frame are you looking at ?

In https://github.com/tbs-fpv/tbs-crsf-spec/blob/main/crsf.md#0x14-link-statistics, we have:

     uint8_t     up_rf_power;        // enum {0mW = 0, 10mW, 25mW, 100mW,
                                    // 500mW, 1000mW, 2000mW, 250mW, 50mW}

but I see no reference to a corresponding RX based one.

The closest thing would be in : https://github.com/tbs-fpv/tbs-crsf-spec/blob/main/crsf.md#0x1d-link-statistics-tx

   uint8_t rssi_db;        // RSSI (dBm * -1)
    uint8_t rssi_percent;   // RSSI in percent
    uint8_t link_quality;   // Package success rate / Link quality (%)
    int8_t  snr;            // SNR (dB)
    uint8_t rf_power_db;    // rf power in dBm

But it is in dBm