Immobilize, mobilize, horn, getver — safely
FleetCommando can send Codec-12 commands to a connected GPS tracker. Use it for recovery (cutting fuel on a stolen vehicle), driver communication (horn pulse), or diagnostics (getver firmware probe).
The four verbs
- Immobilize — DOUT high. Cuts fuel via the immobilizer relay. Vehicle stops at the next idle. Highest risk.
- Mobilize — DOUT low. Restores fuel after a previous immobilize. Use this to release a stolen-vehicle hold once recovered.
- Horn pulse — 5-second DOUT pulse. Helps a driver locate the vehicle in a yard.
- Get version — diagnostic probe. Reads back model + firmware string.
Sending a command
- Open the vehicle, tap the red Remote command button at the top.
- Pick the verb. Immobilize shows a red safety banner explaining the consequence.
- Type a reason (≥ 4 characters — required, audit-logged).
- Tap Issue command. A second "Are you sure you want to immobilize?" card appears with No/Yes buttons.
- On Yes, the platform queues the command. If the device is online, the Codec-12 frame is written to the active TCP socket immediately and the result panel shows Sent. If offline, status is Queued — we retry when the device next reconnects (within 24h).
Permission gates
Server-side, only Admin / SuperAdmin / RootAdmin can issue Immobilize. Other verbs are gated by devices.write permission. The role check fires at the REST layer regardless of how the request was made (UI button, AI pilot, API client).
Audit trail
Every command writes a row in DeviceCommands with the verb, payload bytes, reason, your name, your role, the timestamp, the outcome (Sent / Queued / Failed), and the device's response body if any. View past commands on the vehicle's Activity tab.