u-blox ZED-F9P Interface Description - Manual
Advance Information
5.11.7 UBX-LOG-RETRIEVESTRING (0x21 0x0d)
5.11.7.1 Byte string log entry
Message
UBX-LOG-RETRIEVESTRING
Description
Byte string log entry
Firmware
Supported on:
•
u-blox 9 with protocol version 27
Type
Output
Comment
This message is used to report a byte string log entry
Header
Class
ID
Length (Bytes)
Payload
Checksum
Message Structure
0xB5 0x62
0x21 0x0d 16 + 1*byteCount
see below
CK_A CK_B
Payload Contents:
Byte Offset
Number
Format
Scaling
Name
Unit
Description
0
U4
-
entryIndex
-
The index of this log entry
4
U1
-
version
-
The version of this message. Set to 0
5
U1
-
reserved1
-
6
U2
-
year
-
Year (1-65635) of UTC time. Will be zero if time
not known
8
U1
-
month
-
Month (1-12) of UTC time
9
U1
-
day
-
Day (1-31) of UTC time
10
U1
-
hour
-
Hour (0-23) of UTC time
11
U1
-
minute
-
Minute (0-59) of UTC time
12
U1
-
second
-
Second (0-60) of UTC time
13
U1
-
reserved2
-
14
U2
-
byteCount
-
Size of string in bytes
Start of repeated block (byteCount times)
16 + 1*N
U1
-
bytes
-
The bytes of the string
End of repeated block
5.11.8 UBX-LOG-RETRIEVE (0x21 0x09)
5.11.8.1 Request log data
Message
UBX-LOG-RETRIEVE
Description
Request log data
Firmware
Supported on:
•
u-blox 9 with protocol version 27
Type
Command
Comment
This message is used to request logged data (log recording must first be disabled, see
Log entries are returned in chronological order, using the messages
. If the odometer was enabled at the
time a position was logged, then message
will also be
used. The maximum number of entries that can be returned in response to a single UBX-
LOG-RETRIEVE message is 256. If more entries than this are required the message will need
to be sent multiple times with different startNumbers. The retrieve will be stopped if any
UBX-LOG message is received. The speed of transfer can be maximized by using a high
UBX-18010854 - R04
Advance Information
Page 99 of 259