JT808 Device Access
Page Guide
1. Access Flow
2. Product Configuration
Platform menu:
Device Management > Product ManagementRecommended configuration:
| Field | Recommended Value | Description |
|---|---|---|
| Device type | Direct device | JT808 terminals usually connect to the platform directly |
| Transport protocol | TCP or the transport protocol corresponding to JT808 | Subject to the dropdown options of the actual version |
| Communication protocol | JT808 protocol | Used to parse registration, authentication, location, and alarms |
| Authentication method | Select according to the project configuration | Can combine terminal phone number, device number, and auth code |
| Positioning method | Device positioning | The terminal reports latitude and longitude actively |
| Device authorization | Select according to project security requirements | Plan an authorization strategy for batches of terminals |
After saving the product, open the product details to view the product number, authentication information, and protocol configuration. Publish the product when configuration is complete.
3. Device Number Planning
A JT808 terminal usually has several identifiers: terminal phone number, terminal ID, plate number, and device serial number. Unify the mapping before the project starts.
| Identifier | Source | Recommended Usage |
|---|---|---|
| Terminal phone number | JT808 message header | Can be used as the device number or unique device identifier |
| Terminal ID | Device vendor documentation | Can be used as an extended field or the device number |
| Plate number | Vehicle records | Used as the device name or business extension information |
| Auth code | Registration response or platform assignment | Used for terminal authentication |
| SIM card ICCID | IoT card records | Can be associated with IoT card management |
警告
Once a device number enters the business data link, frequent changes are not recommended. If it must be changed, the associations in historical data, rules, alerts, work orders, and visualization pages must be handled at the same time.
4. Terminal Registration And Authentication
Typical flow:
- The terminal connects to the platform TCP address and port.
- The terminal sends a registration message.
- The platform creates or matches the device based on the product, device number, terminal phone number, and other information.
- The platform returns the registration response and an auth code.
- The terminal sends an authentication message.
- After authentication passes, the platform binds the online session.
Troubleshooting focus:
- Whether the TCP port is open.
- Whether the phone number or device ID reported by the terminal complies with the platform device number rules.
- Whether the product has been published.
- Whether registration and authentication use the same device identifier.
- Whether the auth code returned by the platform is saved by the terminal and used for subsequent authentication.
5. Location And Alarm Reporting
Location data should be mapped to the platform device running status, historical data, or location-related fields.
| Data | Usage | Platform Recommendation |
|---|---|---|
| Longitude/latitude | Map display and track analysis | Store as device positioning data |
| Speed | Vehicle status | Create a Thing Model property |
| Direction | Track direction | Create a Thing Model property |
| Altitude | Special scenario analysis | Configure as needed by the project |
| Alarm flag | Overspeed, fatigue driving, abnormal status | Create events or alert rules |
| Status bits | ACC, positioning, fuel circuit, power circuit | Create properties or events |
Design high-frequency location data separately from ordinary running data to avoid storage and query pressure from irrelevant fields.
6. Platform Command Delivery
Common delivery capabilities include:
- Parameter setting.
- Text delivery.
- Terminal control.
- Location information query.
- Vehicle control commands.
- Platform general response.
For secondary development, clarify:
- Where the delivery entry is displayed on the frontend.
- How the backend encapsulates commands into JT808 messages.
- Whether a command needs to wait for the terminal response.
- How response results are written back to the device log.
- How failures or timeouts are presented to the user.
7. FAQ
The terminal cannot connect
First check the TCP port, firewall, security groups, terminal APN, server address, port, and network standard.
Registration succeeds but authentication fails
Check whether the auth code returned by the platform was saved correctly by the terminal, and whether the device identifier in the terminal authentication message is consistent with the registration phase.
The device is online but the map shows nothing
Check whether latitude and longitude are parsed from location messages, whether the coordinate system needs conversion, and whether the product positioning method is device positioning.
Alarms are not triggered
Check whether alarm bits are mapped to Thing Model events or alert rules, whether the rules are enabled, and whether device data reaches the platform.
8. Secondary Development Entry Points
| Type | Path or Module | Description |
|---|---|---|
| Protocol service | springboot/fastbee-protocol | JT808 codec, message model, and protocol adaptation |
| TCP service | springboot/fastbee-server | TCP connections, sessions, and message sending/receiving |
| Device APIs | springboot/fastbee-open-api | Device, product, log, and running status APIs |
| Frontend device pages | vue3/src/views/iot/device | Device details and running status display |
| Frontend product pages | vue3/src/views/iot/product | Product protocol and Thing Model configuration |