Message Type 111, ULCP binary format, with msg 112, Cell Tower ID, RPM, Fuel Level, Seatbelt, Speed, RSSI, SQI, Accel, PDOP
Header: 0x6F 0xSS 0x06 0x00 0x00 0xNN 0x0000
Where NN is the message length range 0x24 to 0x33 - dependent on the Modem ID string length.
Note: All multi-byte data are little-endian, except for modem ID.
Message body:
Hex | Description |
2 bytes | Binary Pevent |
4 bytes | Normalized latitude (RMC latitude x 100,000) |
4 bytes | Normalized longitude (RMC longitude x 100,000) |
2 bytes | Speed in kmph |
2 bytes | Heading |
1 byte | Status byte [bit 0-seatbelt (0=unbuckled/unknown, 1=buckled); bit 1-GPS (1=valid); bit 2-RF switch box mode (1=RF off); bit 3-ignition (1=ON); bit 4-accel calibrated (1=DONE)] |
1 byte | Number of satellites used for position fix |
1 byte | Digital input state (0= off, 1=on): bit 0 = input #1, bit 1 = input #2…bit 7 = input #8 |
2 bytes | Altitude in meters |
4 bytes | Time (based on number of seconds since 00:00:00 January 1st 1970 |
4 bytes | Cell Tower ID |
2 bytes | RPM |
1 byte | Fuel level (%) |
1 byte | OBD Speed (km/h) |
1 byte | RSSI (negative dBm) |
1 byte | Signal Quality Index (positive %) |
1 byte | Accel event [0=no event; 1/-1=accel/decel; 2/-2=right/left turn; 3=rollover] |
1 byte | 0 if accel event 0, forward accel (km/h/s) if accel event 1/-1/3, lateral accel (km/h/s) if accel event 2/-2 |
1 byte | PDOP (x10) |
1 to 15 bytes | Modem ID: ASCII string |
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 5 years ago
Last modified on 14-12-03 11:54:54 AM