Skip to main content

Concox/Jimi GT06 v2

Status: Works today: built into ZAITRACK for every organisation.

KindVersionPublisherLicence
Device codec1.0.0ZAITRACKApache-2.0

What it does​

Concox / Jimi GT06 protocol (GT06, GT06N and compatibles), widely deployed across budget vehicle trackers: 0x7878 | LEN | PROTO | INFO | SERIAL | CRC-ITU | 0x0D0A. Decodes login (0x01), heartbeat (0x13), GPS+LBS locations (0x12, 0x22 with ACC) and alarms (0x16, the standard alarm codes named), verified against the protocol document's login example and real device packets. Model variants that put the IMEI before the GPS block are refused, not guessed. Online commands (0x80) encode relay 1 cut/restore, locate, diagnostics and explicit ASCII passthrough; the configured relay or DYD/HFYD dialect is used. Command replies (0x15, 0x21) are decoded.

  • Devices: vehicle_tracker, asset_tracker
  • Transport: tcp
  • Commands: engine-cut, engine-restore, output-set, locate-now, diagnostics-run, vendor-passthrough
  • Capabilities: telemetry.position

How to use it​

Built in: register the device in the console and choose its protocol. Where it connects, and its settings: https://docs.zaitrack.app/fleet/connect/concox-gt06.

Its listing: https://marketplace.zaitrack.app/browse/gt06-codec.

Configuration​

None: built in, it has no settings of its own; a device's own settings are on its Connect page.

Credentials​

None.

Limits​

Built in, it runs inside codec-runtime itself today. These are the limits it asks for as a WASM module in codec-runtime's sandbox:

  • Memory: 32 MB
  • Time per call: 100 ms
  • Instructions per call (fuel): 2,000,000,000
  • Largest message: 65,536 bytes
  • Calls per second: 8,000
  • Network: no network access
  • Its own key-value store: up to 1,024 keys of 4,096 bytes

Troubleshooting​

  • The device does not connect. Check the host and port its Connect page gives for your region, that the SIM has data and the APN is set, and that the device sends to that host (some send to the last server they were given).
  • It connects but no position arrives. The device must be registered with this protocol and the IMEI or serial it reports: a device the platform does not know, or a retired one, is refused when it connects. Trackers shows it as Check (never reported) until its first position.
  • Positions arrive with the wrong time. The protocol's timestamps are UTC; a device set to local time reports hours off. Set it to UTC.
  • A command does not reach the device. Only the commands listed under Commands are sent; the device must be online, and some models need the command enabled in their own configuration.

Source​

adapters/codecs/concox-jt06-v2