Page organisation in this revision
- Page type
- Technical article
- Subject
- Tuning
- Parent
- Simos 18
- Applies to
- Simos 18.1
- Tool groups
- None
- Manufacturers
- Volkswagen Group
Changes from revision 1 to revision 1
Removed text is struck through; added text is highlighted.
Scope. Engine drag-torque control, commonly called MSR, addresses driven-wheel slip during deceleration. It is distinct from acceleration traction control (ASR), normal trailing-throttle fuel cut, and a gearbox shift request, although these systems can interact. The software examples below are from the community SC8S5031_C_OEM Simos 18.1 reference; verify the exact ECU, engine, transmission, ABS/ESC equipment, ASW/CAL, configuration, units and logger support.
What happens on lift-off
Volkswagen SSP 374 describes an engine-braking control example in which the ABS/traction controller uses wheel-speed and engine information to detect driven-wheel slip after torque reduction. It requests a change through the engine controller; the illustrated system can briefly open the throttle to reduce the braking effect. This is an explanation of a documented Volkswagen control concept, not proof that every Simos 18 vehicle has exactly the same algorithm, message or actuator response.
In the SC8S5031 VHST deceleration-slip reference, a valid external traction-control request, MSR enable and absence of the relevant disable condition permit a torque request to enter fast and slow coordination paths. A torque request or an enable flag is not a direct measurement of wheel grip or delivered torque. The reference calls the requesting traction-control unit “TCU”; in this context do not confuse that abbreviation with the transmission control unit.
Normal deceleration fuel cut can stop injection during a qualifying overrun, but a lift-off event can also include clutch disengagement, a gearbox change, idle intervention or stability control. Seeing closed pedal or a lean exhaust reading does not establish which function caused a change in vehicle deceleration.
Example calibration fields
In the VHST reference these are scalar calibrations, not driver-adjustable wheel-slip maps. They are research leads, not recommended settings:
c_vs_min_msr is labelled a minimum vehicle-speed condition in km/h for the described MSR path. Other request, error and enable conditions apply; the value shown in an extracted description is not a universal operating threshold.
c_t_dly_diag_msr is a delay for the described emergency ramp, in seconds. c_lgrd_tqi_inc_diag_msr is its torque-change limit in Nm per 10 ms. The reference describes ramping after an enable change while active; verify signs, conditions and time base before interpreting a logger.
c_tq_msr_int_dec is labelled a decrement for the MSR torque integrator. c_tq_msr_int_max is a plausibility threshold in N·m·s. These do not set a traction target or tyre grip.
The separate ECM2 monitoring reference lists c_vs_min_msr_intv_mon, c_t_dly_msr_deac_mon and c_t_dly_msr_inh_mon as monitoring-level speed or delay conditions. They are distinct from the VHST function-level values. Do not alter plausibility monitoring to conceal communication, sensor or vehicle faults.
Signals for diagnosis
lv_msr_ena is the VHST enable condition; lv_msr_emergency denotes the reference's emergency state. tqi_msr_fast and tqi_msr_slow are fast and slow requested intervention values in Nm, not measured torque. tq_msr_int is a torque-by-time accumulator in N·m·s. VHST source.
lv_msr_tq_act is labelled MSR responsible for an increased torque request in the PTQM reference. It is a state indication, not a slip measurement.
lv_msr_req_mon, lv_msr_act_mon and lv_msr_not_plaus_mon describe monitored request, active and communication-plausibility states in the ECM2 reference. Their names or status encodings may differ in diagnostic tools; do not assume a zero or unavailable channel proves that the vehicle lacks the feature.
When investigating an unexpected lift-off or downshift response, record full engine, ABS/ESC and gearbox faults; tyre sizes and pressures; road and weather conditions; pedal and brake state; gear/clutch state; individual wheel speeds; requested and estimated engine torque; throttle; fuel-cut state; and available MSR/ASR request, active and fault signals. Synchronise the logs and check each signal's scaling and sample rate. A small brief difference between requested and actual torque does not by itself prove an MSR intervention or a fault. Do not deliberately create wheel slip on public roads.
Aftermarket feature scope
The simos.app Main Patch guide says its product-specific OEM ASR Sport mode ignores ESP requests for engine-torque cuts but leaves MSR and the described ESP stability/brake interventions active. This is the publisher's description of that patch, not a statement about every tune or a guarantee of all vehicle functions. Confirm installed patch, version, settings and hardware. For COBB custom slip-target and shift-freeze tables, see traction control tuning.
Related: deceleration fuel cut · DSG torque coordination · torque monitoring and plausibility · traction control tuning. References reviewed 17 November 2026.
Rendered revisions
Open each version to inspect formatting, tables and photographs.
Revision 1: Simos 18 engine drag torque and MSR control
Scope. Engine drag-torque control, commonly called MSR, addresses driven-wheel slip during deceleration. It is distinct from acceleration traction control (ASR), normal trailing-throttle fuel cut, and a gearbox shift request, although these systems can interact. The software examples below are from the community SC8S5031_C_OEM Simos 18.1 reference; verify the exact ECU, engine, transmission, ABS/ESC equipment, ASW/CAL, configuration, units and logger support.
What happens on lift-off
Volkswagen SSP 374 describes an engine-braking control example in which the ABS/traction controller uses wheel-speed and engine information to detect driven-wheel slip after torque reduction. It requests a change through the engine controller; the illustrated system can briefly open the throttle to reduce the braking effect. This is an explanation of a documented Volkswagen control concept, not proof that every Simos 18 vehicle has exactly the same algorithm, message or actuator response.
In the SC8S5031 VHST deceleration-slip reference, a valid external traction-control request, MSR enable and absence of the relevant disable condition permit a torque request to enter fast and slow coordination paths. A torque request or an enable flag is not a direct measurement of wheel grip or delivered torque. The reference calls the requesting traction-control unit “TCU”; in this context do not confuse that abbreviation with the transmission control unit.
Normal deceleration fuel cut can stop injection during a qualifying overrun, but a lift-off event can also include clutch disengagement, a gearbox change, idle intervention or stability control. Seeing closed pedal or a lean exhaust reading does not establish which function caused a change in vehicle deceleration.
Example calibration fields
In the VHST reference these are scalar calibrations, not driver-adjustable wheel-slip maps. They are research leads, not recommended settings:
c_vs_min_msr is labelled a minimum vehicle-speed condition in km/h for the described MSR path. Other request, error and enable conditions apply; the value shown in an extracted description is not a universal operating threshold.
c_t_dly_diag_msr is a delay for the described emergency ramp, in seconds. c_lgrd_tqi_inc_diag_msr is its torque-change limit in Nm per 10 ms. The reference describes ramping after an enable change while active; verify signs, conditions and time base before interpreting a logger.
c_tq_msr_int_dec is labelled a decrement for the MSR torque integrator. c_tq_msr_int_max is a plausibility threshold in N·m·s. These do not set a traction target or tyre grip.
The separate ECM2 monitoring reference lists c_vs_min_msr_intv_mon, c_t_dly_msr_deac_mon and c_t_dly_msr_inh_mon as monitoring-level speed or delay conditions. They are distinct from the VHST function-level values. Do not alter plausibility monitoring to conceal communication, sensor or vehicle faults.
Signals for diagnosis
lv_msr_ena is the VHST enable condition; lv_msr_emergency denotes the reference's emergency state. tqi_msr_fast and tqi_msr_slow are fast and slow requested intervention values in Nm, not measured torque. tq_msr_int is a torque-by-time accumulator in N·m·s. VHST source.
lv_msr_tq_act is labelled MSR responsible for an increased torque request in the PTQM reference. It is a state indication, not a slip measurement.
lv_msr_req_mon, lv_msr_act_mon and lv_msr_not_plaus_mon describe monitored request, active and communication-plausibility states in the ECM2 reference. Their names or status encodings may differ in diagnostic tools; do not assume a zero or unavailable channel proves that the vehicle lacks the feature.
When investigating an unexpected lift-off or downshift response, record full engine, ABS/ESC and gearbox faults; tyre sizes and pressures; road and weather conditions; pedal and brake state; gear/clutch state; individual wheel speeds; requested and estimated engine torque; throttle; fuel-cut state; and available MSR/ASR request, active and fault signals. Synchronise the logs and check each signal's scaling and sample rate. A small brief difference between requested and actual torque does not by itself prove an MSR intervention or a fault. Do not deliberately create wheel slip on public roads.
Aftermarket feature scope
The simos.app Main Patch guide says its product-specific OEM ASR Sport mode ignores ESP requests for engine-torque cuts but leaves MSR and the described ESP stability/brake interventions active. This is the publisher's description of that patch, not a statement about every tune or a guarantee of all vehicle functions. Confirm installed patch, version, settings and hardware. For COBB custom slip-target and shift-freeze tables, see traction control tuning.
Related: deceleration fuel cut · DSG torque coordination · torque monitoring and plausibility · traction control tuning. References reviewed 17 November 2026.
Revision 1: Simos 18 engine drag torque and MSR control
Scope. Engine drag-torque control, commonly called MSR, addresses driven-wheel slip during deceleration. It is distinct from acceleration traction control (ASR), normal trailing-throttle fuel cut, and a gearbox shift request, although these systems can interact. The software examples below are from the community SC8S5031_C_OEM Simos 18.1 reference; verify the exact ECU, engine, transmission, ABS/ESC equipment, ASW/CAL, configuration, units and logger support.
What happens on lift-off
Volkswagen SSP 374 describes an engine-braking control example in which the ABS/traction controller uses wheel-speed and engine information to detect driven-wheel slip after torque reduction. It requests a change through the engine controller; the illustrated system can briefly open the throttle to reduce the braking effect. This is an explanation of a documented Volkswagen control concept, not proof that every Simos 18 vehicle has exactly the same algorithm, message or actuator response.
In the SC8S5031 VHST deceleration-slip reference, a valid external traction-control request, MSR enable and absence of the relevant disable condition permit a torque request to enter fast and slow coordination paths. A torque request or an enable flag is not a direct measurement of wheel grip or delivered torque. The reference calls the requesting traction-control unit “TCU”; in this context do not confuse that abbreviation with the transmission control unit.
Normal deceleration fuel cut can stop injection during a qualifying overrun, but a lift-off event can also include clutch disengagement, a gearbox change, idle intervention or stability control. Seeing closed pedal or a lean exhaust reading does not establish which function caused a change in vehicle deceleration.
Example calibration fields
In the VHST reference these are scalar calibrations, not driver-adjustable wheel-slip maps. They are research leads, not recommended settings:
c_vs_min_msr is labelled a minimum vehicle-speed condition in km/h for the described MSR path. Other request, error and enable conditions apply; the value shown in an extracted description is not a universal operating threshold.
c_t_dly_diag_msr is a delay for the described emergency ramp, in seconds. c_lgrd_tqi_inc_diag_msr is its torque-change limit in Nm per 10 ms. The reference describes ramping after an enable change while active; verify signs, conditions and time base before interpreting a logger.
c_tq_msr_int_dec is labelled a decrement for the MSR torque integrator. c_tq_msr_int_max is a plausibility threshold in N·m·s. These do not set a traction target or tyre grip.
The separate ECM2 monitoring reference lists c_vs_min_msr_intv_mon, c_t_dly_msr_deac_mon and c_t_dly_msr_inh_mon as monitoring-level speed or delay conditions. They are distinct from the VHST function-level values. Do not alter plausibility monitoring to conceal communication, sensor or vehicle faults.
Signals for diagnosis
lv_msr_ena is the VHST enable condition; lv_msr_emergency denotes the reference's emergency state. tqi_msr_fast and tqi_msr_slow are fast and slow requested intervention values in Nm, not measured torque. tq_msr_int is a torque-by-time accumulator in N·m·s. VHST source.
lv_msr_tq_act is labelled MSR responsible for an increased torque request in the PTQM reference. It is a state indication, not a slip measurement.
lv_msr_req_mon, lv_msr_act_mon and lv_msr_not_plaus_mon describe monitored request, active and communication-plausibility states in the ECM2 reference. Their names or status encodings may differ in diagnostic tools; do not assume a zero or unavailable channel proves that the vehicle lacks the feature.
When investigating an unexpected lift-off or downshift response, record full engine, ABS/ESC and gearbox faults; tyre sizes and pressures; road and weather conditions; pedal and brake state; gear/clutch state; individual wheel speeds; requested and estimated engine torque; throttle; fuel-cut state; and available MSR/ASR request, active and fault signals. Synchronise the logs and check each signal's scaling and sample rate. A small brief difference between requested and actual torque does not by itself prove an MSR intervention or a fault. Do not deliberately create wheel slip on public roads.
Aftermarket feature scope
The simos.app Main Patch guide says its product-specific OEM ASR Sport mode ignores ESP requests for engine-torque cuts but leaves MSR and the described ESP stability/brake interventions active. This is the publisher's description of that patch, not a statement about every tune or a guarantee of all vehicle functions. Confirm installed patch, version, settings and hardware. For COBB custom slip-target and shift-freeze tables, see traction control tuning.
Related: deceleration fuel cut · DSG torque coordination · torque monitoring and plausibility · traction control tuning. References reviewed 17 November 2026.