DJT module/S8R binding problem - help! ?

[BigVWfan]

Hey everyone. Being a newbie here, I'll firstly dedicate a few words to introduce myself. English teacher from Ireland, living in lockdown Germany, making a return to aero modelling after many years. Boy, have things moved on since I first flew my Super Sixty in 1973. I thought technology is supposed to make things easier ?

Anyway, to my query. I have an FRSKY X9D with a DJT telemetry module. In my plane, an S8R receiver with a couple of telemetry devices connected.

Despite my best efforts for the last month, it steadfastly refuses to bind. I have watched a hundred videos with varying suggestions: flashing firmware, changing settings, applying jumpers to pins, upgrading open TX, you name it. Still, nothing.

Can anyone help?

 

[Nigel]

Well, first thing that always comes to mind is firmware. Would you mind sharing what you currently have flashed with us?

One thing I just remembered as well: Make sure you're also using the EU versions of the firmware! If you ordered a radio from the US but bought your receiver relatively locally (ie your continent) they may have mismatched firmware per region.

Your radio's ISRM module (or RF board) and receiver must match in version to bind. This is independent of OpenTX version. Here's a helpful little graphic:

In terms of firmware compatibility, it is recommended to go to ACCST V1 for both your radio and receiver. This will simplify matters quite a bit, as all receivers besides the Archer series ship with ACCST V1, making this process easier in the future.

If both your radio and receiver are on ACCST V1, you should select D16 mode, and all you should need to do is power on your receiver with the button held down, then press bind on your transmitter.

I assume you've tried these steps before, but I'd rather cover all the bases before we try to troubleshoot further.

 

[BigVWfan]

Well, first thing that always comes to mind is firmware. Would you mind sharing what you currently have flashed with us?

One thing I just remembered as well: Make sure you're also using the EU versions of the firmware! If you ordered a radio from the US but bought your receiver relatively locally (ie your continent) they may have mismatched firmware per region.

Your radio's ISRM module (or RF board) and receiver must match in version to bind. This is independent of OpenTX version. Here's a helpful little graphic:

View attachment 5300

In terms of firmware compatibility, it is recommended to go to ACCST V1 for both your radio and receiver. This will simplify matters quite a bit, as all receivers besides the Archer series ship with ACCST V1, making this process easier in the future.

If both your radio and receiver are on ACCST V1, you should select D16 mode, and all you should need to do is power on your receiver with the button held down, then press bind on your transmitter.

I assume you've tried these steps before, but I'd rather cover all the bases before we try to troubleshoot further.

 

[BigVWfan]

Hi Nigel

Thanks for the detailed reply. Here is the information you sought to the best of my ability. Please note however, that this Open TX stuff is very new to me and I'm on a steep learning curve here. I understood most of what you said, but I'll draw attention to what I didn't as I go along.

All my equipment comes from Germany. I'm not sure how to prove the provenance of my Taranis Tx but it seems to be a Euro X9D+ with DJT telemetry module fitted. The S8R Rx has a very conspicuous EU LBT sticker on the side. I bought them separately.

I updated the firmware on both, directly from the FRSKY download page, after carefully consulting various YT videos and forums as to what should work.

I flashed my Tx with "opentx-x9d+-eu-lua-noheli-bin" using the Companion s/w from a laptop with USB cable and the Rx with "S8R_ACCST_2.1.0_LBT.frk" via a servo lead to the smart-port, both of these filenames I am reading directly from screen as I type. (I note you recommend ACCST V1, while it seems to me that the latest version is V2, if I'm reading the file name correctly.)

My OpenTX version is 2.3.10 dated 6 October 2020 from the .Org website of the same name.

I now have some questions I'd like to ask, based on some stuff I'm still a bit vague on.

1. Is it necessary to flash my DJT module separately or does flashing my Tx cover everything?

2. As per my original query, are there any known compatibility issues with the hardware combination I just described? Is there a way to find out what actual transmitter I'm using? (I don't know for sure what its full name is). It appears to be a Taranis X9D.

3. What exactly do you mean by ISRM/RF and Rx "matching in version" and how do I verify this? As I explained, this stuff is way new to me.

4. I didn't select D16 mode because stuff I'd read suggested I enable the external DJT module and set it to PPM/22.5 ms.

