Horus X10 E ACCESS radio does not regain control of receiver after going into EM (Recovery Mode) ETX V2.10RC3

[BompaBert]

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

By scrolling to and selecting a model in the model manage screen, radio went into EM. Power off/on required to get out of the situation- chosen model was not selected.
See also issues / fixes #3603, #3599 and #4940.

Expected Behavior

Upon triggering EM, radio should regain control of the receiver within a few seconds.

Steps To Reproduce

1. Open manage model screen - long enter [MDL].
2. Scroll through models and select one by pushing [ENTER}

Version

Other (Please specify below)

Transmitter

FrSky X10 Express / X10S Express (ACCESS)

Operating System (OS)

No response

OS Version

No response

Anything else?

No response

[pfeerick]

If I make you some test firmware for 2.9.4 and 2.10.0-RC4, that will cause a EM on demand, are you in a position where you can test if your receiver(s) will respond when the radio comes back up in emergency mode? i.e. do you have a setup that can safely have no signal from handset when on the ground? It could be as simple as grabbing another receiver, BEC and servos, and making a small test platform to see if you get controls back, and setup a new model on the transmitter just for that. This will help us determine whether this issue is new for 2.10, or also exists in 2.9.x.

[BompaBert]

Yes, am glad to be of help. 

[pfeerick]

Okey dokey... when you come onto github to read this message, you'll find attached a zipfile with a 2.9 and 2.10 firmware for the X10 Express

With these firmwares, there is an additional special function you can access, bottom of the list of functions, simply called "Test". Once that special function is enabled and active/triggered, the radio should crash pretty much straight away... i.e. I usually make the active condition my moment switch if I need to use it. I would get your RF link all sorted out, setup the special function, and then restart the radio (to ensure everything is saved, as any unwritten configuration settings may be lost). Then you won't have to re-add the special function if it gets clobbered. Then you can trigger the special function when you are ready, and see what happens.

x10-express-debug-firmwares.zip

[BompaBert]

@pfeerick, with both firmware's test function, the radio goes into 'emergency mode', throttle and all control surfaces drop and as expected control is regained after a few seconds. For the test, the same airplane and identical configuration was used as it was when control was lost. Good to know though, the 'sticky' function drops too but does not come back as it needs triggered again - a bit of a challenge with no visual control or sound. Also, with your firmware 'Emergency Mode' is displayed while it was 'Recovery Mode' previously.

[3djc]

So all seems according to expectations

[BompaBert]

Yes, just that it puzzles me why am seeing 'Emergency mode' instead of 'recovery mode'. Has this been changed in the debug firmware's?

[3djc]

The 'recovery' word is not part of EdgeTx at all, so if you saw it, it was coming from a lua of some kind

[BompaBert]

All lua's on the radio are from our website downloads page, no customs. It baffles me that a lua could put the radio, besides not regaining control and different wording, into exactly the same EM situation as experienced in today's test -black screen and the need of a power off/on to regain control.

[pfeerick]

Thanks for testing that... so it looks like Emergency mode is working correctly, and bringing back the link and mixer - no UI or Lua. I can't remember if logical switches or special functions will funciton... but I would operate on the basis that they won't - only simple mixer controls. Even if they did, they would be in the same state they were when the radio turns on, not how they were before the reset.

Ok, lets re-wind a for minute... so you are saying you had a black screen with white text saying "Recovery Mode" instead of "EMERGENCY MODE" when you were having issues before? Specifics matter here. Since as JC said, "recovery" does not appear in any form in the firmware that would be shown on screen - not even for translated firmware. And if a Lua shows it, you're not in Emergency Mode, as Lua does not function at all.

[BompaBert]

Yes, confirmed, screen was showing 'recovery mode'. The logicals work in emergency mode as well. I use a button with sticky with an edge and a special function to enable and disable throttle. EM drops the sticky but I could re-enable it again in EM.

[pfeerick]

Hm... have absolutely no idea where that is coming from then! 😖 There is no text "recovery mode" at all in the project source *at all, and the nearest match is recover, but this is a completely difference screen (i.e. similar to the throttle/switch warning alerts), which also explains that radio settings are corrupt, etc, not simple black and white screen.

[BompaBert]

Got the radio working on 2.10RC4. Will inform you once I get an EM again.