ArduPilot / ArduPilot/MAVProxy
Telemetry logs fill up disk
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 596
- Forks
- 774
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 18
Description
We have a setup where a MAVProxy instance is running continuously on an onboard computer attached to a Pixhawk 4. The .tlog and .tlog.raw files grow until the disk usage is at 100%. It would be great if one could either a) prevent these log files from being created completely or b) set a size limit via the command line parameters.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating MAVProxy's telemetry log creation and command-line option handling, then determine whether disabling logs or limiting their size is the intended scope. Check how the .tlog and .tlog.raw files are produced and define completion as preventing unbounded disk growth while preserving the selected logging behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100