8 devices 2 brands

Aplicom Protocol

Aplicom CAN/event binary on Traccar TCP 5049, including cold-unit telemetry and active-alarm hex payloads.

Connect your tracker

Enter the tracker IMEI first, then verify your email and continue setup.

Browse 8 supported devices

Quick answers

Stock port?

TCP 5049.

Why cold-unit fields?

Decoder maps reefer sensors and activeAlarm explicitly.

ASCII?

No — AplicomFrameDecoder binary.

Aplicom is a binary CAN/event dialect on TCP 5049. AplicomFrameDecoder feeds AplicomProtocolDecoder, which branches across event/CAN helpers (decodeEventData, decodeCanData, decodeD/E/H/EB/F). Cold-unit fields — diesel/electric hours, defrost temps, condenser/suction pressures, setpoints, activeAlarm, coldUnitState — are first-class in the open decoder.

Alarm hex is not a map bug

When activeAlarm / event data is present but coordinates look stale, treat it as an alarm/event frame class, not GPS failure.

Sibling contrast

Eelink on 5064 also carries binary IO, but Eelink’s old/new packages and BLE MAC tags are not Aplicom’s cold-unit vocabulary.

Catalogue stance

Traccar stock reference; Traxelio positions_only.

Setup walkthrough

  1. 1

    Confirm Aplicom CAN/event firmware

    Reefer/CAN sheets — not Eelink BLE tag manuals.

  2. 2

    Server TCP 5049

    Host + 5049; reboot.

  3. 3

    Capture event vs CAN frame

    Keep hex for an alarm event and a normal position.

  4. 4

    Validate cold-unit fields if fitted

    Check setpoints/pressures/hours after positions decode.

Setup

Public setup commands

Use these rows only after confirming the tracker password and SIM settings. Command families can differ between brands even when they use the same protocol.

Setup guidance

Connection supported

gps.traxelio.com:5049 4 example models
A1 M2M A1 Max A1 Trax A11

Traxelio can receive this model, but public SMS setup depends on SIM or model settings.

Reference

Configuration reference

Parameter Value
Port 5049

Telemetry fields

GPS Location Speed Altitude Heading / Direction Street Address GPS Accuracy Ignition Status Odometer / Mileage Battery Level

All Models

All Aplicom Devices (8)

Start with the strongest matches, then use pagination or brand pages for the full compatibility list.

A11

A11

A1 M2M

Aplicom

A1 Max

Aplicom

A1 Trax

Aplicom

A5 GLX

Aplicom

A9

Aplicom

Aplicom C-series

Aplicom

Aplicom Q-series

Aplicom

Compatible Brands

Brands Using Aplicom Protocol

Aplicom

7 devices

A11

1 device

Common troubleshooting

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.

Explore More

Other Protocols

Eelink

25 devices

Bce

10 devices

Galileo

12 devices
View All Trackers

FAQ

Frequently Asked Questions

Only for reefers?

Cold-unit fields are prominent, but broader CAN/event payloads also decode.

Command set claimed?

Not claimed. positions_only.

HTTP like OsmAnd?

No — binary TCP 5049.

Connect Aplicom tracker
T
Trax
Online
Say hello to Trax!