Concox and Jimi IoT Trackers: Pick the Right GT06 Profile and Test Without Hardware
Concox and Jimi IoT trackers speak different GT06 dialects. Pick the right profile, understand the login ACK and test your platform without hardware.
Concox and Jimi IoT are one company: Concox is the older brand name and is now part of Jimi IoT. Together they make some of the most widely deployed budget trackers - the GT06N, CRX1, and the VL and LL series - and almost all of them talk to servers over GT06, Traccar port 5023.
But GT06 has dialects, and picking the wrong one is the fastest way to a parser that works on your desk and fails in the field.
Which Profile Matches Your Device
Telemify offers three GT06 device profiles:
- GT06 classic - for the original GT06 / GT06N and their clones. 13-byte login, positions in packet type 0x12.
- Jimi 2G - for 2G devices on the newer Jimi protocol. 17-byte login, positions in packet type 0x22.
- Jimi 4G (default) - for 4G devices on the newer Jimi protocol. 17-byte login, positions in packet type 0xA0.
Not sure which one you have? The protocol document that comes with the device lists the position packet type: 0x12, 0x22 or 0xA0. Newer Jimi IoT models, such as the JM-LL301, GK310 and VL series, use the Jimi protocol.
What the Jimi Profiles Add
The Jimi profiles send more than position and battery. External voltage, temperature, humidity, door state and odometer travel in a separate information message, on the first position and then on every 10th. Their heartbeats carry the battery as a voltage.
The classic profile, and alarms on every profile, send the battery as one of 7 levels, which servers show as 0, 17, 33, 50, 67, 83 or 100 %. No profile can send an exact battery percentage, engine hours or RPM.
On Traccar, external voltage shows up as adc1 rather than power - worth knowing before you map attributes.
The Login ACK Tells You More Than You Think
A GT06 device logs in first and waits for the server's acknowledgement. Traccar only acknowledges devices it knows, so an unregistered IMEI means no ACK, and a real device just keeps retrying.
In Telemify, Wait for the server login reply is on by default. If the ACK never comes, the run stops with an error, so you know straight away that the IMEI isn't registered. flespi works too, including battery, external voltage, temperature, humidity and mileage.
Alarms You Can Test
SOS, power cut, vibration, geofence enter and exit, overspeed, tow, door, low battery, collision, fuel theft and high or low temperature, all scheduled on a timeline in the Alarms & Events tab.
How the frames work byte by byte: GT06 protocol explained. Need a server? Set up Traccar in Docker.