Skip to content
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

Add information for the logger module error behavior and file size limitations #2616

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion en/dev_log/logging.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,9 @@ A new log file is created for each arming session on the SD card.
To display the current state, use `logger status` on the console.
If you want to start logging immediately, use `logger on`.
This overrides the arming state, as if the system was armed.
`logger off` undoes this.
`logger off` undoes this.

If logging stops due to a write error, or reaching the [maximum file size](#file-size-limitations), PX4 will automatically restart logging in a new file.

For a list of all supported logger commands and parameters, use:

Expand Down Expand Up @@ -79,6 +81,12 @@ This configuration will log sensor_accel 0 at full rate, sensor_accel 1 at 10Hz,

There are several scripts to analyze and convert logging files in the [pyulog](https://github.com/PX4/pyulog) repository.


## File size limitations

The maximum file size depends on the file system and OS.
The size limit on NuttX is currently around 2GB.

## Dropouts

Logging dropouts are undesired and there are a few factors that influence the
Expand Down