FLEET360 · HARDWARE GUIDE

Route360 & Fleet360: OBD-II Hardware Requirements

Mechanical Intel and Forensic Telemetry require a compatible Bluetooth OBD-II adapter for Route360 Pro or Fleet360 Go.

Minimum Technical Specifications

Choose a low-profile adapter with Bluetooth 4.0 BLE or Bluetooth Classic connectivity. It must support the ELM327 v1.5 or v2.1 command set and communicate over ISO 15765-4 CAN, KWP2000, or ISO 9141-2. A slim form factor avoids interference with the driver’s legs in most cabins.

Required: Bluetooth 4.0 or newer · ELM327 compatible command set · modern CAN or KWP protocol support · low-profile housing.

Recommended Hardware

1. Veepeak OBDCheck BLE — Highly recommended for professional fleet use and long-duration driving. This BLE adapter supports Android and iOS, uses very little power, and provides high data throughput.

2. Vgate iCar Pro — Dual Mode Classic + BLE connectivity with automatic sleep mode and reliable Sticky Handshake performance. Best for drivers who leave the dongle plugged in permanently.

3. OBDLink LX / MX+ — High-performance Bluetooth adapters with fast packet-per-second rates and strong security. Best for advanced forensic logging and high-speed telemetry.

Hardware to Avoid

Avoid cheap “ELM327 v2.1” clones. Many generic blue dongles do not support the full command set and may cause the “Pipe Map Failed” error. Wi-Fi OBD adapters are also unsupported because they can interrupt the phone data connection needed for Cloud Sync and Weather.

Where Is My OBD-II Port?

Most vehicles built after 1996 in the USA or 2001 in the EU have an OBD-II port within three feet of the steering wheel. Look directly under the driver-side dashboard, behind a panel near the fuse box, or under the center console by the handbrake.

Technical Note for Managers

Fleet360’s One-Tap Handshake configures the software automatically, but every driver must pair the Bluetooth OBD dongle in their phone’s system settings before the first shift.