Detailed Explanation of Messages
Comprehensive wire-frame field breakdown of all 22 communication messages in JT/T 808-2013.
Detailed Explanation of Messages
9.0 Terminal Configuration Parameters Overview#
According to the JT/T 808-2013 standard:
0x0001 ~ 0xEFFF: Standard parameters defined in national specification JT/T 808-2013.0xF000 ~ 0xFFFF: Proprietary user-defined parameters for Jimi VL502 connected vehicle terminals.Featured User-Defined Parameters (0xF000 ~ 0xF020)#
| Parameter ID | Data Type | Default Value | Description & Requirements |
|---|---|---|---|
| 0xF000 | DWORD | 0 | Connected vehicle terminal feature switch bitmask |
| 0xF001 | WORD | 10 | OBD data acquisition frequency while driving (seconds) |
| 0xF002 | WORD | 300 | OBD data acquisition frequency while stationary/flameout (seconds) |
| 0xF003 | BYTE | 1 | High-frequency acceleration sensor collection enable (0: Disable, 1: Enable) |
| 0xF004 | WORD | 30 | Idle timeout alarm threshold (seconds) |
| 0xF005 | WORD | 120 | Rapid acceleration threshold (mg) |
| 0xF006 | WORD | 120 | Rapid deceleration / harsh braking threshold (mg) |
| 0xF007 | WORD | 100 | Harsh sharp turn threshold (mg) |
| 0xF008 | WORD | 500 | Collision / impact alarm threshold (mg) |
| 0xF00D | DWORD | 0x00000000 | Vehicle brand & engine protocol type ID (See Table 5) |
| 0xF010 | STRING | "" | FOTA firmware upgrade FTP server address |
| 0xF011 | WORD | 21 | FOTA firmware upgrade FTP server port |
| 0xF020 | DWORD | 0 | Extended telemetry mask flags |
---
9.0.1 Terminal General Response — 0x0001#
Message ID: 0x0001 | Direction: Uplink
Terminal acknowledgement response to platform commands.
Table: Data Format of Terminal General Response Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Response Sequence Number | WORD | Flow number of the corresponding platform message. |
| 2 | Response Message ID | WORD | Message ID of the corresponding platform command. |
| 4 | Result | BYTE | 0: Succeeded/confirm; 1: Failed; 2: Message error; 3: Not support; 4: SE key exchange succeeded; 5: SE key exchange failed. |
9.1 Platform General Response — 0x8001#
Message ID: 0x8001 | Direction: Platform -> Terminal (Downlink)
General response sent by the platform to acknowledge terminal requests or report execution results.
Table: Data Format of Platform General Response Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Response Flow Number | WORD | Corresponding terminal message flow number. |
| 2 | Response Message ID | WORD | Corresponding terminal message ID. |
| 4 | Result | BYTE | 0: Success / Confirmation; 1: Failure; 2: Message error; 3: Not supported. |
9.2 Terminal Heartbeat — 0x0002#
Message ID: 0x0002 | Direction: Terminal -> Platform (Uplink)
Periodically sent by the terminal to keep the TCP/UDP connection alive. The message body is empty.
Table: Data Format of Terminal Heartbeat Message Body
*This message has an empty message body (0 bytes payload).*
9.3 Terminal Registration — 0x0100#
Message ID: 0x0100 | Direction: Terminal -> Platform (Uplink)
Sent upon first boot or SIM insertion to register the hardware identity and vehicle metadata with the platform.
Table: Data Format of Terminal Registration Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Province ID | WORD | GB/T 2260 administrative division province code. |
| 2 | City ID | WORD | GB/T 2260 administrative division city/county code. |
| 4 | Manufacturer ID | STRING[5] | 5-byte manufacturer code assigned to Jimi IoT. |
| 9 | Terminal Model | STRING[20] | Device model, e.g. VL502 (padded with 0x00). |
| 29 | Terminal ID | STRING[7] | 7-byte unique terminal serial number. |
| 36 | License Plate Color | BYTE | JT/T 415-2006: 1=Blue, 2=Yellow, 3=Black, 4=White, 5=Green, 9=Other, 0=Unlicensed. |
| 37 | Vehicle License Plate | STRING | Motor vehicle registration plate string (or VIN if unlicensed). |
9.4 Terminal Registration Response — 0x8100#
Message ID: 0x8100 | Direction: Platform -> Terminal (Downlink)
Platform reply to 0x0100 registration request containing authorization token.
Table: Data Format of Terminal Registration Response Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Response Flow Number | WORD | Flow number of the corresponding 0x0100 registration request. |
| 2 | Result | BYTE | 0: Success; 1: Vehicle already registered; 2: No such vehicle in database; 3: Terminal already registered; 4: No such terminal in database. |
| 3 | Authentication Code | STRING | Authentication token string issued by platform; required for subsequent 0x0102 logins (only present if Result=0). |
9.5 Terminal Logout — 0x0003#
Message ID: 0x0003 | Direction: Terminal -> Platform (Uplink)
Notifies the platform that the terminal is being uninstalled or powering down. Message body is empty.
Table: Data Format of Terminal Logout Message Body
*This message has an empty message body (0 bytes payload).*
9.6 Terminal Login Authentication — 0x0102#
Message ID: 0x0102 | Direction: Terminal -> Platform (Uplink)
Sent immediately after establishing TCP connection to authenticate identity using the token received in 0x8100.
Table: Data Format of Terminal Login Authentication Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Authentication Code | STRING | Authentication string assigned during terminal registration. |
9.7 Set Parameter for Specific Terminal — 0x8103#
Message ID: 0x8103 | Direction: Platform -> Terminal (Downlink)
Downlink command configuring one or multiple terminal parameters (0x0001 - 0xFFFF).
Table: Data Format of Set Parameter for Specific Terminal Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Parameter Count | BYTE | Number of parameter items included in the command (n). |
| 1 | Parameter Items List | PARAM_LIST | Repeated items: [Param ID (DWORD, 4B) + Param Length (BYTE, 1B) + Param Value (Variable)]. |
9.8 Query Parameter of Specific Terminal — 0x8106#
Message ID: 0x8106 | Direction: Platform -> Terminal (Downlink)
Queries current values of designated parameter IDs.
Table: Data Format of Query Parameter of Specific Terminal Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Parameter Count | BYTE | Total number of parameter IDs requested (n). |
| 1 | Parameter ID List | DWORD[n] | Array of 4-byte parameter IDs. |
9.9 Response to Parameter Query — 0x0104#
Message ID: 0x0104 | Direction: Terminal -> Platform (Uplink)
Terminal response containing requested parameter values.
Table: Data Format of Response to Parameter Query Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Response Flow Number | WORD | Flow number of corresponding 0x8106 query message. |
| 2 | Parameter Count | BYTE | Number of returned parameters. |
| 3 | Parameter Items List | PARAM_LIST | [Param ID (DWORD) + Param Length (BYTE) + Param Value]. |
9.10 Terminal Control — 0x8105#
Message ID: 0x8105 | Direction: Platform -> Terminal (Downlink)
Platform remote execution commands for device management (reboot, reset, wireless controls).
Table: Data Format of Terminal Control Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Command Word | BYTE | 1: Wireless upgrade; 2: Connect specified server; 3: Terminal reboot; 4: Factory reset; 5: Turn off data communication; 6: Turn off all wireless. |
| 1 | Command Parameter | STRING | Command arguments (e.g. APN, IP, Port, URL for upgrade). |
9.11 Notification of Terminal Upgrade Result — 0x0108#
Message ID: 0x0108 | Direction: Terminal -> Platform (Uplink)
Reports firmware OTA upgrade completion status.
Table: Data Format of Notification of Terminal Upgrade Result Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Upgrade Type | BYTE | 0: Terminal firmware; 12: Card reader; 52: Beidou/GNSS module. |
| 1 | Upgrade Result | BYTE | 0: Succeeded; 1: Failed; 2: Canceled. |
9.12 Location Information Reporting — 0x0200#
Message ID: 0x0200 | Direction: Terminal -> Platform (Uplink)
Core periodic tracking packet reporting GNSS position, speed, direction, status flags, and active alarms.
Table: Data Format of Location Information Reporting Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Alarm Flag | DWORD | 32-bit alarm bitmap: SOS, speeding, fatigue, geo-fence, low battery, vibration, etc. |
| 4 | Status Flag | DWORD | 32-bit status bitmap: ACC state (bit 0), GPS fix (bit 1), lat/lon signs, encryption, oil/electric cut. |
| 8 | Latitude | DWORD | Latitude in degrees * 10^6 (accurate to 10^-6 deg). |
| 12 | Longitude | DWORD | Longitude in degrees * 10^6 (accurate to 10^-6 deg). |
| 16 | Altitude | WORD | Elevation above sea level in meters. |
| 18 | Speed | WORD | Vehicle speed in 1/10 km/h. |
| 20 | Direction | WORD | Heading azimuth 0 - 359 degrees (0 = True North). |
| 22 | Time | BCD[6] | GNSS UTC/local timestamp in YY-MM-DD-HH-MM-SS BCD format. |
| 28 | Additional Info Items | EXT_ITEMS | Optional TLV items: Mileage (0x01, DWORD), Fuel level (0x02, WORD), Speed sensor (0x03, WORD), etc. |
9.12.1 Definition of Location Alarm Flag Bit (Table 19)#
| Bit | Alarm Definition | Bit | Alarm Definition |
|---|---|---|---|
| 0 | SOS emergency alarm (terminal trigger) | 16 | VSS vehicle speed sensor abnormal |
| 1 | Overspeed alarm | 17 | Abnormal vehicle oil level |
| 2 | Fatigue driving alarm | 18 | Cumulative driving overspeed |
| 3 | Danger early warning | 19 | Overtime parking alarm |
| 4 | GNSS module failure | 20 | In/Out area geofence breach |
| 5 | GNSS antenna disconnected | 21 | In/Out route breach |
| 6 | GNSS antenna short circuit | 22 | Insufficient / excessive travel time on route |
| 7 | Terminal main power undervoltage | 23 | Route deviation alarm |
| 8 | Terminal main power disconnected | 28 | Illegal vehicle ignition alarm |
| 9 | Terminal display / LCD failure | 29 | Illegal vehicle movement / towing |
| 10 | TTS speech module failure | 30 | Vehicle collision warning |
| 11 | Camera failure | 31 | Vehicle rollover warning |
9.12.2 Definition of Status Bit for Location Information (Table 20)#
| Bit | Status Definition | Bit | Status Definition |
|---|---|---|---|
| 0 | ACC state (0: ACC OFF, 1: ACC ON) | 10 | Vehicle fuel line state (0: Normal, 1: Disconnected) |
| 1 | Positioning state (0: Unfixed, 1: Fixed) | 11 | Vehicle electrical circuit (0: Normal, 1: Cut off) |
| 2 | Latitude hemisphere (0: North, 1: South) | 12 | Vehicle door lock state (0: Unlocked, 1: Locked) |
| 3 | Longitude hemisphere (0: East, 1: West) | 18 | GPS positioning constellation enabled |
| 4 | Operating state (0: In service, 1: Suspended) | 19 | Beidou (BDS) positioning enabled |
| 5 | Position encryption (0: Plain, 1: Encrypted) | 20 | GLONASS positioning enabled |
9.13 Data Downlink Transparent Transmission — 0x8900#
Message ID: 0x8900 | Direction: Platform -> Terminal (Downlink)
Transfers proprietary downstream commands including vehicle remote control (0xF1) and CAN learning parameters.
Table: Data Format of Data Downlink Transparent Transmission Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Transparent Message Type | BYTE | 0xF1: Vehicle remote control command. |
| 1 | Transparent Message Content | BYTES | Control payload (door lock/unlock, trunk, remote cut-off). |
9.14 Data Uplink Transparent Transmission — 0x0900#
Message ID: 0x0900 | Direction: Terminal -> Platform (Uplink)
Container for high-level telematics data: OBD-II live telemetry, trouble codes, driving behaviors, trip summaries, and CAN data.
Table: Data Format of Data Uplink Transparent Transmission Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Transparent Message Type | BYTE | 0xF0: Telematics uplink data stream. |
| 1 | Message Subcategory | BYTE | 0x01: OBD stream; 0x02: Trouble codes; 0x03: Alarms & driving behavior; 0x04: Travel summary; 0x05: Logs; 0x06: CAN learning; 0x0B: VIN; 0x0C: Inspection; 0x0D: Self-test; 0x0F: Function list; 0x15: Emergency event packet. |
9.14.1 Transparent Sub-Command Types#
| Sub-Command Type | Name | Purpose |
|---|---|---|
| 0xF0 | Standard Vehicle Telemetry Upload | Carries OBD data streams (Table 25), driving behaviors (Table 28), DTCs, VIN |
| 0xF1 | Diagnostic Command Response | Returns result of downlink transparent AT/CAN diagnostic command |
9.15 Set Circular Geofence — 0x8600#
Message ID: 0x8600 | Direction: Platform -> Terminal (Downlink)
Configures a circular boundary with latitude, longitude, radius, and trigger conditions.
Table: Data Format of Set Circular Geofence Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Setting Attribute | BYTE | 0: Update area; 1: Append area; 2: Modify area. |
| 1 | Total Areas | BYTE | Number of circular regions. |
| 2 | Area ID | DWORD | Unique identifier for this geofence zone. |
| 6 | Area Attribute | WORD | Bit flags: enter alarm, exit alarm, speed limit enabled, time range enabled. |
| 8 | Center Latitude | DWORD | Center latitude in degrees * 10^6. |
| 12 | Center Longitude | DWORD | Center longitude in degrees * 10^6. |
| 16 | Radius | DWORD | Radius of circular zone in meters. |
9.16 Delete Circular Geofence — 0x8601#
Message ID: 0x8601 | Direction: Platform -> Terminal (Downlink)
Removes designated circular zones from terminal memory.
Table: Data Format of Delete Circular Geofence Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Area Count | BYTE | Number of areas to delete (0 = delete all). |
| 1 | Area ID List | DWORD[n] | Array of 4-byte area IDs. |
9.17 Set Rectangular Geofence — 0x8602#
Message ID: 0x8602 | Direction: Platform -> Terminal (Downlink)
Configures rectangular geofence bounding boxes (top-left & bottom-right coordinates).
Table: Data Format of Set Rectangular Geofence Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Setting Attribute | BYTE | 0: Update area; 1: Append area; 2: Modify area. |
| 1 | Total Areas | BYTE | Number of rectangular regions. |
| 2 | Area ID | DWORD | Unique zone ID. |
| 6 | Area Attribute | WORD | Trigger attributes: enter/exit alarm, speed limit. |
| 8 | Upper-Left Latitude | DWORD | Top-left corner latitude * 10^6. |
| 12 | Upper-Left Longitude | DWORD | Top-left corner longitude * 10^6. |
| 16 | Lower-Right Latitude | DWORD | Bottom-right corner latitude * 10^6. |
| 20 | Lower-Right Longitude | DWORD | Bottom-right corner longitude * 10^6. |
9.18 Delete Rectangular Geofence — 0x8603#
Message ID: 0x8603 | Direction: Platform -> Terminal (Downlink)
Deletes designated rectangular zones from device memory.
Table: Data Format of Delete Rectangular Geofence Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Area Count | BYTE | Number of rectangular areas to delete (0 = delete all). |
| 1 | Area ID List | DWORD[n] | Array of 4-byte area IDs. |
9.19 CAN Bus Data Upload — 0x0705#
Message ID: 0x0705 | Direction: Terminal -> Platform (Uplink)
Raw CAN frame stream upload with high-precision timestamps for vehicle bus diagnostic logging.
Table: Data Format of CAN Bus Data Upload Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | CAN Item Count | WORD | Number of CAN frame items included. |
| 2 | Receive Time | BCD[5] | First frame timestamp (hh-mm-ss-ms*10). |
| 7 | CAN Items | CAN_FRAME[n] | Frame items: CAN Channel (1B) + Frame ID (DWORD, 4B) + Data (BYTE[8]). |
9.20 Sending Text Message — 0x8300#
Message ID: 0x8300 | Direction: Platform -> Terminal (Downlink)
Platform sends text notification or synthesized voice message to vehicle screen/audio terminal.
Table: Data Format of Sending Text Message Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Text Flag | BYTE | Bit flags: Emergency (bit 0), LCD display (bit 2), TTS voice (bit 3), Advert display (bit 4). |
| 1 | Text Information | STRING | GBK/Unicode encoded text message content. |
9.21 Response to Text Message Sending — 0x0303#
Message ID: 0x0303 | Direction: Terminal -> Platform (Uplink)
Terminal acknowledgment for text message display.
Table: Data Format of Response to Text Message Sending Message Body
| Start Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Response Flow Number | WORD | Corresponding 0x8300 message flow number. |