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.
Three displays, one stored throttle table
The MSS52 XDF presents normal, 120% and 154% views of KF_EGAS_WDK. All three use the same stored table at file-relative 0x6392, with 23 rows and 14 columns. MSS52 XDF.
View labelValue equationNormalx/10120%x/12154%x/15.4
The source labels the axes RPM and relative filling. Record which display you use. Editing a value through another view writes to the same underlying range, so compare raw bytes and avoid treating these as separate selectable driving modes.
Request and torque entry points
AreaSource symbolsPedal/request curvesKL_PWG_SOLL_COMFORT, KL_PWG_SOLL_SPORT, KL_PWG_SOLL_EMERGENCYTorque modelKF_MD_MAX_MD_IND_OPT, KF_MD_POLYNOM_ATorque shapingKF_MD_DASHPOT_FAKTOR, KL_MD_BEGR_GANGIdle targetKL_LFR_NSOLL_GRUND, KL_LFR_NSOLL_OFFSET, KL_LFR_NSOLL_START
These names locate items in the definition. The base idle curve is described as coolant temperature versus target RPM. MSS52 XDF.
Trace the request and response
For a response complaint, compare driver input, processed request, command, actuator response and resulting engine behaviour. Keep gear, temperature and intervention state with the event. Identify which stage differs from the intended result before choosing a calibration change.
For idle, build a cold/hot and accessory-load comparison and include target/actual speed with available actuator data. For torque shaping, compare repeatable tip-in, lift-off and shift events. Preserve the original maps and explain the intended effect of each change.
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 driver demand and torque
Three displays, one stored throttle table
The MSS52 XDF presents normal, 120% and 154% views of KF_EGAS_WDK. All three use the same stored table at file-relative 0x6392, with 23 rows and 14 columns. MSS52 XDF.
| View label | Value equation |
|---|
| Normal | x/10 |
| 120% | x/12 |
| 154% | x/15.4 |
The source labels the axes RPM and relative filling. Record which display you use. Editing a value through another view writes to the same underlying range, so compare raw bytes and avoid treating these as separate selectable driving modes.
Request and torque entry points
| Area | Source symbols |
|---|
| Pedal/request curves | KL_PWG_SOLL_COMFORT, KL_PWG_SOLL_SPORT, KL_PWG_SOLL_EMERGENCY |
| Torque model | KF_MD_MAX_MD_IND_OPT, KF_MD_POLYNOM_A |
| Torque shaping | KF_MD_DASHPOT_FAKTOR, KL_MD_BEGR_GANG |
| Idle target | KL_LFR_NSOLL_GRUND, KL_LFR_NSOLL_OFFSET, KL_LFR_NSOLL_START |
These names locate items in the definition. The base idle curve is described as coolant temperature versus target RPM. MSS52 XDF.
Trace the request and response
For a response complaint, compare driver input, processed request, command, actuator response and resulting engine behaviour. Keep gear, temperature and intervention state with the event. Identify which stage differs from the intended result before choosing a calibration change.
For idle, build a cold/hot and accessory-load comparison and include target/actual speed with available actuator data. For torque shaping, compare repeatable tip-in, lift-off and shift events. Preserve the original maps and explain the intended effect of each change.
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 driver demand and torque
Three displays, one stored throttle table
The MSS52 XDF presents normal, 120% and 154% views of KF_EGAS_WDK. All three use the same stored table at file-relative 0x6392, with 23 rows and 14 columns. MSS52 XDF.
| View label | Value equation |
|---|
| Normal | x/10 |
| 120% | x/12 |
| 154% | x/15.4 |
The source labels the axes RPM and relative filling. Record which display you use. Editing a value through another view writes to the same underlying range, so compare raw bytes and avoid treating these as separate selectable driving modes.
Request and torque entry points
| Area | Source symbols |
|---|
| Pedal/request curves | KL_PWG_SOLL_COMFORT, KL_PWG_SOLL_SPORT, KL_PWG_SOLL_EMERGENCY |
| Torque model | KF_MD_MAX_MD_IND_OPT, KF_MD_POLYNOM_A |
| Torque shaping | KF_MD_DASHPOT_FAKTOR, KL_MD_BEGR_GANG |
| Idle target | KL_LFR_NSOLL_GRUND, KL_LFR_NSOLL_OFFSET, KL_LFR_NSOLL_START |
These names locate items in the definition. The base idle curve is described as coolant temperature versus target RPM. MSS52 XDF.
Trace the request and response
For a response complaint, compare driver input, processed request, command, actuator response and resulting engine behaviour. Keep gear, temperature and intervention state with the event. Identify which stage differs from the intended result before choosing a calibration change.
For idle, build a cold/hot and accessory-load comparison and include target/actual speed with available actuator data. For torque shaping, compare repeatable tip-in, lift-off and shift events. Preserve the original maps and explain the intended effect of each change.
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.