Skip to content
TuneView

Required Log Channels & Table Paste Guide

Log the right channels.
Get the right answers.

TuneView grades only what your log can prove. This page lists exactly which VCM Scanner channels the analysis looks for, what happens when one is missing, and how to send your VVE and MAF tables so revisions can be computed against your actual calibration — not a guess at it.

01

Required — the log is rejected without these

Three channels are non-negotiable. If any of them is missing from the CSV export, the parser stops before analysis begins.

Engine RPM (SAE)Every module keys off RPM. Without it the log cannot be analyzed at all.
Throttle Position (SAE)Separates idle, cruise, and WOT so findings land in the right operating zone.
Knock RetardThe single most important safety channel. No knock channel, no safety verdict.
02

Core — needed for a complete grade

The log parses without these, but modules that depend on a missing channel report reduced confidence or are skipped outright — they are never faked from a proxy. A healthy log maps at least 8 recognized channels.

Manifold Absolute Pressure (MAP)The only signal TuneView accepts for boost detection. No MAP, no boost analysis — we never guess from throttle or RPM.
MAF Airflow (g/s) + MAF Frequency (Hz)Airflow model health, MAF vs VE agreement, and MAF curve corrections.
Fuel Rail Pressure — Commanded AND ActualBoth are needed as a pair. Commanded-vs-actual delta is how fuel-system health is graded.
Spark / Timing AdvanceWhere your timing actually lands, cell by cell, against knock activity.
Accelerator Pedal PositionDriver-demand context — distinguishes pedal-limited pulls from tune-limited ones.
TimeVCM Scanner includes it by default. Event ordering and duration math depend on it.
04

Send your VVE table — Copy with Axis

A datalog shows the symptoms; your VVE table is the calibration producing them. With both, revision steps can point at the exact cells that need to move instead of describing regions.

  1. 1.In VCM Editor, open your tune and navigate to Engine → Airflow → Virtual VE (the VVE virtual table view).
  2. 2.Click into the table so it has focus, then right-click anywhere in the cells.
  3. 3.Choose Copy with Axis — not plain Copy. Plain Copy drops the RPM and MAP breakpoints and the paste will be rejected.
  4. 4.In TuneView, open your vehicle's follow-up upload page, select VVE TABLE in the Tune Table Paste box, and paste.
  5. 5.Submit. TuneView echoes back what it parsed — e.g. 31 RPM × 73 MAP cells, 0.10–2.98 bar — so you can confirm the grid matches your editor before it's attached to your case.
400     600     800     ...     6400    rpm
0.10    990.63  982.07  ...     831.09
0.14    1092.31 1082.64 ...     967.20
...

What a valid paste looks like: RPM breakpoints across the top, MAP (bar or kPa — auto-detected) down the side. Transposed copies are detected and flipped automatically.

05

Send your MAF calibration — Copy with Axis

Same idea, one dimension: the airflow-vs-frequency curve your MAF corrections will be computed against.

  1. 1.In VCM Editor, navigate to Engine → Airflow → your MAF calibration curve (airflow vs frequency).
  2. 2.Right-click the table and choose Copy with Axis.
  3. 3.In TuneView, select MAF CURVE in the Tune Table Paste box and paste. Both layouts work — breakpoints across the top or down the side.
  4. 4.Submit and confirm the echoed breakpoint count and frequency range match your editor.

Questions? [email protected]