Supported cars
FuGPS works with most petrol and diesel cars that have a standard OBD-II port. What matters is that the car reports its speed over OBD-II.
Requirements
A 16-pin socket, usually under the dashboard near the driver's knees.
Standard PID 0D (vehicle speed) is required. Engine RPM (PID 0C) is used if available.
An ELM327-compatible adapter with Bluetooth Low Energy. Classic Bluetooth and Wi-Fi adapters are not supported.
Which cars usually qualify
| Car | Status |
|---|---|
| Petrol, 2001 or newer (EU) / 1996 or newer (US) | Supported |
| Diesel, 2004 or newer (EU) | Supported |
| CAN bus cars, roughly 2008 and newer | Best results: fast, frequent speed readings |
| Older non-CAN cars (K-Line, J1850) | Works, but slower readings lower accuracy |
| Hybrids | Usually supported |
| Fully electric cars | Often not supported — many EVs do not report standard OBD-II speed |
| Cars without a standard OBD-II port | Not supported |
Model years are a guide: OBD-II became mandatory at different times in different markets, and imported cars follow the rules of the market they were built for. Security gateways on newer cars normally do not block the read-only data FuGPS uses.
Supported OBD‑II protocols
The adapter detects the protocol automatically: ISO 15765-4 CAN (11- and 29-bit, 250 and 500 kbit/s), ISO 14230-4 KWP2000, ISO 9141-2, SAE J1850 PWM and VPW.
Tested
| Car | Adapter | Result |
|---|---|---|
| Volkswagen Touareg (2025) | Vgate iCar Pro Bluetooth 4.0 (BLE) | CAN 11-bit 500 kbit/s · speed and RPM ≈ 16 readings/s · ≈ 60 ms latency |
Tried FuGPS with another car or adapter? Tell us the make, model, year and adapter, and we will add it here.
Safe for your car
FuGPS only reads data. Every request goes through a fixed allowlist of read-only OBD-II commands, so the app cannot clear fault codes, change settings or write anything to the car.