EdgeTX
Flysky el18/nv14 Switch Function Lost
Is there an existing issue for this problem?
- [x] I have searched the existing issues
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
Flysky EL18 EdgeTX 2.11RC3. The switches stop working at random intervals. Sometimes for 20 minutes, sometimes for an hour. It's very dangerous if the copter won't let you disarm.
Note (Richard Li): We have received several reports about this symptom, the switches will suddenly stop responding and can be recovered by a power cycle.
Expected Behavior
Flysky EL18 EdgeTX 2.11RC3. The switches stop working at random intervals. Sometimes for 20 minutes, sometimes for an hour. It's very dangerous if the copter won't let you disarm.
Steps To Reproduce
Dont know
Version
2.11.0-rc
Transmitter
Flysky EL18
Operating System (OS)
macOS
OS Version
Latest
Anything else?
No response
The symptom can be related to hardware cabling connectivity problem, did you check this? Can downgrading to 2.10 solves the problem?
I don't think it's a hardware issue. All switches are affected, and the rear ones are connected to a different board. I'll have to test whether a downgrade fixes the problem. Apparently, there was a problem with 2.11 that was supposed to be fixed with RC3. I'll try upgrading to 2.10 in the next few days.
The symptom can be related to hardware cabling connectivity problem, did you check this? Can downgrading to 2.10 solves the problem?
With 2.10.6 all Fine. Over 30 Flights no Switch Problem.
BTW, can you try to build with el18-old target and have a try? There is a change in 2.11 that use a single pl18 target to support all Flysky F4 radios. But I do not think this change will affect the switches.
Please test the release version 2.11.0 to see if the problem persists. Or wait for the 2.11.1 releases, should be out soon.
I can confirm the issue with 2.11.0 and NV14.
Can the problem be reproduced by switching on the radio and wait for 1-2 hours doing nothing? Or requires one to move.the gimbals/switches to reproduce?
I can confirm the issue with 2.11.0 and NV14.
Can the problem be reproduced by switching on the radio and wait for 1-2 hours doing nothing? Or requires one to move.the gimbals/switches to reproduce?
I've kept the radio on for 3 hours without touching anything. Switches were working.
Check if 2.11.1 fixes the problem. There are quite a few critical bugs and fixed in 2.11.1, so not sure if the problem is gone or not.
I can confirm the issue with 2.11.0 and NV14.
Can the problem be reproduced by switching on the radio and wait for 1-2 hours doing nothing? Or requires one to move.the gimbals/switches to reproduce?
I've kept the radio on for 3 hours without touching anything. Switches were working.
So one must operate the radio to repeat the problem, right?
So one must operate the radio to repeat the problem, right?
I've tested the radio two times for about 5-6 hours total. It was sitting on the desk on batteries without any input. Worked fine. It could be just luck, though. The pattern to reproduce is unknown for me.
Check if 2.11.1 fixes the problem. There are quite a few critical bugs and fixed in 2.11.1, so not sure if the problem is gone or not.
I've installed todays nightly via ETX buddy. I'll report if issue persist or not.
I've got same issue after a significant time. The radio was in a USB HID mode. Will try a new release.
I have an EL18 running since 16 hours now, with an external ELRS module connected and the error did not happen. Could someone please share their radio config, model and widgets with me, so that I can test that specific setup?
Please, use my config from https://github.com/EdgeTX/edgetx/issues/6200
Just remember one thing that worth to check. So for those who are able to reproduce this. Please reproduce the problem and check the hardware debug screen and see if the switches all malfunctioned? Or moving sa will show sb moving, etc.
As I remember, all switches are stuck in the position they had at the time of the bug event. Can it be, that the bug is only happens, when the INPUTS tab is not completely empty?