Aircraft crash after SD card fills during logging in EdgeTX 2.11
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c
- Domain
- embedded-iot
Research direction
Start by searching the firmware for SD-card logging and the “SD card full” handling, then compare that path with issue #3728, which the report identifies as a related but different trigger. Reproduce with logging enabled on a full SD card if possible. Done means logging stops or reports the storage condition without interrupting radio operation or control.
Written by the indexing model from the issue text.
Description
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
In EdgeTX 2.11 jolly mon, the SD card became full while logging and control was lost and the aircraft crashed. The radio screen showed the regular info, but a text in programming language format was written on top of it. I believe it contained words like 'unexpected' and 'argument'.
When I restarted the controller, it started in Emergency Mode. Restarting again, there was a warning that the SD card was full and that no logging would take place and the radio seemed to work well.
I was running 2.11.2 but not sure about the third digit. I have since upgraded to 2.12
Expected Behavior
When the SD card runs out of space during logging, logging should stop or report the storage condition without interrupting radio operation or control of the aircraft.
Steps To Reproduce
- Use EdgeTX 2.11.2 with SD-card logging enabled.
- Allow the SD card to become full while logging.
- The aircraft crashed in the reported incident.
Version
2.11.2
Transmitter
HelloRadioSky V16
Operating System (OS)
No response
OS Version
No response
Anything else?
A search found a previously reported SD-card-full logging crash in issue #3728, but that report involved connecting USB while the "SD card full" popup was displayed. It appears to be a different trigger than the aircraft crash reported here.
- Dominant language
- C
- Stars
- 2.4k
- Forks
- 614
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 63
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EdgeTX/edgetx
-
translationOpenenhancement ✨
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
EdgeTX/edgetx#7412 · 2 comments ·
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 2/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug 🪲 triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
EdgeTX/edgetx#8003 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
要トリアージ 辞書
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
yksr-melt/Meltype#1625 · 1 reaction ·
Maintainers usually reply within 1 day
-
kind/bug priority/medium qa_automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37324 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tree-sitter/tree-sitter#6111 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
joncampbell123/dosbox-x#6797 ·
Maintainers usually reply within 1 day