3 devices 2 brands

IoTM Protocol

Binary IoTM fleet protocol on Traccar TCP 5218 publishing door, brake, cargo weight, trailer id, and cornering attributes.

Connect your tracker

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

Browse 3 supported devices

Quick answers

Port?

TCP 5218.

Signature attributes?

Door corners, brakes, cargoWeight, trailerId, cornering.

ASCII?

No — binary IoTM frames.

Commands?

One pathway exists on IotmProtocol; Traxelio still positions_only.

Confuse with M2C?

M2C is ASCII on 5157 with different field semantics.

IoTM is a binary fleet dialect on TCP 5218. Traccar’s decoder surfaces cabin and cargo IO that thin ASCII shells never carry: doorFL / doorFR / doorRL / doorRR, handBrake, footBrake, cargoWeight, trailerId, cornering, and buttonPresent. The protocol class also registers a data-command pathway — still catalogue positions_only in Traxelio until that path is productized.

Why IoTM pages must not reuse Motor prose

Motor is a minimal line identity problem. IoTM is an IO matrix problem. If your ticket is “left rear door open while trailer id X is coupled,” you are in IoTM territory.

Sibling caution

M2C on 5157 is dense ASCII with archive/priority headers — not this binary door matrix.

Setup walkthrough

  1. 1

    Confirm IO-heavy firmware

    Door/brake/cargo fields in the vendor list → IoTM.

  2. 2

    APN then host:5218

    Binary listeners stay dark without data.

  3. 3

    Decode a frame with door bits

    Prove doorFL..RR before arguing map delay.

  4. 4

    Note trailerId if present

    Coupling identity is part of the IoTM value.

  5. 5

    Command tests last

    Only after positions + IO attributes are stable.

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.

Reference

Configuration reference

Parameter Value
Port 5218

Telemetry fields

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

All Models

All Iotm Devices (3)

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

FMS500

FMS500

FMS500 StScan

FMS500

Xirgo XG37 Series

Xirgo

Compatible Brands

Brands Using Iotm Protocol

FMS500

2 devices

Xirgo

1 device

Common troubleshooting

Positions without doors

IO report mask disabled — enable digital inputs in firmware.

Trailer id always blank

Some SKUs omit trailer probes; hardware may lack the sensor.

Cornering never increments

Needs IMU-capable firmware; not universal.

Explore More

Other Protocols

M2C

1 device

VT200

2 devices

Bstpl

2 devices
View All Trackers

FAQ

Frequently Asked Questions

Fleet vs asset seal?

IoTM is cabin/cargo vehicle IO. Eseal is padlock tamper events on 5169.

Open reference?

IotmProtocolDecoder + port 5218.

Connect Iotm tracker
T
Trax
Online
Say hello to Trax!