Skip to main content

Carrier Reefer Link

Status: Planned: not built. The maker does not publish its protocol or interface; ZAITRACK builds it once it does.

KindVersionPublisherLicence
Device codec1.0.0ZAITRACKApache-2.0

What it does​

Experimental: Carrier Transicold's reefer telematics — Lynx Fleet (its API toolkit and specification document) and DataLINK — are available to dealers and partners only; nothing at wire or API level is published. Every frame is refused and no command is encoded until the protocol document is in hand.

  • Devices: reefer
  • Transport: tcp, mqtt
  • Commands: None.

How to use it​

Not yet: see its status above.

Configuration​

SettingTypeRequiredAllowed values and default
strict_validationbooleannodefault true

Credentials​

None.

Limits​

It runs in codec-runtime's WASM sandbox, within these limits (the platform's own ceilings bound them too):

  • 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/carrier-reefer-link