What is OBD-II?
On-Board Diagnostics II
Definition
OBD-II is a standardised vehicle self-diagnostics port that exposes engine and system data, RPM, coolant temperature, fault codes, and more. Plug-and-play OBD devices read this data for tracking and diagnostics without hard-wiring.
Why it matters for Indian fleets
OBD data turns a vehicle’s own sensors into a predictive-maintenance feed, letting fleets catch engine faults before they cause a roadside breakdown.
What the OBD-II port is and where to find it
OBD-II is a standardised diagnostic interface that vehicles expose through a 16-pin trapezoidal connector, normally within reach of the driver’s seat, under the dashboard near the steering column. Because the connector and the core request format are standardised, one device can read basic data from a very wide range of vehicles without any vehicle-specific wiring.
The port was designed for emissions diagnostics in a workshop. Fleet telematics repurposes it: instead of a mechanic plugging in once, a small always-connected device polls the same data continuously and forwards it to a platform.
That is why an OBD tracker installs in about a minute and a hard-wired tracker takes an auto-electrician. It is also why an OBD device can be unplugged in about a minute, which is a genuine trade-off rather than a detail.
What data actually comes out of it
The standard exposes parameters through numbered PIDs, and the useful ones for a fleet are engine and driveline signals rather than emissions internals.
- Engine RPM and vehicle speed, which together reveal over-revving, wrong-gear driving and prolonged idling.
- Coolant temperature, an early warning of a cooling-system problem before it becomes a roadside failure.
- Fuel system and throttle data, which supports consumption and efficiency analysis.
- Diagnostic trouble codes, the fault codes the vehicle raises itself.
- Malfunction indicator status, meaning whether the dashboard warning light is actually on.
Coverage varies. Every compliant vehicle supports the emissions-related PIDs, but manufacturers expose extended parameters through their own codes, so depth of data differs between makes.
OBD tracking versus hard-wired tracking
These solve different problems and the choice is usually decided by vehicle type and compliance need rather than preference.
- OBD devices install without tools, move between vehicles easily, and add engine data that a GPS-only tracker cannot see. They suit cars, light commercial vehicles, leased fleets and pilot deployments.
- Hard-wired devices are concealed, cannot be casually unplugged, and can be tied into ignition, panic buttons and immobiliser relays. They suit trucks, buses and any vehicle where tamper resistance matters.
- For AIS-140 compliance, the requirement is a certified VLTD with a panic button and backup battery. A generic OBD dongle does not satisfy that, whatever data it reports.
Many fleets run both: certified hardware for the regulated vehicles, OBD devices where the value is diagnostics rather than compliance.
Frequently asked questions
Where is the OBD-II port located?
In most vehicles it is under the dashboard on the driver’s side, near the steering column, within about half a metre of the steering wheel. It is a 16-pin trapezoidal socket, sometimes behind a small removable cover.
Does an OBD tracker drain the vehicle battery?
The port stays powered when the ignition is off, so an OBD device does draw current continuously. A well-designed fleet device manages this with a low-power sleep mode. The risk is real for a vehicle parked unused for weeks, and negligible for a vehicle in regular service.
Can an OBD tracker be used for AIS-140 compliance?
No. AIS-140 requires a certified Vehicle Location Tracking Device with an emergency panic button, backup battery and a connection to the state backend control centre. A generic OBD dongle does not meet the specification regardless of how accurate its tracking is.
Will an OBD device work on any vehicle?
The connector and the emissions-related parameters are standardised, so basic data reads across a wide range of vehicles. Extended parameters are manufacturer-specific, so the depth of engine data varies by make and model. Older commercial vehicles may not expose a usable OBD-II port at all.
Related MoboSafe workflows
Review the documented product scope and setup requirements for these related operational tasks.
Vehicle Inspections
Digital pre-trip, post-trip, and periodic vehicle inspections with configurable checklists, defect photos, and inspection history.
Fleet Asset Management
Manage fleet vehicles, trailers, equipment, ownership, insurance documents, device assignments, and utilisation in MoboSafe.
Fleet Inventory & Stores
Manage fleet inventory, depot stores, material requests, stock transfers, supplier records, goods receipts, and stock valuation.
Related terms
Begin
Ready to connect your whole operation?
Explore tracking, trips, assets, fuel, inventory, accounting, and payroll with the MoboSafe team. Build a rollout around the workflows your fleet needs.