Importing logs

Logs come in as CSV or TSV files, and a three-step wizard turns one into channels the log analyzer can plot. Start it from the analyzer.

Figure 1

Step 1 — file & format

The first page shows a raw preview of the file’s opening lines, so you can see exactly how it is laid out, alongside the controls to read it correctly:

• Separator — Tab, Comma, Semicolon or a Custom character.
• Decimal — point (1.234) or comma (1,234), so logs that use a decimal comma are read correctly.
• Header row, Units row and First data row — tell the wizard which line holds the channel names, which (if any) holds the units, and where the numbers begin, so preamble lines and a units row are skipped cleanly.

A live parsed preview updates as you change these, showing the first rows the way they will actually be read — and the detected column list confirms the file split into the channels you expect.

Step 2 — the channels

The detected channels are listed for you to curate. Each has an include checkbox (with Select all / Select none), its original name plus a field to rename it to something friendlier, and an X axis radio button — you mark exactly one channel as the X axis, normally the time column. The Common 4 button is a shortcut that includes just RPM, MAP, TPS and AFR. You need at least two channels (one X and one Y), and the channel you mark as X must be among those included.

Step 3 — save a preset

Optionally save the whole configuration as a named preset: tick Save as preset, give it a name (the page lists your existing presets and shows where it will be saved), and use Open Log Presets folder if you want to manage them on disk. The wizard recognises a log by its first columns, so the next time you open one from the same device it auto-matches that preset and re-applies your separator, channel names, renames and X-axis choice — re-saving then updates the same preset rather than making a new one.

Tip — set up one preset per logger or export format. After that, importing is essentially one click, and every log lines up the same way for comparison.

See also

• The log analyzer
• Replaying logs over your maps