A datalog records ECU parameters over time. It can show whether requested and actual values agree and whether a protection or limitation becomes active. It is a diagnostic and validation tool, not an automatic verdict on calibration quality.
Choosing useful channels
The relevant channels depend on the engine and question. Boost, airflow, fuel pressure, lambda, ignition correction, injection quantity, temperatures, torque requests and throttle position may all matter. Recording everything at once can reduce clarity or sampling speed.
Conditions must be known
Gear, engine speed, ambient temperature, fuel, road gradient and starting temperatures affect the result. Comparing two logs only makes sense when their conditions are understood.
What Swaptune looks for
When a partner reports a concern, we first define the symptom and request the measurements needed to investigate it. We compare target and actual behaviour, look for limits or corrections and relate the data to the vehicle’s mechanical configuration.
A log cannot repair a boost leak, weak pump or ignition fault, but it can help direct the diagnosis.
FAQ
Can a datalog measure horsepower?
Not directly. It records operating parameters; a controlled dyno measures output.
Is one short log enough?
Sometimes, but repeatable conditions and additional checks may be needed.
Does a clean log guarantee reliability?
No. It is evidence from a particular test, not a prediction of every future use.