16: Satellite Data

Header

Field	Name	Description	Type
5	Method	Request a service to be perform an action Possible values: 1: SET— Set one or more values that are provided in the message payload. 2: GET— Get values for the associated message type. 3: SUBSCRIBE— Subscribe to values for the associated message type. Can be used in conjunction with other header fields to define the subscription parameters, such as Interval, Duration, Timeout, Storage Level and Message Level. If no interval is provided, messages will be sent as and when new data is available. Some data, such as GPS position, may require a set interval to be provided. 5: UNSUBSCRIBE— Unsubscribe from a previous subscription.	uint8

This is an extract of header fields that are relevant to this message type, you can find them all documented in the Headers section.

Payload

Field	Name	Description	Type	Unit
1	SNR Average	Average signal-to-noise ratio across all satellites	uint8
2	SNR Minimum	Minimum signal-to-noise ratio among all satellites	uint8
3	SNR Maximum	Maximum signal-to-noise ratio among all satellites	uint8
4	Total Satellites	Total number of satellites in view	uint8
5	Good Satellites	Heuristic for signal quality (defined as satellites with SNR>=38dBm. This number should be higher than 8 for a good RTK fix, typically)	uint8
10	GPS L1	Summary data for GPS L1 satellites	bytes
11	GPS Lx	Summary data for GPS L2 or L5 satellite signals (depending on hardware)	bytes
12	GLONASS L1	Summary data for GLONASS L1 satellite signals	bytes
13	GLONASS Lx	Summary data for GLONASS L2 or L5 satellite signals (depending on hardware)	bytes
14	Beidou L1	Summary data for Beidou L1 satellite signals	bytes
15	Beidou Lx	Summary data for Beidou L2 or L5 satellite signals (depending on hardware)	bytes
16	Galileo L1	Summary data for Galileo L1 satellite signals	bytes
17	Galileo Lx	Summary data for Galileo L2 or L5 satellite signals (depending on hardware)	bytes

Examples

RTK fix satellite data

📡 Real example from RV1 P1 v2287 on 2025-10-03This example is captured from an RV1 device as part of normal communications with the cloud, somewhere in California.

Code

For convenience, the following constants can be used to reference this message type.