fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-25 06:43:35 +08:00
Code Issues Packages Projects Releases Wiki Activity

Link fixes - mostly redirects (#25186)

Browse Source
This commit is contained in:
Hamish Willee
2025-07-10 17:35:07 +10:00
committed by GitHub
parent 5d5e23bcfa
commit dd0dcbb82c
43 changed files with 90 additions and 150 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/dev_log/ulog_file_format.md
+1 -5
View File
@@ -114,7 +114,6 @@ struct ulog_message_flag_bits_s {
```
- `compat_flags`: compatible flag bits
- These flags indicate the presence of features in the log file that are compatible with any ULog parser.
- `compat_flags[0]`: _DEFAULT_PARAMETERS_ (Bit 0): if set, the log contains [default parameters message](#q-default-parameter-message)
@@ -124,7 +123,6 @@ struct ulog_message_flag_bits_s {
It means parsers can just ignore the bits if one of the unknown bits is set.
- `incompat_flags`: incompatible flag bits.
- `incompat_flags[0]`: _DATA_APPENDED_ (Bit 0): if set, the log contains appended data and at least one of the `appended_offsets` is non-zero.
The rest of the bits are currently not defined and must be set to 0.
@@ -137,7 +135,6 @@ struct ulog_message_flag_bits_s {
For example, crash dumps.
A process appending data should do:
- set the relevant `incompat_flags` bit
- set the first `appended_offsets` that is currently 0 to the length of the log file without the appended data, as that is where the new data will start
- append any type of messages that are valid for the Data section.
@@ -403,7 +400,6 @@ struct message_logging_tagged_s {
```
- `tag`: id representing source of logged message string. It could represent a process, thread or a class depending upon the system architecture.
- For example, a reference implementation for an onboard computer running multiple processes to control different payloads, external disks, serial devices etc can encode these process identifiers using a `uint16_t enum` into the `tag` attribute of struct as follows:
```c
@@ -494,7 +490,7 @@ A valid ULog parser must fulfill the following requirements:
- [FlightPlot](https://github.com/PX4/FlightPlot): Java, log plotter.
- [MAVLink](https://github.com/mavlink/mavlink): Messages for ULog streaming via MAVLink (note that appending data is not supported, at least not for cut off messages).
- [QGroundControl](https://github.com/mavlink/qgroundcontrol): C++, ULog streaming via MAVLink and minimal parsing for GeoTagging.
- [mavlink-router](https://github.com/01org/mavlink-router): C++, ULog streaming via MAVLink.
- [mavlink-router](https://github.com/mavlink-router/mavlink-router): C++, ULog streaming via MAVLink.
- [MAVGAnalysis](https://github.com/ecmnet/MAVGCL): Java, ULog streaming via MAVLink and parser for plotting and analysis.
- [PlotJuggler](https://github.com/facontidavide/PlotJuggler): C++/Qt application to plot logs and time series. Supports ULog since version 2.1.3.
- [ulogreader](https://github.com/maxsun/ulogreader): Javascript, ULog reader and parser outputs log in JSON object format.