Skip to main content

JT/T 808 terminals

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

KindVersionPublisherLicence
Device codec1.0.2ZAITRACKApache-2.0

What it does​

JT/T 808-2013 and -2019 terminals (MDVRs and trackers): registration and authentication, locations and blind-spot batches with alarm and status flags, mileage and fuel; the T/JSATL 12-2017 active-safety alarms (ADAS, driver monitoring, tyre pressures, blind spot) and the JT/T 1078-2016 video alarms; live video and recorded footage (JT/T 1078); position, attribute and vehicle-control answers.

  • Devices: mdvr, vehicle_tracker
  • Transport: tcp, udp
  • Models: JT/T 808-2013 and 808-2019 terminals, Howen Hero-ME31, Howen Hero-ME41, Streamax X1N
  • Commands: engine-cut, engine-restore, locate-now, diagnostics-run, vendor-passthrough, seal-disarm, ota-trigger, video-live-start, video-live-stop, video-alarm-attachments, video-recordings-list, video-playback-start, video-playback-stop
  • Capabilities: telemetry.position, telemetry.video, telemetry.adas, telemetry.tpms, command.engine-cut, command.passthrough, command.video

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/jt808.

Its listing: https://marketplace.zaitrack.app/browse/jt808-video.

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

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/jt808