X9D+ SE 2019 and multimodule communication cut off with SF switch when openTX >= 2.3.12

[EddyBag42]

Hi,

I have a Taranis X9D+ SE 2019 (openTX 2.3.14) and an iRangeX IRX4+ multimodule (firmware 1.3.6) I'm facing a fairly critical issue of communication cut off between radio and module.

In serial mode (MULTI), communication between the radio and the multimodule cuts off under reproducible circumstances as follows :

• radio is using external RF
• communication between radio and module is set in serial mode (MULTI)
• receiver doesn't need to be on (though problem may appear quicker when receiver is on, but not sure of this point)
• after several toggles of the 2-positions switch SF (random number of toggles, that can be one or ten, rarely more than a few tens) the communication between the radio and the multimodule cuts off (the radio says "No serial input" and the red led flashes slowly on the multimodule)

I posted this issue to RC Groups thread and it appears that this is not an isolated case, it seems to be related to using multimodule inside X9D+ SE 2019, please see here.

Old openTX versions for X9D+ SE 2019 have been posted on the same thread so I could try and see if issue is still there.

Here are the results of my tests :

• openTX 2.3.13 : issue is present
• openTX 2.3.12 : issue is present
• openTX 2.3.11 : no issue detected
• openTX 2.3.10 : no issue detected
• openTX <= 2.3.9 : not tested

So it seems to me that the issue appeared with openTX 2.3.12 and is there since.

Thanks for your help. Best regards.

Remark : no issue with another switch than SF, no issue with PPM communication mode, no issue with SF switch when using internal RF, no issue with an X9D, seems specific to X9D+ SE 2019 + multimodule + serial mode + SF switch

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[EddyBag42]

Cut off bug still present with openTX 2.3.15

[gratefulfrog]

I confirm that this bug is there and terrible

[gratefulfrog]

any progress??

Thanks, B

[gratefulfrog]

Hello? Is there any way to help you guys with this issue? It is really hurting me...

[HippoDan]

This is still an ongoing problem. Lost a plane this week because of it. Going back to 2.3.11 for the time being. Please fix this, I don't want to be stuck on older firmware forever.

[bsongis]

Do you use SF for anything? Like screenshot

[gratefulfrog]

Yes, I use SF for throttle cut on all my models.

Thanks for your help, it would be great to fix this so we can move to the latest version of open-tx!

On Thu, 21 Sept 2023, 15:55 Bertrand Songis, @.***> wrote:

Do you use SF for anything? Like screenshot

— Reply to this email directly, view it on GitHub https://github.com/opentx/opentx/issues/8786#issuecomment-1729636953, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOUDF74ZR43AE4P73WSIM3X3RBM3ANCNFSM5JB3PY7Q . You are receiving this because you commented.Message ID: @.***>

[bsongis]

Would you share your eeprom here?

[bsongis]

Do you reproduce if you use SF for nothing? And on a blank model?

[gratefulfrog]

Yes, it still happens on a blank model with nothing assigned to SF.

On Thu, 21 Sept 2023, 17:12 Bertrand Songis, @.***> wrote:

Do you reproduce if you use SF for nothing? And on a blank model?

— Reply to this email directly, view it on GitHub https://github.com/opentx/opentx/issues/8786#issuecomment-1729786291, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOUDF2A4IUP4WBNJGOZQ4DX3RKO7ANCNFSM5JB3PY7Q . You are receiving this because you commented.Message ID: @.***>

[gratefulfrog]

I am happy to share my eeprom, but how do I do it? Is it available on the SD card?

On Thu, 21 Sept 2023, 17:12 Bertrand Songis, @.***> wrote:

Would you share your eeprom here?

— Reply to this email directly, view it on GitHub https://github.com/opentx/opentx/issues/8786#issuecomment-1729785506, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOUDFYIJFUHTK3H2T4ICUTX3RKNHANCNFSM5JB3PY7Q . You are receiving this because you commented.Message ID: @.***>

[HippoDan]

Do you use SF for anything? Like screenshot

I like my momentary switch on the left, and I use it to call out my timer among other things. It gets pressed a lot for timer, gun sound effects, self level and more. Started having the problem right away, but it took forever for me to figure out what was happening.

[gratefulfrog]

So are you able to work on a bug fix? This problem has been open for a while and no one seems to be looking at it...

I would look at the code, but it would take me so long to dive in... I hardly have the time.

Let me know about the EEPROM if you could use it - it is version 219 I think

On Thu, 21 Sept 2023 at 18:52, HippoDan @.***> wrote:

Do you use SF for anything? Like screenshot

