docs: auto-sync metadata [skip ci]

Co-Authored-By: PX4 BuildBot <bot@px4.io>
This commit is contained in:
PX4BuildBot
2026-09-30 18:09:05 +00:00
parent df34662110
commit 358d9df81b
6 changed files with 56 additions and 58 deletions
+3 -3
View File
@@ -14,7 +14,7 @@ The flag comments are used as label for the failsafe state machine simulation
## Fields
| Name | Type | Unit [Frame] | Range/Enum | Description |
| ------------------------------------------------------------------------------------------------- | -------- | ------------ | ---------- | ------------------------------------------------------------------------------------------------ |
| ------------------------------------------------------------------------------------------------- | -------- | ------------ | ---------- | ---------------------------------------------------------------------------------------------- |
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) |
| <a id="fld_mode_req_angular_velocity"></a>mode_req_angular_velocity | `uint32` | | |
| <a id="fld_mode_req_attitude"></a>mode_req_attitude | `uint32` | | |
@@ -61,7 +61,7 @@ The flag comments are used as label for the failsafe state machine simulation
| <a id="fld_parachute_unhealthy"></a>parachute_unhealthy | `bool` | | | Parachute system missing or unhealthy |
| <a id="fld_traffic_avoidance_unhealthy"></a>traffic_avoidance_unhealthy | `bool` | | | Traffic avoidance (ADS-B/FLARM) system missing or unhealthy |
| <a id="fld_remote_id_unhealthy"></a>remote_id_unhealthy | `bool` | | | Remote ID (Open Drone ID) system missing or unhealthy |
| <a id="fld_gnss_lost"></a>gnss_lost | `bool` | | | Active GNSS count dropped below SYS_HAS_NUM_GNSS, or two receivers report inconsistent positions |
| <a id="fld_gnss_lost"></a>gnss_lost | `bool` | | | Fewer GNSS receivers are healthy than required, or two receivers report inconsistent positions |
## Source Message
@@ -134,7 +134,7 @@ bool navigator_failure # Navigator failed to execute a mode
bool parachute_unhealthy # Parachute system missing or unhealthy
bool traffic_avoidance_unhealthy # Traffic avoidance (ADS-B/FLARM) system missing or unhealthy
bool remote_id_unhealthy # Remote ID (Open Drone ID) system missing or unhealthy
bool gnss_lost # Active GNSS count dropped below SYS_HAS_NUM_GNSS, or two receivers report inconsistent positions
bool gnss_lost # Fewer GNSS receivers are healthy than required, or two receivers report inconsistent positions
```
:::
+3 -3
View File
@@ -9,10 +9,10 @@ pageClass: is-wide-page
## Fields
| Name | Type | Unit [Frame] | Range/Enum | Description |
| ------------------------------------------- | -------- | ------------ | ---------- | ----------------------------------------------------------- |
| ------------------------------------------- | -------- | ------------ | ---------- | ---------------------------------------------------------------- |
| <a id="fld_timestamp"></a>timestamp | `uint64` | | | time since system start (microseconds) at PPS capture event |
| <a id="fld_rtc_timestamp"></a>rtc_timestamp | `uint64` | | | Corrected GPS UTC timestamp at PPS capture event |
| <a id="fld_"></a> | `uint8` | | | Increments when PPS dt < 50ms |
| <a id="fld_"></a> | `uint8` | | | Count of PPS pulses that arrived too soon after the previous one |
## Source Message
@@ -23,7 +23,7 @@ pageClass: is-wide-page
```c
uint64 timestamp # time since system start (microseconds) at PPS capture event
uint64 rtc_timestamp # Corrected GPS UTC timestamp at PPS capture event
uint8 pps_rate_exceeded_counter # Increments when PPS dt < 50ms
uint8 pps_rate_exceeded_counter # Count of PPS pulses that arrived too soon after the previous one
```
:::
+2 -4
View File
@@ -10,8 +10,7 @@ Published under two topic names that share this definition (see TOPICS below):
rtcm_corrections - external fixed-base corrections fed into the vehicle (MAVLink
GPS_RTCM_DATA, UAVCAN RTCMStream, GPS drivers in dump mode). Multiple
sources are allowed, one uORB instance each; consumers select an instance
via their stale-link logic.
sources are allowed, one uORB instance each; consumers select one instance.
rtcm_moving_baseline - moving-base GPS output (RTCM 4072 or equivalent) intended for a rover.
Single publisher per vehicle (on-board moving base, or a CANnode
@@ -49,8 +48,7 @@ forwarding MovingBaselineData); consumers only read instance 0.
#
# rtcm_corrections - external fixed-base corrections fed into the vehicle (MAVLink
# GPS_RTCM_DATA, UAVCAN RTCMStream, GPS drivers in dump mode). Multiple
# sources are allowed, one uORB instance each; consumers select an instance
# via their stale-link logic.
# sources are allowed, one uORB instance each; consumers select one instance.
#
# rtcm_moving_baseline - moving-base GPS output (RTCM 4072 or equivalent) intended for a rover.
# Single publisher per vehicle (on-board moving base, or a CANnode
+2 -4
View File
@@ -6,8 +6,7 @@ pageClass: is-wide-page
GNSS spectrum analysis.
Reports a basic RF spectrum analysis for a GNSS receiver, decoded from the u-blox UBX-MON-SPAN
message (enabled via the GPS_UBX_SPECTRUM parameter).
Reports a basic RF spectrum analysis for a GNSS receiver, decoded from the u-blox UBX-MON-SPAN message.
Published by the `gps` driver (UBX protocol only), once per RF block, via the block-specific topics below.
The center frequency of bin i is: f(i) = center_frequency + spectrum_span \* (i - 127) / 256
@@ -36,8 +35,7 @@ The center frequency of bin i is: f(i) = center_frequency + spectrum_span \* (i
```c
# GNSS spectrum analysis
#
# Reports a basic RF spectrum analysis for a GNSS receiver, decoded from the u-blox UBX-MON-SPAN
# message (enabled via the GPS_UBX_SPECTRUM parameter).
# Reports a basic RF spectrum analysis for a GNSS receiver, decoded from the u-blox UBX-MON-SPAN message.
# Published by the `gps` driver (UBX protocol only), once per RF block, via the block-specific topics below.
# The center frequency of bin i is: f(i) = center_frequency + spectrum_span * (i - 127) / 256
+6 -4
View File
@@ -4,7 +4,9 @@ pageClass: is-wide-page
# VehicleGnssHeading (UORB message)
GNSS heading from a dual-antenna or moving-baseline receiver, published by the sensors module from sensor_gnss_relative. Only headings whose reported baseline matches the configured SENS_GNSSn_HDG baseline are published. Consumed by EKF2. independently from position/velocity.
GNSS heading from a dual-antenna or moving-baseline receiver.
Published by the sensors module from sensor_gnss_relative. Consumed by EKF2 independently from position and velocity.
**TOPICS:** vehicle_gnss_heading
@@ -29,9 +31,9 @@ GNSS heading from a dual-antenna or moving-baseline receiver, published by the s
::: details Click here to see original file
```c
# GNSS heading from a dual-antenna or moving-baseline receiver, published by the sensors module from sensor_gnss_relative.
# Only headings whose reported baseline matches the configured SENS_GNSSn_HDG baseline are published. Consumed by EKF2
# independently from position/velocity.
# GNSS heading from a dual-antenna or moving-baseline receiver
#
# Published by the sensors module from sensor_gnss_relative. Consumed by EKF2 independently from position and velocity.
uint64 timestamp # time since system start (microseconds)
uint64 timestamp_sample # time since system start (microseconds) - actual measurement time
+1 -1
View File
@@ -293,7 +293,7 @@ Graphs showing how these are used [can be found here](../middleware/uorb_graph.m
- [VehicleConstraints](VehicleConstraints.md) — Local setpoint constraints in NED frame. setting something to NaN means that no limit is provided.
- [VehicleControlMode](VehicleControlMode.md) — Defines which controllers should run.
- [VehicleGnss](VehicleGnss.md) — Selected GNSS solution.
- [VehicleGnssHeading](VehicleGnssHeading.md) — GNSS heading from a dual-antenna or moving-baseline receiver, published by the sensors module from sensor_gnss_relative. Only headings whose reported baseline matches the configured SENS_GNSSn_HDG baseline are published. Consumed by EKF2. independently from position/velocity.
- [VehicleGnssHeading](VehicleGnssHeading.md) — GNSS heading from a dual-antenna or moving-baseline receiver.
- [VehicleImu](VehicleImu.md) — IMU readings in SI-unit form.
- [VehicleImuStatus](VehicleImuStatus.md)
- [VehicleLocalPositionSetpoint](VehicleLocalPositionSetpoint.md) — Local position setpoint in NED frame. Telemetry of PID position controller to monitor tracking. NaN means the state was not controlled.