Keep a reproducible source record
For each investigation, record controller type, hardware evidence, complete software identification, engine specification, transmission, fuel, read tool/version, file size, orientation and hash. Save an untouched original alongside the source definition and its commit.
The GitHub projects provide definitions and research material. An XDF describes binary data; a live-data decoder, flashing application and runtime validation are separate parts of a workflow. Check current primary tool documentation for the exact controller and file format instead of inferring support from a project name.
Build a map record
| Record | What a reviewer needs |
|---|---|
| Identity | Original BMW symbol, editor title, unique item ID and source file/commit. |
| Representation | File-relative offset, width, signedness, conversion, axes and any shared/alternate views. |
| State | The operating conditions the source associates with the item, plus evidence for the state actually observed. |
| Change | Original and proposed values, purpose, byte comparison and affected ranges. |
| Result | Comparable before/after data, faults, learning state and unresolved questions. |
Choose evidence around the question
- Fueling: record relevant load, engine speed, requested and suitably measured lambda, available injection data, per-bank feedback and adaptation state.
- Ignition or camshafts: keep temperature, fuel, command/actual data and intervention evidence with the comparison.
- Throttle or idle: record request, actuator response, speed, accessory load and the relevant operating state.
Request only the signals the selected logger actually exposes. Keep missing channels explicit. Use repeatable conditions and inspect a defined region or event rather than averaging unrelated states together.
Separate file checks from engine checks
Confirm the image basis and required integrity checks before a write. Then keep the write log and validate the intended behaviour separately. A matching checksum establishes an integrity property of the checked data; it does not establish appropriate fuel delivery, timing or hardware configuration.
Use the family-specific file references for MSS52, MSS54 and MSS54HP. Keep any later worked calibration on its ECU/variant page with its exact software and measured result.
Sources and evidence
Original Tuning Wiki reference notes. Definition data and source-code observations are identified as such; they do not establish runtime behaviour or a tested calibration. Validation suggestions and worked arithmetic are editorial guidance. Sources checked 10 November 2026.
MSS52: Ken Malinich (kdm) and the contributors credited by his project; copyright © 2019 Ken Malinich, MIT licence. MSS54/MSS54HP: saildot4k, the OpenSource MSS54 Project and credited contributors. Use the original files and retain their individual credits.
- MSS52 project and software coverage — commit a04c0d24fe63.
- MSS54/MSS54HP project guide — commit dd845dd34225.
- MSS54/MSS54HP partial extraction source — commit dd845dd34225.