The device decision looks technical and is mostly operational. It determines how much data you get, how easily a device can be removed, what installation costs, and how much work is involved every time a vehicle joins or leaves the fleet.
The options compared
| Factor | OBD plug-in | Hardwired |
|---|---|---|
| Installation | Seconds, self-service | 30–90 minutes, technician |
| Installation cost | Effectively zero | Per-vehicle labour charge |
| Tamper resistance | Low — unplugs by hand | High — concealed, alarms on disconnect |
| Data depth | Good on many light vehicles, variable | Better, especially with bus access |
| Vehicle compatibility | Light vehicles with OBD-II | Almost anything, including plant |
| Redeployment | Trivial | Requires removal and reinstallation |
| Physical intrusion | None | Wiring into the vehicle |
| Lease and warranty concerns | Occasionally raised | Sometimes requires approval |
| Ignition detection | Via voltage or port data | Direct, more reliable |
| Suitability for heavy vehicles | Poor | Standard |
Ask yourself what happens the first time a device is found unplugged. If the answer is "a conversation", plug-in is fine.
When plug-in is right
- Light commercial and car fleets with standard OBD-II ports.
- Short-term or seasonal vehicles, including hire and grey fleet.
- Rapid deployment where you want data next week, not next quarter.
- Leased vehicles where the lessor restricts modifications.
- Pilots and trials before committing to a vendor.
- Fleets with high vehicle churn, where installation and removal cost would dominate.
The redeployment advantage is genuinely large. If you replace 30% of your vehicles a year, hardwired installation and removal costs recur constantly, while a plug-in device moves with a click.
When hardwired is right
- Heavy vehicles requiring J1939 or J1708 bus access.
- Where tamper resistance matters — high-value cargo, driver behaviour programmes, hours recording, insurance requirements.
- Plant, trailers and specialist equipment with no OBD port.
- Where additional inputs are needed — door sensors, temperature probes, PTO, tail lift, panic buttons.
- Long-term owned vehicles where installation cost amortises over years.
- Poor port reliability on specific models where plug-in devices are known to disconnect.
Data depth reality
OBD-II gives access to standardised diagnostic parameters, but manufacturers expose different amounts of data, and much of the useful information sits in proprietary messages. In practice:
- Position, speed and trip data: reliable on both.
- Odometer: usually available on both, occasionally derived rather than read.
- Fuel level and consumption: variable on OBD, better on hardwired bus connections.
- Engine hours: often available, model-dependent.
- Fault codes: standardised emissions codes on OBD; manufacturer-specific codes usually need deeper access.
- Seat belt, doors, PTO: generally requires hardwired inputs or CAN access.
Always request a per-model coverage statement for your actual fleet. General claims are not useful.
Practical issues that catch people out
Battery drain. Devices draw power when the vehicle is off. Modern units use deep sleep, but vehicles that sit for weeks — seasonal, spare, or awaiting repair — can be found flat. Ask about sleep current and whether the device disconnects below a voltage threshold.
Port obstruction. In some vehicles the OBD port is where the driver's knee goes. Right-angle adapters solve it; discovering it after fleet-wide deployment does not.
Vehicle electrical systems. Poorly installed hardwired devices cause faults that are expensive to diagnose. Use the vendor's approved installers, insist on fused connections, and document the installation.
Warranty and lease terms. Some manufacturers and lessors have views on both port devices and wiring. Confirm before, not after.
Removal at disposal. Budget for de-installation and for the residual value impact of visible wiring. It is a real cost that is routinely omitted from comparisons.
Mixed fleets. Running both device types across a fleet is normal and manageable, provided the platform presents them consistently. Confirm reporting is uniform across device types.
Cost over three years
Compare like for like:
`` Plug-in: device + subscription × 36 + redeployment effort Hardwired: device + installation + subscription × 36 + removal at disposal ``
At typical installation costs, hardwired is more expensive over a three-year term for a vehicle that is replaced at the end of it, and can be cheaper for a vehicle kept seven years. The tamper-resistance and data-depth benefits then decide the rest.
Questions readers send us
Can plug-in devices be used on trucks? Heavy vehicles generally use J1939 rather than OBD-II, so a standard plug-in car device will not work. Some vendors offer plug-in adapters for heavy-vehicle diagnostic ports, but hardwired remains standard for trucks.
Do trackers drain the vehicle battery? Modern devices draw very little in sleep mode, and the risk is real only for vehicles left unused for extended periods. Ask for the quiescent current figure and whether there is a low-voltage cut-off, particularly if you have seasonal or spare vehicles.
Will a hardwired installation void the vehicle warranty? A correctly installed, fused device generally does not, but manufacturer positions vary and lease agreements may restrict modifications. Get written confirmation for your specific vehicles and lessor before fleet-wide installation.
What about self-powered battery trackers? They suit trailers, containers and plant with no power source. Reporting frequency is traded against battery life — daily positions for years, or frequent positions for months. See asset tracking.
Can we mix device types in one fleet? Yes, and most fleets do. The requirement is that your platform normalises the data so reports are comparable, and that you know which parameters are unavailable on which devices when interpreting the results.
