A useful datalog records what the ECU saw and commanded at the time of a symptom. It is a diagnostic aid, not proof that an input, output or engine is healthy. Field names, sample rates and available channels depend on firmware and software.
Capture a useful log
- Identify the ECU model, board, firmware and software project. Save the current tune separately and note any change made before the test.
- Record battery voltage, engine speed, synchronisation status or loss counter if available, MAP, throttle position, coolant and intake temperatures, measured lambda, target lambda, injector pulse width and commanded ignition timing. Add fuel pressure, knock or other channels if correctly instrumented.
- Capture the event and the seconds before and after it. Note whether the engine was cold, idling, accelerating or under load, and record the test conditions and time.
- Compare one change at a time against a known baseline. Stop testing if there are signs of an unsafe condition.
Patterns to investigate
- No start and zero RPM: check ECU power, sensor and trigger wiring, then inspect a trigger log using the correct decoder and sensor conditioning.
- RPM drops or sync losses: compare the sync-loss counters or trigger log with the symptom; investigate noise, sensor gap, grounding and configuration.
- Unexpected sensor readings: compare readings with an independent measurement and check calibration, sensor supply and ground before changing tables.
- Lean or rich under steady conditions: verify the wideband/controller, fuel pressure, injector data and target, then review VE and corrections; a misfire or exhaust leak can mislead lambda readings.
- Brief hesitation on throttle movement: compare throttle rate and measured lambda with the transient; review acceleration enrichment only after the base fuel table is sound.
Software
TunerStudio can display ECU data and record logs; MegaLogViewer can inspect recorded logs and, where supported, analyse VE. Features and file compatibility vary by edition and ECU definition. Match the TunerStudio project to the installed firmware and consult the software documentation before applying any suggested table changes.