5. Both the Tx and Rx behave exactly as they should during bind, according to the manual (correct colours blinking, appropriate beeps etc) but they simply will not bind. The blinking and beeping continues ad infinitum as if both are invisible to each other.

This is as much information as I can currently muster. I hope it gives you something to go on.

Thanks for taking the trouble.
Thomas

 

[Konrad]

As the DJT is not a D16 module, you will want to keep both the TX RF (DJT) and RX flashed for FW ACCST v.1.1.x This is how the RX and TX talk to each other. Both RX and TX need to have the same RF Firmware flashed ACCST Vx.x.x (V1.1.x)
(As the DJT does not support D-16, I see there is no ACCST 2.1.0 firmware update,( none needed)

OpenTX is how the TX talks (interfaces) with you. see Aloft graphic Nigel posted. Is there a reason you want to be running such a high OpenTX version number (2.3.10)?


Yes, you need to flash the internal or external RF module separately from the human Interface software (OpenTX). They are two separate functions and software.

If you aren't using D-16 then you don't want "S8R_ACCST_2.1.0_LBT.frk".
Bring your receiver back to ACCST v.1.1.x See firmware history link

S8R - FrSky - Lets you set the limits

www.frsky-rc.com

In europe: S8R_LBT_20190531.frk

I have to ask are you running an internal RF module? I gather you are running an external RF module DJT

 

[BigVWfan]

As the DJT is not a D16 module, you will want to keep both the TX RF (DJT) and RX flashed for FW ACCST v.1.1.x This is how the RX and TX talk to each other. Both RX and TX need to have the same RF Firmware flashed ACCST Vx.x.x (V1.1.x)
(As the DJT does not support D-16, I see there is no ACCST 2.1.0 firmware update,( none needed)

OpenTX is how the TX talks (interfaces) with you. see Aloft graphic Nigel posted. Is there a reason you want to be running such a high OpenTX version number (2.3.10)?


Yes, you need to flash the internal or external RF module separately from the human Interface software (OpenTX). They are two separate functions and software.

If you aren't using D-16 then you don't want "S8R_ACCST_2.1.0_LBT.frk".
Bring your receiver back to ACCST v.1.1.x See firmware history link

S8R - FrSky - Lets you set the limits

www.frsky-rc.com

In europe: S8R_LBT_20190531.frk

I have to ask are you running an internal RF module? I gather you are running an external RF module DJT

To briefly answer your question, I'm running the version numbers I listed, because in every other example in which updates are applied, my Android phone, my Windows laptop, my numerous smartphone apps, and any device of mine which is constantly being improved or developed, the latest version is by definition the best one. Are you suggesting that I abandon this guiding principle for my aero modelling efforts? Genuine question.

 

[BigVWfan]

I'm now more confused than ever. Revisiting the download area of the website, shows only one version, the most recent, to be available.

 

[Konrad]

There is s a small link at the bottom that says history firmware DOWNLOAD (not compatible with 2.x.x).

This is for the RX S8R. As the DJT doesn't support D-16 there is no ACCST v2 for this module.

 

[Konrad]

To briefly answer your question, I'm running the version numbers I listed, because in every other example in which updates are applied, my Android phone, my Windows laptop, my numerous smartphone apps, and any device of mine which is constantly being improved or developed, the latest version is by definition the best one. Are you suggesting that I abandon this guiding principle for my aero modelling efforts? Genuine question.

Sincere answer, NO.

I rarely upgrade. I upgrade if there is a known issue that effects my application (situation). Most FW updates introduce more issue than they solve. So if it an't broke don't fix it. This is true of my computers down to my toys.

Now OpenTX offers free updates more as a way to offer new feature sets than anything else. If I'm not interested or if my hardware can't support the feature I don't upgrade. I really like OpenTX 2.2.4

FrSky firmware is very very buggy I avoid it like the plague! If I need to for safety reasons, like the D-16 un-commanded control issue (faulty packet pass), I'll upgrade but only after FrSky's firmware has been vetted for a few months. I think with the ACCST v2 it took 9 month and a plethora of revisions to reach ACCST v2.1.1 (TX is running v2.1.0 and some RX have a minor up date to that running ACCST v2.1.1)

I love OpenTX that is why I'm running FrSky. I have a love hate relationship with FrSky's engineering. They don't have a robust validation/QA system.