Match the whole logging setup
MS4X’s TunerPro RT guide calls for a matching ECU/logger definition, binary definition and current ECU binary, with a K-line interface or Logger.S. For the high-speed definitions it describes, connect before starting the engine because baud-rate switching is blocked once running. MS4X reference.
Keep a log header containing the ECU/software ID, engine, binary hash, logger definition filename/revision, interface, sampling configuration, fuel and test conditions. This makes the results comparable after a calibration or hardware change. Record actual files; a dashboard or a screenshot cannot be replayed as a time series.
Standard and extended packets
The MS4X logger catalogue separates standard MS43 logging from extended definitions. Extended MS42/MS43 definitions require the corresponding ECU logging feature; the list distinguishes patch generations and engine-specific files. Do not assume that an ADX installs the ECU patch. MS4X reference.
Before interpreting a new packet definition, check plausible RPM and temperatures, both banks where exposed, changing sensor values and state flags. Treat a fixed, implausible or discontinuous channel as a definition/decoding question before treating it as engine behaviour. Keep the raw recording for re-analysis.
Build a baseline around a question
| Question | Suggested evidence |
|---|---|
| Idle and starting | Coolant/intake temperature, battery voltage, RPM, lambda feedback, trims, injection time and idle target/actuator data where available. |
| Fueling under load | Requested and independently measured lambda, engine speed, relevant load, injection time and available fuel-pressure evidence. |
| Camshaft control | Requested/actual cam positions and operating state alongside load and temperature. |
| Throttle response | Pedal, requested/actual throttle, idle-valve command, gear/clutch state and torque intervention channels where exposed. |
Only request signals the selected logger actually provides. Too many channels can reduce useful time resolution. Capture a repeatable baseline, change one explained group of parameters, and compare the same operating region.
Read the relevant load
For MS42/MS43, use the load reference before choosing a map for a histogram. A histogram should use the map’s own axis quantity and units. Mark which channels are measured, calculated or substituted.
MS45 logging needs a tool and packet definition that explicitly supports that controller; this page does not extend the cited MS41/MS42/MS43 setup to MS45.
Sources and scope
Original reference notes by Tuning Wiki, informed by the linked MS4X Wiki pages. MS4X Wiki contributors and the authors credited by each linked project remain the source authors. Sources checked 10 November 2026. Suggested validation steps and worked arithmetic are editorial guidance; they are not a tested calibration or a claim of hardware verification.
- TunerPro Data Logging (revision 22449).
- Logger Definition Files (revision 22476).