GT06N, JM-VL01, AT4 and the wider Concox range report over the GT06 protocol family. The platform decodes it — including the variants that appear on cloned hardware sold under other names.
The best price per tracked vehicle in the market, which is why it dominates entry-level fleet and vehicle-finance deployments.
Protocol-level facts from the manufacturer’s own documentation. Model-level behaviour varies within a series, so confirm your exact unit with us rather than assuming.
| Item | Supported | Notes |
|---|---|---|
| Protocol family | GT06 and derivatives | Compact binary framing, widely cloned |
| Transport | TCP | Persistent connection with keepalive |
| Series commonly deployed | GT06N, JM-VL01, JM-LL01, AT4, X3, GT300 | Vehicle, asset and portable form factors |
| Relay / immobilisation | Supported on wired vehicle models | Command acknowledged by the device before the platform reports success |
| Fuel sensing | Analogue input on selected models | Lower resolution than a digital probe — calibrate before relying on it |
| Alarms | SOS, vibration, power cut, low battery, geo-fence | Arrive as distinct event codes |
| Remote configuration | SMS commands | Server, APN and reporting interval all settable remotely |
Most platform vendors publish a list of supported model numbers. It looks reassuring and it is usually out of date, because it describes a snapshot of what somebody tested once rather than how the integration actually works. GPS platforms do not implement models; they implement protocols. Concox devices report over GT06 family (binary) across TCP, and the platform decodes that protocol — which is why a new unit in the GT06N, GT300, JM-VL01, JM-LL01, AT4, X3 families generally works on the day it ships rather than after a development cycle.
What genuinely varies between models is not the protocol but the hardware: which inputs physically exist, whether a CAN interface is present, whether there is a relay output, how many 1-Wire devices can be attached. That is why we ask for your exact model and firmware version rather than publishing a matrix. It takes us a day to confirm against a live server, and it is the difference between a deployment that works and one that discovers a missing input after the units are installed.
Send the model, the firmware version and what you need to report on. You will get back a straight answer on three things: whether the unit reports into the platform at all, which of your required data points it can actually produce, and whether a cheaper unit in the same range would do the same job. That last one costs us margin and saves you money, which is the point — a fleet that buys the wrong hardware blames the platform.
Concox units already in the field can be re-pointed to a new server remotely, so a migration does not mean visiting vehicles. We audit what is connected first, import your historical data, re-point a pilot group, and cut the rest across only once the pilot reconciles cleanly against your old system. The old endpoint stays live through the window. Full detail is on the hosting and migration page.
Send your Concox model list and we will confirm compatibility against a live server before you commit. Request a compatibility check or message us on WhatsApp — include firmware versions if you have them, and tell us what you need to report on.
The GT06 protocol family is implemented, which covers the GT06N and the widely deployed Concox range built on it. Because the protocol is heavily cloned, we ask for one physical sample of the exact unit you intend to buy and test it against a live server before you place a bulk order.
Because the label on the case is not the protocol. Dozens of manufacturers ship GT06-derived firmware under their own brands, and while the framing usually matches, the IO mapping frequently does not — an input that means ignition on one unit can mean door sensor on another. Testing one sample takes a day and prevents discovering the mismatch after 500 installations.
On wired vehicle models with a relay fitted, yes. The command is queued and the platform reports the cut as successful only once the device acknowledges it, so the interface shows the actual state of the vehicle rather than the state of the request. The action is permission-gated and every use is logged against a user.
The analogue input on the models that offer it is workable for trend detection but noticeably coarser than a digital RS232 or RS485 probe. If fuel loss is the business case, fit a proper probe — on Concox or on a tracker that supports one — rather than relying on the analogue reading.
Concox devices fall back to LBS cell positioning, which the platform stores and displays as a distinctly lower-confidence position rather than presenting it as a GPS fix. That distinction matters when a position is used as evidence.
Send us your exact models and firmware versions. We will test them against a live server and tell you what works before you commit to anything.
Check My Device →