Message Type 255, ULCP binary format, Custom Message: (message 112 + Auxilliary data)
Header: 0xFF 0xSS 0x06 0x00 0x00 0xNN 0x0000
Where 0xNN is message length - dependant on the Modem ID, auxiliary device ID and payload length.
Note: This message is message 112 + ',' + device ID + ',' + Continued flag + payload, but with message type changed from 112 to 255.
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 |
| 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 … bit 7 = Not used |
| 0x00 | Not used |
| 0x00 | Event source: None |
| 0x00 | Event reason: None |
| 1 to 15 bytes | Modem ID: ASCII string |
| 1 byte | ',' Delimiter |
| 1 to 4 bytes | Device ID: ASCII string |
| 1 byte | ',' Delimiter |
| 1 byte | Continued flag:0x00 = if following packet is not part of current one; 0x01 = if following packet is part of current one |
| 1 to 205 bytes | Payload if available |
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 10:59:42 AM