Skip to main content

Jointech JT701

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

KindVersionPublisherLicence
Device codec1.0.0ZAITRACKApache-2.0

What it does​

JT701 binary seal status, battery and position, plus inherited JT600 tracker U/W positions. P45 is an authorization report, never physical proof that a lock opened or armed. By default P45 retains identity and raw diagnostic fields only: no assumed speed units, validation result or reply. For a verified legacy JT701 V3.6 device, the installed adapter configuration {"ascii_profile":"legacy_v3_6"} enables P45 km/h, separate card/dynamic/password validation and exact (P46) receipt. This is not JT701D support. The native built-in listener has no selected-profile handoff and remains diagnostic-only for P45. Binary physical state is independent; pre-0x19 status-bit-5 receipts retain (P35), while unverified later P69 receipts are not sent. Unconfirmed devices may retry; assess compatibility before rollout. This codec implements no outbound command, including remote unlock. Legacy field semantics are based on a manufacturer-attributed V3.6 text mirror, not verified original PDF bytes or a hardware/firmware certification; full provenance and compatibility limits are in source README.

  • Devices: e_lock, e_seal, asset_tracker
  • Transport: tcp
  • Commands: None.
  • Capabilities: telemetry.position, telemetry.seal, telemetry.battery

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

Its listing: https://marketplace.zaitrack.app/browse/jointech-elock.

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/jointech-jt701