Message Type 97, ULCP binary format, Digital I/O plus GPS data (no events)
Header: 0x61 0xSS 0x06 0x00 0x00 0x19 0x0000
Note: This message is message type 98 w/o the last 3 bytes
Message body:
Hex | Description |
4 bytes | Normalized latitude (RMC latitude x 100,000) |
4 bytes | Normalized longitude (RMC longitude x 100,000) |
2 bytes | Speed in knots |
2 bytes | Heading |
1 byte | GPS data validity: 0x”A” = valid; 0x”V” = invalid; 0x”B” = buffered valid; 0x”W” = buffered invalid. |
1 byte | Number of satellites used for position fix |
1 byte | Position type (from GGA message) |
1 byte | Digital input state (0=off, 1=on): bit 0 = input #1, bit 1 = input #2…bit 5 = input #6, bit 6 = RF switch box output mode (1 = RF off, 0 = RF on), bit 7 = ignition status. |
2 bytes | Altitude in meters |
2 bytes | Differential correction age (only valid if differential correction being used) |
4 bytes | Time (based on number of seconds since 00:00:00 January 1st 1970 |
1 byte | Digital output state (0= off, 1=on): bit 0 = output #1, bit 1 = output #2, bit 2 = output #3, bit 3 = output #4, bit 4 = output #5, bit 5 = output #6, bit 6 = input #7, bit 7 = input #8 (Outputs 5/6 and inputs 7/8 are CTM200r2 only) |
Note: ULCP binary messages should not be used for local serial report mode 1 and 2 in applications where timed message delivery is critical.
Last modified 6 years ago
Last modified on 14-04-29 08:41:57 AM