[{"data":1,"prerenderedAt":8},["ShallowReactive",2],{"ecu:racechrono":3},{"slug":4,"wikiHtml":5,"adapter":6,"channels":7},"racechrono","\u003Cul>\n\u003Cli>\u003Cstrong>File type:\u003C\u002Fstrong> CSV v3 session exports from the RaceChrono \u002F RaceChrono Pro lap-timing app (Android\u002FiOS)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Supported devices:\u003C\u002Fstrong> Any session recorded in RaceChrono — phone GPS or external GPS receivers, phone accelerometer\u002Fgyroscope\u002Fmagnetometer, and OBD-II \u002F CAN-Bus channels from a connected adapter\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Features:\u003C\u002Fstrong> All sources merged on one time axis, duplicate channel names disambiguated by source, multi-fragment (paused and resumed) sessions, GPS Track Map support out of the box\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Supported File Format\u003C\u002Fh2>\n\u003Cp>RaceChrono CSV v3 files start with a banner and a metadata preamble, followed by a header row, a units row, and a sources row:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">This file is created using RaceChrono Pro v10.1.3 ( http:\u002F\u002Fracechrono.com\u002F ).\nFormat,3\nSession title,"My Track Session"\nSession type,Lap timing\n...\n\ntimestamp,fragment_id,lap_number,elapsed_time,...,latitude,longitude,...,speed,...,rpm\nunix time,,,s,...,deg,deg,...,m\u002Fs,...,rpm\n,,,,...,100: gps,100: gps,...,calc,...,300: canbus\n1785849363.002,0,,0.002,...,44.831825,11.224415,...,0.0,...,850.0\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2>How to Export from RaceChrono\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Open the session in RaceChrono\u003C\u002Fli>\n\u003Cli>Tap the share\u002Fexport button and choose \u003Cstrong>CSV v3\u003C\u002Fstrong> as the export format\u003C\u002Fli>\n\u003Cli>Load the resulting \u003Ccode>.csv\u003C\u002Fcode> file directly into UltraLog\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Only CSV v3 is supported. The other RaceChrono export formats (\u003Ccode>.vbo\u003C\u002Fcode>, \u003Ccode>.rcz\u003C\u002Fcode>, CSV v1\u002Fv2) will not load — UltraLog shows a clear error asking for a CSV v3 re-export if it sees an older CSV version.\u003C\u002Fp>\n\u003Ch2>Supported Data\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>GPS: latitude, longitude, altitude, speed, bearing, accuracy, satellites, fix type\u003C\u002Fli>\n\u003Cli>Phone sensors: accelerometer (x\u002Fy\u002Fz), gyroscope, magnetometer, and derived lateral\u002Flongitudinal\u002Fcombined acceleration and lean angle\u003C\u002Fli>\n\u003Cli>Lap timing: lap number, fragment id, distance traveled\u003C\u002Fli>\n\u003Cli>OBD-II \u002F CAN: every channel the session logged (RPM, engine oil temp, throttle, and more)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Channel Naming\u003C\u002Fh2>\n\u003Cp>RaceChrono exports the same column name once per source (for example \u003Ccode>speed\u003C\u002Fcode> from GPS and from the calculated pipeline). UltraLog disambiguates duplicates with the source label — \u003Ccode>speed (gps)\u003C\u002Fcode>, \u003Ccode>speed (calc)\u003C\u002Fcode>, \u003Ccode>device_update_rate (acc)\u003C\u002Fcode> — while unique names such as \u003Ccode>latitude\u003C\u002Fcode>, \u003Ccode>longitude\u003C\u002Fcode>, and \u003Ccode>rpm\u003C\u002Fcode> are kept exactly as exported.\u003C\u002Fp>\n\u003Ch2>Timestamp Handling\u003C\u002Fh2>\n\u003Cp>The \u003Ccode>timestamp\u003C\u002Fcode> column is unix time. UltraLog re-bases it so the first record is \u003Ccode>t = 0\u003C\u002Fcode>. The \u003Ccode>elapsed_time\u003C\u002Fcode> column resets to zero at every fragment boundary (each time the recording was paused and resumed), so it is kept as a regular channel rather than used as the time axis.\u003C\u002Fp>\n\u003Ch2>GPS Track Map\u003C\u002Fh2>\n\u003Cp>Because latitude\u002Flongitude arrive in decimal degrees under their standard names, the GPS Track Map works immediately: lap detection, channel-colored track polyline, and cursor sync.\u003C\u002Fp>\n",null,[],1792894560299]