I like my momentary switch on the left, and I use it to call out my timer among other things. It gets pressed a lot for timer, gun sound effects, self level and more. Started having the problem right away, but it took forever for me to figure out what was happening.

— Reply to this email directly, view it on GitHub https://github.com/opentx/opentx/issues/8786#issuecomment-1729955508, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOUDF7UWNRVTAAUQWKS7FTX3RWFTANCNFSM5JB3PY7Q . You are receiving this because you commented.Message ID: @.***>

[Ceeb182]

The EEPROM is the complete copy of the radio's contents (models + radio configuration + OpenTx firmware).

To obtain the EEPROM and attach it here in a message:

1. Install Companion 2.3 software on a PC
2. Put the radio in "Bootloader" mode (press the two horizontal trims towards the center while powering up the radio, the screen will turn on with "OpenTx Bootloader" in the title bar).
3. Open the Companion software on PC (if the software suggests updates, ignore them for the moment, i.e. answer "No" twice).
4. Connect the radio via USB to the PC. The radio displays "USB Connected".
5. In Companion software, go to menu: Read Write > Backup Radio To File
6. Choose an explicit file name (Example: "OTX2313-BugSF-ModelName.bin")
7. Companion displays a bar graph showing the progress of the EEPROM transfer to the file "OTX2313-BugSF-ModelName.bin".
8. Attach the file to this issue's message (by dragging and dropping "OTX2313-BugSF-ModelName.bin" in the message)
9. Specify in the message: radio type, radio's OpenTx version, model name.
10. And that's it!

[bsongis]

Someone reproduces the issue with a radio with the small external module bay? because I only have the small Multimodule ...

[gratefulfrog]

As requested, I attach my EEPROM File, but please note that this is OTX version 2.3.11 which is the most recent version that DOES NOT HAVE THE BUG.

The bug is present in all versions 2.3.XX where XX > 11.

I do not use the more recent version because of the bug!

My firmware is: FW: opentx-x9d+2019 VERS: 2.3.11-OTX (4328055e) Date: 2021-01-08 23:44:58 EEPR: 219

I hope this helps, I am so glad that you guys are working on it. Let me know if I can help, I am a good programmer and debugger... Cheers, Bob

On Thu, 21 Sept 2023 at 22:05, Bertrand Songis @.***> wrote:

Someone reproduces the issue with a radio with the small external module bay? because I only have the small Multimodule ...

— Reply to this email directly, view it on GitHub https://github.com/opentx/opentx/issues/8786#issuecomment-1730224792, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOUDF5LTXWOMRGSGOKADM3X3SMYNANCNFSM5JB3PY7Q . You are receiving this because you commented.Message ID: @.***>

[bsongis]

Searching for a module to reproduce the problem ...

[bsongis]

Now I have X9D+ updated to latest 'master', compiled with a recent compiler (the one I use for Ethos) I have a multimodulle in version 1.3.3.20 AETR I cannot reproduce the problem

[bsongis]

Now the same opentx, compiled with the old good compiler. I cannot reproduce the problem.

[bsongis]

Now the official firmware downloaded from companion. I cannot reproduce the problem. I have not bound the RX, should I? Which OpenTX options did you choose?

[bsongis]

@gratefulfrog can you also share your eeprom here?

[bsongis]

Now with the official firmware downloaded from companion and bound with a Spektrum AR410. I cannot reproduce the problem

[EddyBag42]

On Fri, Sep 22, 2023, 06:44 Bertrand Songis @.***> wrote:

Now I have X9D+ updated to latest 'master'

Hi, Is it a X9D+ SE 2019 ? You will not have thé problem with a regular X9D+. Cheers.

Ed

[bsongis]

Yes of course

[bsongis]

[bsongis]

No luck, I have the multimodule marked as "No problem" I also have the iRX4 lite, searching for a way to connect it to the fullsize module slot...

[3djc]

On Fri, Sep 22, 2023, 06:44 Bertrand Songis @.***> wrote: Now I have X9D+ updated to latest 'master' Hi, Is it a X9D+ SE 2019 ? You will not have thé problem with a regular X9D+. Cheers. -- Ed

At this point in time, we cannot reproduce and we spend time going through all the differences between 2.3.11 and 2.3.12 and found nothing that could explain that

[3djc]

On Fri, Sep 22, 2023, 06:44 Bertrand Songis @.***> wrote: Now I have X9D+ updated to latest 'master' Hi, Is it a X9D+ SE 2019 ? You will not have thé problem with a regular X9D+. Cheers. -- Ed

If you have the issue too, an eeprom back would be helpful

[bsongis]

Now testing with iRX4, bound to the AR410 Still no issue