[{"data":1,"prerenderedAt":8},["ShallowReactive",2],{"ecu:bluedriver":3},{"slug":4,"wikiHtml":5,"adapter":6,"channels":7},"bluedriver","\u003Cul>\n\u003Cli>\u003Cstrong>File type:\u003C\u002Fstrong> CSV log exports from the BlueDriver Bluetooth OBD-II scan tool app\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Supported devices:\u003C\u002Fstrong> Any vehicle with an OBD-II port, scanned through a BlueDriver Bluetooth adapter\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Features:\u003C\u002Fstrong> Automatic channel\u002Funit extraction from parenthesized header units, UTF-16 file handling\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Supported File Format\u003C\u002Fh2>\n\u003Cp>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:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">BlueDriver Data Log\nJan 16, 2026\nTime(s), Engine RPM (rpm), Voltage (V)\n0.00, 850, 14.2\n0.50, 900, 14.1\n1.00, 950, 14.0\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2>How to Export from BlueDriver\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Open the logged session in the BlueDriver app\u003C\u002Fli>\n\u003Cli>Use the app's export\u002Fshare option to save the session as CSV\u003C\u002Fli>\n\u003Cli>Load the resulting \u003Ccode>.csv\u003C\u002Fcode> file directly into UltraLog\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Supported Data\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Every OBD-II PID logged by the session: RPM, vehicle speed, coolant temperature, MAF\u003C\u002Fli>\n\u003Cli>Fuel trims (short-term\u002Flong-term)\u003C\u002Fli>\n\u003Cli>O2 sensor readings and voltages (e.g. "O2 Bank 1 - Sensor 2 - Oxygen Sensor Voltage")\u003C\u002Fli>\n\u003Cli>Any additional PID selected in the BlueDriver live-data view\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Character Encoding\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2>Missing Data\u003C\u002Fh2>\n\u003Cp>Empty or unparseable cells are recorded as \u003Ccode>NaN\u003C\u002Fcode> 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.\u003C\u002Fp>\n",null,[],1792894560341]