10 devices
2 brands
Aplicom Protocol
Aplicom CAN/event binary on Traccar TCP 5049, including cold-unit telemetry and active-alarm hex payloads.
On Traxelio
What Aplicom trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Aplicom
Point this protocol at Traxelio
Point Aplicom at Traxelio
-
1
Confirm Aplicom CAN/event firmware
Reefer/CAN sheets — not Eelink BLE tag manuals.
-
2
Server TCP 5049
Host + 5049; reboot.
-
3
Capture event vs CAN frame
Keep hex for an alarm event and a normal position.
-
4
Validate cold-unit fields if fitted
Check setpoints/pressures/hours after positions decode.
Still offline after GPS lock
Aplicom still not landing
- Bound to Eelink 5064
Retarget to 5049; BLE packages will not parse Aplicom cold-unit frames.
- Alarms without coordinates
Expected for some event frames; inspect activeAlarm/eventData before a GPS reset.
- IMEI validation failures
Open decoder validates IMEI derived from unit id — confirm unit id config.
FAQ
Aplicom leftover questions
Only for reefers?
Cold-unit fields are prominent, but broader CAN/event payloads also decode.