It's offical. My external XJT module in my Taranis X9D doesn't like the new RX series receivers

[Masterpiece]

I have tried the new G-RX6 and RX6R receivers on my Taranis X9D with the external XJT module and they bind beautifully everytime, BUT the module goes into range failure mode beeps (constant beeps), even though the radios RSSI is showing full bar signal reception.
It really sucks and the beeping is so @#$&ing annoying (why have this feature in the module if the radio already does it anyway????).
The module was purchased locally (Austalian vendor) only a month or two ago, but i feel that it's firmware needs updating so this bug can be sorted.
Has anybody else had this same issue with a similar set up? And if so what ideas do you recommend I do so i can use the module with the new "RX" series receivers?

Any feedback is greatly appreciated

Thanks
Glen

PS: the external module works fine with the older "X" series receivers (ie X8R, X6R ..... etc)

 

[Konrad]

The beep is there for radios that are not native to FrSky. These modules are used more often than not in allowing off brand TX's to use FrSky receivers.

The last firmware update seems to deal with LR 12 mode issues
https://www.frsky-rc.com/xjt/

What is the native (internal) Tx RF protocal for the X9D? Or but another way, why do you need the XJT module in a FrSky radio when using less than 8 channels?

All the best,
Konrad

 

[PressAllTheKnobs]

2017-05-21 170317 adds support for bindopts and fixes a Q-X7 bind bug. It is a roll up of a previous update (now withdrawn) that contained the fix described in the notes. It pre-dates the release of the RX-series. The firmware is used for both internal and external XJT modules. I suspect all recently made XJTs have this firmware.

As I understand it the RX- series RSSI value is not as predictable as it is with the X-Series and is reportedly lower. There is speculation that this is due to adaptive sensitivity which will have the effect of reducing the RSSI when the TX is close and increasing it when the TX is further away. This will have the effect of flattening the RSSI vs distance curve and if the sensitivity adjustment is not continuous, may cause the curve to be disjoint.

If a good RSSI from an RX-series is significantly lower than I can see how that that might trigger the stock XJT RSSI warning.

I am unclear if the external XJT module emits the alarm sounds when the PXX is used instead of PWM...seems like it should not since using PXX implies the TX will take control of those features. I don't have one to try. However if you are using an XJT only in PXX mode you could mechanically disable the beeper.

Reading around a bit it seems you can change the stock external XJT alarms with the XJT dashboard...
https://alofthobbies.com/frsky-dashboard-smart-port-data-display.html

I also found that sometimes XJTs develop a beeping fault that can be repaired but there maybe TX-ID caveats...
https://openrcforums.com/forum/view...sid=fbcdb183f917cea26785eac9adadfeb3&start=30

 

[Masterpiece]

Thanks for the quick replies guys ☺

I tried with a X series receiver today (X4R) and surprising am getting the beeping with this series of RX too (on both the internal and external modules), so i figured that it can't be the modules but a setting in the radio. Went through the radio settings but couldn't see anything obvious unfortunately. My next step (and since I only have one model set up on the radio) was to do a factory reset. Long story short ... no more beeping 😊.
Will try and see whilst resetting up the erased model what may have been the beeping issue.

 

[PressAllTheKnobs]

From what I found reading around, the external XJT beeps are not explicitly controllable from the radio except if it is the case that using PXX implicitly disables the beeper.

They can only be explicitly controlled using the Dashboard device.

An OpenTX factory reset will remove all models and reset the Radio setting to default. It will depower the external module bay so if it was the current model that had that active it makes sense that the beeps stopped...its just like you switched off the module.

Note that a factory reset will set the firmware mode back to Mode 1 and reset the default channel order to something. You should change those back to what you expect so that the Mode agrees with your sticks. I recommend using AETR channel for the channel order since that is generally assumed for things made for FrSky (Stability RXs, multimodule-FrSky version firmware)

 

[Masterpiece]

Hi PressAllTheKnobs
Thank you for the explanation. I'm fine with the factory reset option as i only had one model 1/2 set up on the radio, so no big loss. Also I have the fantastic user manual from Aloft too which helped me set up this model so I'll just use that again 😉. And the firmware I'll reload back on too so no issue there (but thank you for the heads up 😉)

 

[Masterpiece]

From what I found reading around, the external XJT beeps are not explicitly controllable from the radio except if it is the case that using PXX implicitly disables the beeper.

They can only be explicitly controlled using the Dashboard device.

An OpenTX factory reset will remove all models and reset the Radio setting to default. It will depower the external module bay so if it was the current model that had that active it makes sense that the beeps stopped...its just like you switched off the module.

Note that a factory reset will set the firmware mode back to Mode 1 and reset the default channel order to something. You should change those back to what you expect so that the Mode agrees with your sticks. I recommend using AETR channel for the channel order since that is generally assumed for things made for FrSky (Stability RXs, multimodule-FrSky version firmware)

Just checked the settings on my radio and only the model setting was reset. The radio is still mode 1 RETA (the flying mode used mostly in Australia), I still have the Amber sound pack, model images downloaded and the firmware is the latest 2.2.2 (as it was before I did the factory reset).
Basically all the factory reset did was reset the model settings. Everything else stayed the same 😊. Bonus

 

[PressAllTheKnobs]

That is all it does.

Mode 1 with RETA new model channel order is the default so if that is what you use then you are in luck. Most people don't and if the firmware Mode and sticks don't agree then weirdness results.

The default channel order only matters if you are planning to use the stabilizer RXs or the Multimodule since they are set up to use AETR