FleetCommando logo FleetCommando · Manual
On-site installation

Wire up the tracker, mount it, see it on the map

Step-by-step for the field engineer fitting a Teltonika FMB-series GPS tracker into a vehicle. Targets are: continuous power, ignition wire detection, antenna line-of-sight, immobilizer relay (optional), and a verified online state on the FleetCommando dashboard before you leave the yard.

Pre-arrival checklist

Wiring

FMB-series devices have a 12-pin connector. The four wires you must attach for a working installation:

⚡ Power & ignition
  • VCC (red) — constant 12 V or 24 V from a fused source. Tap the battery + terminal or a fused +12V always-on circuit. Add an inline 5A blade fuse close to the source.
  • GND (black) — chassis ground or battery negative.
  • IGN (yellow) — switched 12V, hot only when the key is in the ON or START position. Tap the radio's switched-power feed or a fused ignition circuit. Without this, FleetCommando can't tell when the engine is running.
🔧 Optional: immobilizer relay (cut fuel)
  • DOUT1 (white) — drives a 40A relay that breaks the fuel pump's positive line. When DOUT1 is high (immobilize), the relay opens and the pump loses power. When DOUT1 is low (mobilize), the relay closes and fuel flows again.
  • Place the relay's coil between DOUT1 and ground. Use a flyback diode if your relay doesn't include one.
  • Splice the fuel pump's +12V line through the relay's normally-closed contacts. Mark the splice + take a photo for the customer's records.
Don't tap the alternator's main bus directly. The voltage regulator spikes during load transients can fry the device. Always go through a fused switched circuit.

Antenna placement

Mounting the device

  1. Pick a dry spot (under-dash, behind the glove box, beneath the driver's seat). Avoid hot zones (engine bay, near exhaust).
  2. Wipe the surface, peel the 3M VHB backing, press for 30 seconds.
  3. Coil and zip-tie the harness so it can't snag. Apply dielectric grease to any spliced joints if the install is in a humid / coastal environment.
  4. Power on. The status LED on FMB-series should go through: solid (booting) → blinking blue (acquiring GPS) → fast blue (online).

Pair on the FleetCommando dashboard

  1. Sign in to fleet.midaspathsoftwaresolutions.com with the operator's account (or use Platform Admin → Impersonate if doing this for them).
  2. Open Devices. Find the device you pre-added by IMEI.
  3. Confirm the green online dot appears. Telematics → Devices should show GSM bars and a "Last seen" timestamp within 30 seconds of power-on.
  4. Open Live Map. Drive the vehicle outside if no GPS lock yet — most FMB devices need 30–60 seconds of clear sky for first fix.
  5. Within 2 minutes, the vehicle's marker pulses green on the map.
Acceptance test. Before signing off the install, drive a 5 km loop with the customer or operator on a phone watching the dashboard. They should see the map marker move in real time, the trail draw behind it, and the trip appear under Trips when the engine cuts off at the end.

Hand-off

Common gotchas

🛑 No GSM bars after install
  • SIM not activated — call your provider, request data + SMS APN.
  • SIM seated wrong — eject, re-seat, ensure it clicks.
  • Country lock — some SIMs only roam onto specific carriers; FMB devices follow the SIM, so verify with the provider.
🛑 Online but no GPS fix
  • Internal antenna is blocked by metal — fit external GPS antenna.
  • Test outside / clear sky for 5 minutes.
  • Cold start in a new region can take 60+ seconds.
🛑 Ignition stays "OFF" even when engine is running
  • IGN wire is on the wrong feed (constant 12V instead of switched). Re-tap the radio's switched circuit and verify with a multimeter that it goes 0 V → 12 V when you turn the key.

Reference: Codec 8 + Codec 12

FleetCommando ingests Codec 8 / Codec 8 Extended for telemetry and uses Codec 12 for outbound commands (immobilize, getver, horn pulse). No special device-side configuration needed — every FMB-series device ships with Codec 8 enabled by default. You can verify the device firmware via Remote command → Get version in the dashboard.