Is your GPS tracker installed correctly? Eight checks before the vehicle goes back on the road

A tracker that is never verified after installation usually works — but it works wrong, silently: it reports "engine off" while the engine is running, reads the odometer from the wrong source, or sends a point every thirty seconds while you believe you are watching the vehicle live. The problem does not surface on installation day. It surfaces weeks later, when decisions are built on numbers that were never right.

That is why Asateel treats installation as a verification process, not a wiring job. These are the eight checks no device passes without.

1) Did the device reach the server?

First, the device must have handshaked with the tracking server within the last three minutes. A device that lights up but never connects usually means an inactive SIM, a wrong APN, or a server address that was never set. Nothing else matters until this passes.

2) Does it have a GPS fix?

We ask the device for its latest GPS point and confirm it is recent, has real coordinates, and enough satellites. A unit tucked under a metal panel may reach the network yet never see the sky — better discovered now than after a week of "gaps in the track".

3) Is it powered by the vehicle?

We read the external voltage the device measures: 11–15.5 V on 12 V vehicles, 22–30.5 V on 24 V vehicles. A zero means the unit is running on its internal battery and will die within hours.

4) The ignition test — the most important and most skipped step

A simple sequence: vehicle off → key on without starting → engine running for a minute → off. We watch the device see every transition. This exposes the most common OBD-tracker mistake: relying on a factory voltage threshold that does not fit the vehicle, so a modern car reads "always on" or another reads "off" with the engine running. Calibration happens on site, against the vehicle's real resting voltage.

5) Is it talking to the vehicle bus?

For OBD units we confirm the device actually negotiated the vehicle protocol — a non-zero protocol and real parameters (RPM, fuel, odometer). A device that sends position only, with no engine data, is rarely a vehicle fault; it is a negotiation that did not complete and must be retried.

6) Is the VIN the VIN of this vehicle?

We read the VIN from the vehicle bus and match it against the record. The match prevents an expensive mistake: a device registered to one vehicle and installed in another. After the match, the device is locked to that VIN, so any later move is detected automatically.

7) Network signal

Weak signal in the parking spot is not a fault by itself, but it must be recorded: it is what later explains a delayed point. We keep a minimum; below it, we revisit the mounting position.

8) Device settings as we want them — not as they left the factory

Trackers ship with conservative defaults: driving scenarios (harsh acceleration, braking, crash, unplug) are off, and the send interval is long. We push the standard configuration in one command and then read it back from the device — because a device can accept a command silently without applying it.

---

The rule we do not bend

The vehicle does not return to service before the checks pass. Whatever fails is fixed now, on site, not "later" — because in real operations, later means never.

Everything is documented: the device before and after mounting, the odometer, time and location, and the result of every check. If someone asks two months later "was this device installed correctly?", the answer is a record, not a memory.

Asateel — the fleet management platform by Mayader. If you are preparing your fleet for tracking devices, this checklist is where to start.