BlueDriver OBD-II logs

• File type: CSV log exports from the BlueDriver Bluetooth OBD-II scan tool app
• Supported devices: Any vehicle with an OBD-II port, scanned through a BlueDriver Bluetooth adapter
• Features: Automatic channel/unit extraction from parenthesized header units, UTF-16 file handling

Supported File Format

BlueDriver exports a UTF-16-encoded CSV (with a byte-order mark) containing a title line, a date line, then a header row and comma-separated data. Time is in decimal seconds:

BlueDriver Data Log
Jan 16, 2026
Time(s), Engine RPM (rpm), Voltage (V)
0.00, 850, 14.2
0.50, 900, 14.1
1.00, 950, 14.0

How to Export from BlueDriver

1. Open the logged session in the BlueDriver app
2. Use the app's export/share option to save the session as CSV
3. Load the resulting .csv file directly into UltraLog

Supported Data

• Every OBD-II PID logged by the session: RPM, vehicle speed, coolant temperature, MAF
• Fuel trims (short-term/long-term)
• O2 sensor readings and voltages (e.g. "O2 Bank 1 - Sensor 2 - Oxygen Sensor Voltage")
• Any additional PID selected in the BlueDriver live-data view

Character Encoding

BlueDriver writes its CSV as UTF-16 with a byte-order mark, unlike nearly every other supported format, which is UTF-8. UltraLog detects and decodes this automatically — no manual conversion needed before loading the file.

Missing Data

Empty or unparseable cells are recorded as NaN rather than filled from the previous value, so a PID the scan tool briefly failed to read shows as a genuine gap instead of a flat line.