Xexun RMC
Status: In development: its code is written and tested on its own, but it does not work end to end on the platform yet. It cannot be installed.
| Kind | Version | Publisher | Licence |
|---|---|---|---|
| Device codec | 1.0.0 | ZAITRACK | Apache-2.0 |
What it does
Candidate basic RMC profile with explicit IMEI, verified NMEA checksum and signal validity. ARM extensions, outgoing commands and hardware acceptance remain open. Not enabled for customer use.
- Devices:
vehicle_tracker - Transport:
tcp - Commands: None.
- Capabilities:
telemetry.position
How to use it
Not yet: see its status above.
Configuration
| Setting | Type | Required | Allowed values and default |
|---|---|---|---|
profile | string | no | one of rmc-basic-v1; default "rmc-basic-v1" |
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: 50 ms
- Instructions per call (fuel): 50,000,000
- Largest message: 4,096 bytes
- Calls per second: 2,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/xexun