CalAmp LMU
Guided setup available
Ask the tracker to read back its settings
!R0APN commands depend on the carrier SIM in your tracker, so they are not shown here.
27 devices
1 brand
CalAmp LM Direct Protocol
Binary UDP / TCP protocol published by CalAmp (Irvine, California, NASDAQ: CAMP) for the LMU, MTM, and MXT vehicle and asset tracker families · the North American fleet-tier alternative to Teltonika and Geotab.
On Traxelio
What Calamp trackers do once they are on Traxelio
Geo-Zones
Get alerted when vehicles cross boundaries
Driving Behaviors
PremiumDriver scoring software to reduce accidents and insurance costs
Predictive Maintenance
PremiumAutomated maintenance scheduling that prevents breakdowns
Trip History
Every trip recorded, every dispute settled
Immobilizer request for compatible installations
Immobilizer requests for compatible installations
Fuel Level Monitoring
PremiumSee fuel level, volume, and consumption for every vehicle
Hardware that speaks this protocol
Devices that speak Calamp
Point this protocol at Traxelio
Point Calamp at Traxelio
-
1
Download CalAmp Configuration Tool
Windows desktop tool from CalAmp's developer portal. Works with any LM-Direct-compatible server · not just Phantom Web Services.
-
2
Connect the device via USB serial
LMU/MTM/MXT devices expose a USB-to-serial config port. Driver auto-installs on Windows 10+; the Configuration Tool's connection wizard auto-detects the COM port.
-
3
Set the Inbound URL
In the Server section: Inbound URL = your platform's host, Port = your platform's listener (Traccar default for LM Direct is
5082), Transport =UDP(canonical) orTCP. -
4
Optional · review PEG script
If the device has a custom PEG (Programmable Event Generator) script for geofence / accelerometer triggers, review the script's
sendmsg()IDs to confirm they won't collide with CalAmp's canonical message types on the new server. -
5
Save and reboot
Save to Device, power-cycle. Confirm the first decoded position in Traxelio.
gps.traxelio.com:5082
TCP
What Traxelio surfaces from these packets
Calamp fields Traxelio reads
- GPS Location
- Speed
- Altitude
- Heading / Direction
- Street Address
- GPS Accuracy
- Ignition Status
- Odometer / Mileage
- Engine Hours
- Battery Level
- Fuel Level
- Network / Cell Info
Still offline after GPS lock
Calamp still not landing
- Device sends UDP packets but server doesn't ACK them, then nothing arrives
Some CalAmp firmware variants require server-side ACK for User-Defined messages even though UDP itself doesn't · without the ACK, the device assumes the server is dead and stops sending. Confirm Traxelio's ingestor is sending the ACK opcode (0x80) on each received message. Less common: firewall is dropping UDP return packets · check ingress / egress rules on the cellular APN.
- OBD-II PIDs come through on some vehicles but not others
OBD-II PID availability is per-vehicle-make/model · not all cars expose all PIDs via the OBD-II port. Fuel level (0x2F) in particular is optional and rarely exposed on European vehicles · for accurate fuel monitoring on those, use the LMU-3640 wired to the fuel-sender wire instead of the OBD-II MTM variant.
- PEG script fires events as expected but Traxelio doesn't decode them
Custom PEG-generated events use User-Defined message IDs that may collide with CalAmp's canonical event IDs · check the PEG script's
sendmsg()calls and confirm the message ID isn't reused. If the ID is custom, Traxelio's decoder needs a mapping rule (contact support).
FAQ
Calamp leftover questions
What's the difference between CalAmp LMU and MXT?
LMU = vehicle-mounted (mid-power, hardwired to ignition + accessory bus, designed for always-on fleet tracking). MXT = asset / trailer / container (low-power, internal battery, designed for periodic-report use cases where the asset isn't powered most of the time). Both speak LM Direct; the form factor and power budget differ.