Determining TXID from Betaflight frsky_spi_tx_id

Hi guys, i did some searching, but didnt get any useful results. I know i can set the txid in hardware.ini, and there is a fixed id in the models, but what i'd like to do is match the txid on my Jumper T8SG V2 Plus with that of my other radio (Betafpv Lite Radio2) which uses OpenTX and an external SBUS module, unknown what FW that uses.

In the betaflight dump there is a value frsky_spi_tx_id, and apparently this allows the quad to remember its bind info; but the problem is that number is very low...

This is from my Jumper T8SG V2 Plus
set frsky_spi_tx_id = 13,82
set frsky_spi_offset = -36
set frsky_spi_bind_hop_data = 2,212,187,162,137,112,87,62,37,12,222,197,172,147,122,97,72,47,22,232,207,182,157,132,107,82,57,32,7,217,192,167,142,117,92,67,42,17,227,202,177,152,127,102,77,52,27,0,0,0

And this is from the Lite Radio 2
set frsky_spi_tx_id = 105,99
set frsky_spi_offset = 23
set frsky_spi_bind_hop_data = 0,17,34,27,49,21,30,52,75,54,14,45,7,29,64,23,8,46,40,66,3,59,31,74,68,48,71,32,56,15,51,24,55,16,60,10,53,28,5,19,57,6,69,13,61,22,58,0,0,0
set frsky_x_rx_num = 0

Is there any way of determining the Lite Radio's TX ID from that number 105,99 so i can match it in hardware.ini on my Jumper? I dont mind rebinding (I only have 3 Frsky models) but i want to be able to use either tx without having to rebind.

According to the Betaflight documentation, the txid is the internal number from the transmitter:
* the RX bind information is stored in the following CLI parameters: frsky_spi_tx_id (internal TX id), frsky_spi_offset (frequency offset), frsky_spi_bind_hop_data (frequency hop sequence), and frsky_x_rx_num (RX number; FrSky X only). These are printed as part of a CLI diff / dump, and will be restored after a firmware update, making it unnecessary to do another bind after the update;

Not sure if it helps you in your search, but between Deviation radio's you can put foloowing commend line in hardware.ini (by default I understnd Tx code is random, but you can set it fixed in multiple Deviation Tx and control the model with multiple transmitters, but it also means transmitters clash when multiple TX are switched on with same ID at same time.


I have it in my ini files, but normally disabled.

---

;Unique TxId, With tx same id and model bind Id, the rx can be controlled by multiple Tx 00000000 - FFFFFFFF
;txid = 78968765

---

Thanks, yes if both radios were deviation, that would be fairly easy. The problem is this radio is OpenTX (and even then, its using an 'external' SBUS module). I could get around this by replacing that SBUS module with a DIY Multiprotocol module (where you can compile your own TXID into the firmware). but the cost of that module is more than this Lite Radio is worth haha.