Chapter 10
Standard: JT/T 808-2013
Technical Appendix
Table 3 terminal parameters, 202 OBD-II data stream PIDs, driving behavior alert codes, and privileged SMS commands.
Appendix
10.1 List of Figures#
The following sequence diagrams and frame structure figures are specified in this standard:
| Figure # | Title | Primary Chapter | Direct Link |
|---|---|---|---|
| Fig. 1 | Business Flowchart of Terminal Registration | Chapter 4: Business Process | View Fig. 1 Flowchart |
| Fig. 2 | Message Structure (Wire Frame Packet Diagram) | Chapter 5: Protocol Details | View Fig. 2 Structure |
| Fig. 3 | Structure Chart of Message Body Attributes Format | Chapter 5: Protocol Details | View Fig. 3 Attributes |
10.2 List of Key Protocol Tables#
| Table # | Title | Description & Topic | Explorer Link |
|---|---|---|---|
| Table 1 | Data Type | Primitive data types (BYTE, WORD, DWORD, BCD, STRING) | Chapter 5 |
| Table 2 | Message Header | Standard 12~16 byte packet header fields | Chapter 5 |
| Table 3 | Packet Encapsulation Item | Long message sub-packet encapsulation header | Chapter 5 |
| Table 4 | User-Defined Parameter IDs | Terminal configuration parameters (0xF000 ~ 0xFFFF) | Explore Parameters |
| Table 6 | Terminal General Response | ACK result status codes for platform commands | View 0x0001 |
| Table 7 | Platform General Response | Acknowledgement format for terminal telemetry | View 0x8001 |
| Table 8-9 | Terminal Registration Request & Response | Handshake provisioning & base key issuance | View 0x0100 |
| Table 18 | Location Information Reporting | GPS position, speed, direction, status flags | View 0x0200 |
| Table 19 | Location Alarm Flag Bits | 32-bit alarm bitmask (SOS, speeding, rollover, fault) | Chapter 9 |
| Table 20 | Location Status Flag Bits | 32-bit vehicle status flags (ACC, fixed, door, fuel) | Chapter 9 |
| Table 25 | OBD Data Stream IDs (Extensible) | Real-time vehicle engine RPM, speed, coolant temp | Explore OBD PIDs |
| Table 28 | Alarm and Driving Behavior Data IDs | Rapid acceleration, harsh braking, crash, idling | Chapter 9 |
10.3 Trouble Code Description (DTC Data Format)#
The terminal supports standard automotive OBD-II and heavy-duty commercial vehicle SAE J1939 diagnostic trouble codes:
10.3.1 SAE J1939 Diagnostic Trouble Code Format (4 Bytes)#
| Byte | Field | Bitmask | Description and Requirements |
|---|---|---|---|
| Byte 1 | SPN [7:0] | Bit 7 ~ 0 | SPN lower 8 significant bits (Bit 7 is MSB) |
| Byte 2 | SPN [15:8] | Bit 7 ~ 0 | SPN middle 8 significant bits |
| Byte 3 | SPN [18:16] | Bit 7 ~ 5 | SPN upper 3 significant bits |
| Byte 3 | FMI [4:0] | Bit 4 ~ 0 | Failure Mode Identifier (5 bits, Bit 4 is MSB) |
| Byte 4 | Fault Period | Bit 7 | 0: Current active fault; 1: Historical fault |
| Byte 4 | Fault Count | Bit 6 ~ 0 | Current fault occurrence count (Bit 1 ~ 7) |
10.3.2 Standard OBD-II DTC Format (4 Bytes)#
| Byte | Field | Description and Requirements |
|---|---|---|
| Byte 1 | DTC Low Byte | Standard OBD-II Diagnostic Trouble Code low byte (e.g. P0300, P0420) |
| Byte 2 | DTC High Byte | Standard OBD-II Diagnostic Trouble Code high byte |
| Byte 3 | Reserved | Reserved byte, fixed at 0x00 |
| Byte 4 | Fault Period | Bit 7 indicates fault occurrence period (0: Current active fault, 1: Historical fault) |
10.4 Privileged SMS Configuration Commands#
The terminal should have SMS service enabled on its cellular SIM card to allow emergency configuration and control even if cellular GPRS/LTE data links fail:
| Item | Function Name | SMS Command Syntax | Terminal Reply Format | Description |
|---|---|---|---|---|
| 1 | Restart Terminal | Reboot! | Reboot OK! | Restarts device MCU and cellular modem |
| 2 | Factory Reset | Restore! | Restore OK! | Resets configuration parameters to factory defaults (server IP & port remain unchanged) |
| 3 | Query Server Address | Port? | query Port:[IP]:[PORT]; | Inquires currently configured telematics server address & port |
| 4 | Set Server Address | *SETSERVER:[IP],[PORT]# | set server success ip=[IP] port=[PORT] | Sets server IP address or domain name and port |
| 5 | Query Registration Status | Register State? | Registered! or Unregister! | Checks if device is currently registered on the platform |
| 6 | Terminal Deregistration | Deregister! | Deregister OK! | Clears registration ID and deletes base key from FLASH |
10.5 Device Self-Check Modules#
When executing on-demand or periodic hardware self-check diagnostics, the terminal inspects sub-system modules and reports status flags:
| Self-Check ID | Hardware Module | Status Code | Diagnostic State & Meaning |
|---|---|---|---|
| 0x01 | GPS / GNSS Module | 0x00 | Succeeded / Normal operation |
| 0x01 | GPS / GNSS Module | 0x01 | Antenna disconnected |
| 0x01 | GPS / GNSS Module | 0x02 | Antenna short-circuited |
| 0x02 | Bluetooth Module | 0x00 | Succeeded / Normal operation |
| 0x02 | Bluetooth Module | 0x01 | Failed / No communication |
| 0x03 | Backup Battery Module | 0x00 | Succeeded / Normal voltage |
| 0x03 | Backup Battery Module | 0x01 | Low battery voltage |
| 0x03 | Backup Battery Module | 0x02 | Abnormal battery / Charging fault |
| 0x04 | CAN Bus Controller | 0x00 | Succeeded / Normal CAN bus activity |
| 0x04 | CAN Bus Controller | 0x01 | Failed to connect CAN transceiver |
| 0x05 | G-Sensor / Gyroscope | 0x00 | Succeeded / Accelerometer ready |
| 0x05 | G-Sensor / Gyroscope | 0x01 | Sensor I2C/SPI communication failed |
| 0x06 | K-Line Interface | 0x00 | Succeeded / Normal K-Line transceiver |
| 0x06 | K-Line Interface | 0x01 | K-Line communication failed |
| 0x07 | FLASH Storage Chip | 0x00 | Succeeded / SPI FLASH accessible |
| 0x07 | FLASH Storage Chip | 0x01 | SPI FLASH read/write failed |
| 0x08 | Vin ADC Sampling | 0x00 | Succeeded / Operating voltage normal |
| 0x08 | Vin ADC Sampling | 0x01 | Main voltage ADC sampling abnormal |