-
Notifications
You must be signed in to change notification settings - Fork 13.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dealing with SDCARD failure #7750
Comments
PS: on the last log, by the clients account it was in RETURN flight mode but kept loitering around the last waypoint. |
TODO:
|
Also i would do a dry run reading all items before switching. Could we do some crc checking? |
Yes we should. Sorry for not raising this earlier. |
Hey, this issue has been closed because the label (This is an automated comment from GitMate.io.) |
hello, I see this issue is closed, but I encountered the same problem when I'm using 1.8.2 stable(modified rtk gps driver) firmware. The SD card is broken and then the plane flew to the last known point until the battery ran out. I want to know if you have plans to fix this? |
Some flights on a vehicle with a failing SDcard from a client:
Mission read failure (presumably) resulted in unexpected back transition: https://logs.px4.io/plot_app?log=ffa0687e-c817-4163-b52e-4f9fa1a66994 (the user then activated the takeoff waypoint to re-transition)
Complete weirdness at takeoff: https://logs.px4.io/plot_app?log=bc6215da-fd24-425c-a4e8-ecfaa9b12571
Also not all params seem to have been logged
Total failure halfway: https://logs.px4.io/plot_app?log=2258f3eb-fa11-4571-a409-b1d7417f19e3
Also not all params seem to have been logged
At minimum, when mission read fails it must RTL, not loiter around the last known WP
The other strange behavior i am pretty sure is sd card related too, maybe some io buffer issue.
@LorenzMeier @dagar @bkueng thoughts?
Update:
Action: check sd-card performance at boot, warn when performance is below threshold. (see: #4460)
Action: crc checking on read missions
Action: raise awareness in community
The text was updated successfully, but these errors were encountered: