Page organisation in this revision
- Page type
- Technical article
- Subject
- Tuning
- Parent
- Siemens MSS52
- Applies to
- Siemens MSS52
- Tool groups
- None
- Manufacturers
- BMW
Changes from revision 1 to revision 1
Removed text is struck through; added text is highlighted.
Ignition-map records
SymbolDimensionsDefinition unitsKF_TZ_GRUND18 RPM columns × 12 relative-filling rows16-bit angle; x/10KF_TZ_VL18 RPM columns × 3 relative-filling rows16-bit angle; x/10
These are properties of the pinned MSS52 XDF. MSS52 XDF.
Cam-target axes differ from the ignition axes
The KF_EVAN1_SOLL intake and KF_AVAN1_SOLL exhaust XY views each use a 16 × 16 grid. Their axes are labelled RPM and % TPS, whereas the ignition tables above use relative filling. MSS52 XDF.
Choose the logged axis quantity that matches the selected definition. A throttle percentage and a filling percentage are different quantities, even when their numeric ranges look similar. Record the channel’s actual meaning before using it to build a histogram.
Angle, overlap and transposed views
The file presents these targets as XY/YX views and alternative percentage displays over the same stored targets. The intake angle view is labelled retard; source comments give different advance/retard conventions for intake and exhaust. MSS52 XDF.
Pick one documented convention for the comparison. Keep axis order, angle reference and units with the result. Changing to a percentage display is an interpretation of the stored value; it does not measure physical valve overlap. A transposed display does not establish another independently selectable ECU target.
Evaluate the commanded and achieved result
Compare target and actual camshaft data, temperature, relevant load and fault state where available. For timing comparisons, keep fuel, temperature and operating state consistent, and retain knock/intervention evidence. An edited target and an achieved physical result are separate observations.
The shared validation guide provides the record to keep with each software-specific example.
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.
MSS52 XDF — commit a04c0d24fe63.
Rendered revisions
Open each version to inspect formatting, tables and photographs.
Revision 1: MSS52 ignition and VANOS
Ignition-map records
| Symbol | Dimensions | Definition units |
|---|
KF_TZ_GRUND | 18 RPM columns × 12 relative-filling rows | 16-bit angle; x/10 |
KF_TZ_VL | 18 RPM columns × 3 relative-filling rows | 16-bit angle; x/10 |
These are properties of the pinned MSS52 XDF. MSS52 XDF.
Cam-target axes differ from the ignition axes
The KF_EVAN1_SOLL intake and KF_AVAN1_SOLL exhaust XY views each use a 16 × 16 grid. Their axes are labelled RPM and % TPS, whereas the ignition tables above use relative filling. MSS52 XDF.
Choose the logged axis quantity that matches the selected definition. A throttle percentage and a filling percentage are different quantities, even when their numeric ranges look similar. Record the channel’s actual meaning before using it to build a histogram.
Angle, overlap and transposed views
The file presents these targets as XY/YX views and alternative percentage displays over the same stored targets. The intake angle view is labelled retard; source comments give different advance/retard conventions for intake and exhaust. MSS52 XDF.
Pick one documented convention for the comparison. Keep axis order, angle reference and units with the result. Changing to a percentage display is an interpretation of the stored value; it does not measure physical valve overlap. A transposed display does not establish another independently selectable ECU target.
Evaluate the commanded and achieved result
Compare target and actual camshaft data, temperature, relevant load and fault state where available. For timing comparisons, keep fuel, temperature and operating state consistent, and retain knock/intervention evidence. An edited target and an achieved physical result are separate observations.
The shared validation guide provides the record to keep with each software-specific example.
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.
Revision 1: MSS52 ignition and VANOS
Ignition-map records
| Symbol | Dimensions | Definition units |
|---|
KF_TZ_GRUND | 18 RPM columns × 12 relative-filling rows | 16-bit angle; x/10 |
KF_TZ_VL | 18 RPM columns × 3 relative-filling rows | 16-bit angle; x/10 |
These are properties of the pinned MSS52 XDF. MSS52 XDF.
Cam-target axes differ from the ignition axes
The KF_EVAN1_SOLL intake and KF_AVAN1_SOLL exhaust XY views each use a 16 × 16 grid. Their axes are labelled RPM and % TPS, whereas the ignition tables above use relative filling. MSS52 XDF.
Choose the logged axis quantity that matches the selected definition. A throttle percentage and a filling percentage are different quantities, even when their numeric ranges look similar. Record the channel’s actual meaning before using it to build a histogram.
Angle, overlap and transposed views
The file presents these targets as XY/YX views and alternative percentage displays over the same stored targets. The intake angle view is labelled retard; source comments give different advance/retard conventions for intake and exhaust. MSS52 XDF.
Pick one documented convention for the comparison. Keep axis order, angle reference and units with the result. Changing to a percentage display is an interpretation of the stored value; it does not measure physical valve overlap. A transposed display does not establish another independently selectable ECU target.
Evaluate the commanded and achieved result
Compare target and actual camshaft data, temperature, relevant load and fault state where available. For timing comparisons, keep fuel, temperature and operating state consistent, and retain knock/intervention evidence. An edited target and an achieved physical result are separate observations.
The shared validation guide provides the record to keep with each software-specific example.
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.