Documentation

Commands

A command is a message to a tracker: ask it for its status, switch a relay, change a setting, set its odometer. The Commands page keeps the commands you send often as saved commands, links them to the devices that may receive them, and lists every command sent with the tracker's reply.

You send commands from a vehicle's card on the Tracking page.

Saved Commands

The Saved tab lists your saved commands:

• Description — the name you gave it, with the text it sends.
• Command — a built-in command (from your tracker model's list) or a tracking server type, and SMS when it is sent by text message.
• Devices — the devices and groups it is linked to.
• Users — who can use it.
• Sync — whether it's saved on the tracking server; Retry when that failed.

Search by command, device or group; the Built-in and Server types chips narrow the list. Export downloads the list to Excel or prints it.

Adding a Command

1. Click New command.
2. Pick the Devices (and Groups) first — each device is listed by its name with its model. The Command list stays disabled until you do, then only shows the commands every picked device can take.
3. Pick the Command. The list has:
   • Built-in commands for your tracker models, grouped as Common, Bluetooth, Features, OBD and CAN adapter — for example Device info, Set outputs, Set odometer, Fault codes.
   • Tracking server types — the general commands the tracking server knows, such as Custom Command (any text), Engine Stop or Position Periodic.
4. Fill in its fields. Sends shows the exact text the tracker will receive, e.g. setdigout 1? 60.
5. The Description follows the command you pick; change it if you like.
6. Optional: Don't queue — when the tracker is offline the command is dropped instead of waiting until it connects. Send as SMS appears when the tracking server can send text messages.
7. Pick the Users who may use it, or leave it empty for everyone who can send commands.
8. Click Save command.

A command linked to a group reaches every device in that group and its subgroups, and has to suit all of them.

When you save, every linked device is checked: a command some of them can't take isn't saved, and the form names those devices.

Built-in Commands

Built-in commands come from the manufacturer's command list for each model. They are available for the Teltonika FMB003, FMB020, FMB125, FMB140, FMB204, FMB920, FMC130 and FMC650. Each model only gets the commands it supports — for example, CAN adapter commands only for models that take a CAN adapter, output commands only for models with outputs.

The tracker model comes from the device's Model on the Devices page. If a picked device has no model, or a model the app has no command list for, the list shows the tracking server commands all the trackers support — the same list the tracking server offers for them. A command specific to that device can still be sent as a Custom Command with its text.

Some commands are listed but disabled, with the reason. They could take a tracker off the platform or wipe its data:

• moving it to another server,
• loading the default configuration,
• locking or unlocking its configuration,
• deleting stored records or formatting its memory card.

Commands that change the vehicle or the tracker — outputs (relays), engine block, doors, restart, clearing fault codes, changing parameters, setting the odometer — are marked with a shield. They ask for confirmation before they are sent, and only users who can create commands can send them.

Sending a Command

On the Tracking page, select a vehicle and click Commands on its card. It lists only the saved commands linked to this vehicle's device (directly or through its group) that you may use — to send something new, save it here first and link it to the device. Pick one and click Send. The latest commands sent to the vehicle are listed below with their status.

Status

Some commands never answer (Restart tracker, Send a record now); they stay at Sent or Delivered.

A tracker's reply doesn't say which command it answers. It is matched to the oldest command still waiting on that vehicle, so send one command at a time and wait for the reply.

History

The History tab lists every command sent to your vehicles, newest first: time, vehicle, command and its text, who sent it, status and the tracker's reply. Filter by Device or Status (Waiting, Replied, Queued, Failed). Statuses update live.

Setting a Tracker's Odometer

To make the odometer match the vehicle, open the vehicle on the Vehicles page, type the real reading in Total Distance and click Set on the tracker. The tracker's own odometer is set and its reply is shown. If it doesn't reply, save the vehicle with Total Distance instead — see Total Distance and Engine Hours.

On a Phone

Saved commands are cards; New command at the bottom opens the form full screen. History is the second tab. On the Tracking page, Commands is in the vehicle card's actions.

Permissions

Team owners have everything. Client users have no access to commands at all. Users limited to certain vehicles (contractors) only see the commands linked to their own vehicles' devices, and can't create commands.