Files
PX4-Autopilot/msg/RtcmData.msg
T
Jacob DahlandBeniamino Pozzan be03ec79c9 feat(uxrce_dds_client): accept RTCM corrections from ROS 2 (#29368)
* feat(uxrce_dds_client): accept RTCM corrections from ROS 2

ROS 2 setups that need RTK had to keep a MAVLink link beside DDS just for GPS_RTCM_DATA. Routing by device_id gives each DDS source its own rtcm_corrections instance, so two publishers never interleave their byte streams. The DDS side needs no framing: the injectors reframe the stream from arbitrary chunks.

Assisted-by: Claude:claude-opus-5-5

* docs(releases): note RTCM corrections over uXRCE-DDS

Assisted-by: Claude:claude-opus-5-5

* fix(uavcan): bound RTCM corrections length before forwarding

uXRCE-DDS is the first rtcm_corrections source that does not bound len. A ROS 2 RtcmData with len over 300 made the DroneCAN forwarder read past the data array and broadcast that memory as RTCMStream.

Assisted-by: Claude:claude-opus-5-5

* docs(msg): drop the uXRCE-DDS routing note from RtcmData

It described the client's routing rather than the message, and the device_id field comment already covers it.

Assisted-by: Claude:claude-opus-5-5

* fix(uavcan): bound moving-baseline length before forwarding

The forwarder trusted the publisher's len, the same gap just closed for rtcm_corrections. No current publisher exceeds the array, so this only keeps a future one from reading past it.

Assisted-by: Claude:claude-opus-5-5

---------

Co-authored-by: Beniamino Pozzan <beniamino.pozzan@gmail.com>
2026-11-03 11:39:08 -07:00

28 lines
1.1 KiB
Plaintext

# RTCM3 data exchanged with GNSS receivers.
#
# 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, uXRCE-DDS, GPS drivers in dump mode). Multiple
# 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
# forwarding MovingBaselineData); consumers only read instance 0.
uint64 timestamp # [us] Time since system start
uint32 device_id # [-] Unique device ID of the publisher that produced this RTCM
uint16 len # [-] Length of data
uint8 flags # [-] LSB: 1=fragmented
uint8[300] data # Correction payload (fixed-base RTCM3 and/or SPARTN frames, or moving-baseline RTCM3)
uint8 ORB_QUEUE_LENGTH = 16
# Sized for the fixed-base corrections case (up to four independent sources). The moving-baseline
# topic only uses instance 0 (single publisher per vehicle).
uint8 MAX_INSTANCES = 4
# TOPICS rtcm_corrections rtcm_moving_baseline