px4-firmware/msg/gps_dump.msg

# This message is used to dump the raw gps communication to the log.
# Set the parameter GPS_DUMP_COMM to 1 to use this.

uint64 timestamp		# time since system start (microseconds)

uint8 instance 		# Instance of GNSS receiver

uint8 len			# length of data, MSB bit set = message to the gps device,
				# clear = message from the device
uint8[79] data		# data to write to the log

uint8 ORB_QUEUE_LENGTH = 8
gps file dump: re-implement with an uORB topic & write to the log file (#4987) Drawbacks of the previous method: when writing to the SD card, there are high delays in the write() call of several 100ms, every now and then. The frequency and length of these events depend on: - SD card - used logger bandwidth - bandwidth of gps data (RTCM) Since the whole gps thread was blocked during this period, it lead to gps timeouts and lost module. What we do now is: publish an orb topic with queuing. This makes it async and the logger takes care of buffering. This means it's best to: - use high logger rate - use large logger buffer - reduce logger bandwith by disabling unused topics 2016-07-06 04:32:37 -03:00			`# This message is used to dump the raw gps communication to the log.`
			`# Set the parameter GPS_DUMP_COMM to 1 to use this.`

add timestamp field to uORB msgs; sync timestamp whenever possible 2018-08-06 21:30:05 -03:00			`uint64 timestamp # time since system start (microseconds)`

Spelling errors (#19935) 2022-07-27 01:33:16 -03:00			`uint8 instance # Instance of GNSS receiver`
GPS_DUMP_COMM: dump all gps instances 2020-12-08 06:45:24 -04:00
gps file dump: re-implement with an uORB topic & write to the log file (#4987) Drawbacks of the previous method: when writing to the SD card, there are high delays in the write() call of several 100ms, every now and then. The frequency and length of these events depend on: - SD card - used logger bandwidth - bandwidth of gps data (RTCM) Since the whole gps thread was blocked during this period, it lead to gps timeouts and lost module. What we do now is: publish an orb topic with queuing. This makes it async and the logger takes care of buffering. This means it's best to: - use high logger rate - use large logger buffer - reduce logger bandwith by disabling unused topics 2016-07-06 04:32:37 -03:00			`uint8 len # length of data, MSB bit set = message to the gps device,`
			`# clear = message from the device`
GPS_DUMP_COMM: dump all gps instances 2020-12-08 06:45:24 -04:00			`uint8[79] data # data to write to the log`
introduce uORB::PublicationQueued and transition most orb_advertise_queue usage 2019-07-03 17:30:21 -03:00
			`uint8 ORB_QUEUE_LENGTH = 8`