Skip to content 
The H02 Protocol: A Universal Standard for GPS Tracking
In the world of Telematics and IoT, the H02 protocol stands as one of the most widely adopted communication standards for GPS tracking devices. Originally popularized by manufacturers like Sinotrack and Incutex, it has become the default language for a massive array of hardware, ranging from simple vehicle trackers to advanced 4G personal locators.
Why is H02 so popular?
The primary reason for its dominance is versatility. As seen in the extensive list of compatible hardware (including the LK-series, MV-series like MV720, and the ubiquitous ST-901), the protocol supports a broad range of features including:
- Real-time location reporting (Latitude/Longitude).
- Ignition status detection (ACC).
- Over-speed and Geofence alerts.
- Remote engine cut-off commands.
Comparison: H02 vs. Other Common Protocols
To understand where H02 fits in the ecosystem, here is a comparison with other industry standards like GT06 and JT808.
| Feature | H02 Protocol | GT06 Protocol | JT808 Protocol |
|---|---|---|---|
| Data Format | Mostly ASCII (Text) | Binary (HEX) | Binary (HEX) |
| Default Port | 5013 | 5023 / 5030 | 808 / 1078 |
| Complexity | Low (Easy to implement) | Medium | High (Government standard) |
| Best For | Generic/Budget Trackers | Professional Logistics | Commercial Trucking (China) |
| Bandwidth Use | Moderate | Low (Efficient) | High (Feature rich) |
Compatible Hardware Categories
The H02 protocol is the “backbone” for several famous device series:
- LK Series: Models like LK206, LK209, and the magnetic LK710.
- Sinotrack: The legendary ST-901 and ST-902 waterproof trackers.
- Micodus/MV Series: Hidden relay trackers like the MV720 and MV740.
- Portable/Pet: Smaller units like the RF-V8S and GF series (GF40/70L).
List of H02 Supported Devices and Trackers
1. LK Series (Asset & Magnetic Trackers)
2. Sinotrack & Micodus (Vehicle & Hidden Trackers)
3. XE & Cantrack Series
4. CCTR & CC Series (OBD & Hardwired)
- Models: CC830, CCTR, CCTR-630, CCTR-830G, CCTR-622G, CCRT809
5. Personal, Pet & Mini Trackers
6. Specialty & Miscellaneous Models
- H-Series: H02, H-02A, H-02B, H-06, H08
- i-Trac: i-Trac MT1, i-Trac VT600X
- General: TX-2, GTLT3, NT201, NT202, S31, MI-G6, AT-18, GRTQ, VT900, G-T005, AT-1, MT-1, GTRACK4G, GTR-100, FM03E, G06L, TK100, Secumore G05
Sample Raw Message Structure
*), followed by a manufacturer ID (often HQ), the device ID, a command/packet type, and data fields separated by commas.1. Location Data Packet (V1/V2)
- Format:
*Manufacturer,ID,V1,Time,Status,Latitude,NS,Longitude,EW,Speed,Direction,Date,VehicleStatus# - Sample:
*HQ,865205030330012,V1,145452,A,2240.55181,N,11358.32389,E,000.00,060,100815,FFFFFBFF#
- Format:
| Field | Example | Description |
|---|---|---|
| Header | *HQ | Start of message and Manufacturer ID (e.g., HQ for HuaSunTeK) |
| Device ID | 86520... | 15-digit IMEI or ID |
| Packet Type | V1 | V1 for standard GPS; V2 for LBS/Chinese address request |
| Time | 145452 | UTC Time (HHMMSS) |
| Validity | A | A = Valid GPS fix; V = Invalid/Last known position |
| Latitude | 2240.55181,N | 22°40.55181 North |
| Longitude | 11358.32389,E | 113°58.32389 East |
| Speed | 000.00 | Speed in knots or km/h (varies by model) |
| Direction | 060 | Heading in degrees (0-359) |
| Date | 100815 | Date (DDMMYY) |
| Status | FFFFFBFF | 8-digit HEX bitmask for alerts (ACC, SOS, Power) |
2. Heartbeat Packet (HTBT)
Sent by the device to keep the TCP connection alive when it is stationary.
- Sample:*HQ,865205030330012,HTBT#
Conclusion
The H02 protocol remains a cornerstone of the GPS tracking industry because of its simplicity and the massive ecosystem of manufacturers that support it. Whether you are using a Sinotrack ST-901 for your personal car or managing a fleet with LK210 units, the H02 protocol ensures your data reaches the server reliably on port 5013.
