[Bug] dataman_client unable to write to sd storage #24608
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Starting in PX4 1.15.0, assumed to be with the introduction of 208552f, dataman_client is unable to write to SD storage on my tested hardware (EchoPilot AI https://echomav.com/product/echopilot-ai/). Checking dmesg logs and dataman status, datman status is good but dataman_client times out after 5000ms. This issue does not occur on PX4 1.14.4 (before the dataman_client refactor). I have tried restarting dataman after the system has started via a mavlink console but this does not fix the issue. The issue results in unable to write to SD storage errors throughout mission planner and qgroundcontrol. The sd card can be read and written to successfully when tested via mavlink console (eg:
echo thisisatest > /fs/microsd/filenameandcat /fs/microsd/filename).CC: @Igor-Misic
To Reproduce
No response
Expected behavior
No response
Screenshot / Media
No response
Flight Log
No response
Software Version
1.15.0-1.15.4 (latest stable tag)
Flight controller
No response
Vehicle type
None
How are the different components wired up (including port information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: