Tuning Wiki

This is a historical revision. Read the current page or return to its history.

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

Scope: The names and descriptions below are examples from the community SC8S5031_C_OEM Simos 18.1 cross-reference; they are not proof that other Simos 18 variants have identical monitoring, calibration addresses, units or fault behavior. Match the exact software, engine, transmission and definition. Extracted functional descriptions and axes can be incomplete or inconsistent, so verify selectors, signs and live signal availability. The examples are for understanding and diagnosis, not a recipe for defeating a safety function.

Why torque is monitored

A requested torque, a limit and the ECU's estimated engine torque are different quantities. In its EA888 Simos 18 example, EcuTek describes slow air-path and fast ignition, fuelling and cut paths. The community SC8S5031 reference also describes a monitoring calculation and comparison of desired and actual indicated engine torque. These are ECU model quantities, not direct crankshaft torque measurements. A mismatch may arise from a real control problem, incorrect inputs, a model mismatch, intervening logic or the way data is logged; a torque code alone does not identify the cause.

The ECM2 actual indicated torque reference describes reference torque corrected by efficiencies and other inputs. The monitoring reference describes an allowed instantaneous deviation and an integral difference. This is more than a single maximum-torque table; the described logic includes conditions, time behavior and other monitoring paths. Do not assume a similar fault on a different ECU uses the same comparison.

Example process-monitoring calibration names

  • ip_tqi_ref_sel_mon[0] is described as indicated engine torque at reference conditions for an engine-configuration-selective monitoring path. The documented output is Nm against monitored engine speed n_32_mon and an mg/stroke axis. The latter is identified as online_dummy in the extraction; confirm its actual runtime selection. ip_iga_ref_sel_mon[0] is the corresponding reference-ignition map in crank-angle degrees, and ip_eff_iga_mon is a monitoring ignition-efficiency curve. The [0] selector is not a portable description of flap, lift or other engine configuration. ECM2 reference.
  • ip_tq_dif_max_mon is described as an engine-torque-overflow diagnostic threshold map, output in Nm, versus n_32_mon and a torque-axis reference. The latter is marked NO_INPUT_QUANTITY in the extracted axis, so its precise runtime input needs confirmation.
  • ip_tq_dif_max_int_mon is described as a threshold in the integral torque-difference path, with monitored engine speed and tq_sp_mon torque axes and an Nm output. c_tq_max_dif_int_mon is separately described as an integral difference threshold in Nms. The units and separate variables matter; do not treat either as a normal torque request. ECM2 monitoring definitions.
  • DATA_MonTqLim.MonTqLim_tqDesOfs_M_VW is described as a desired-torque offset in Nm against engine speed and filtered desired torque. DATA_MonTqLim.MonTqLim_tqResvMax_T_VW limits torque reserve versus speed. The MonTqLim reference does not establish that these alone govern all torque monitoring or describe an appropriate change on a modified engine.

These calibrations belong to monitoring or coordination paths; a maximum allowed deviation, a reference model and the ordinary driver-demand limit are not interchangeable. Retain safety monitoring and diagnose the discrepancy rather than simply widening a threshold or masking the fault.

Runtime indicators and source limitations

  • tqi_av_h_rng_mon is the monitoring model's actual indicated torque; tqi_av_sel_mon[0] and tqi_ref_sel_mon[0] are selected actual and reference indicated-torque quantities. “Actual” here identifies an ECU calculation; it does not mean a torque transducer measured it. ECM2 indicated torque.
  • tq_dif_av_mon and tq_dif_max_mon are the calculated deviation and permitted deviation in Nm. tq_dif_av_int_mon is an integral difference in Nms; lv_err_tq_av_dif_mon and lv_err_tq_av_int_mon are error indicators. All are listed as measurements, not editable calibration maps. Confirm sampling and activation conditions. ECM2 monitoring.
  • lv_tq_lim_intv_fast and lv_tq_lim_intv_slow indicate active safety torque intervention in the TQSP safety-request reference. Their presence in an engineering reference does not ensure a scan tool exposes them or identify the original trigger.

COBB defines Torque Actual and Torque at Clutch as calculated or modelled monitors for its supported MQB applications and provides a Torque Limitation Source monitor. Its source is a product-specific compound indication and is not a universal decoder for every safety-monitor fault. The logger's units, channels, filtering and supported vehicles vary. COBB MQB monitor list.

Diagnosis after tuning or hardware changes

  1. Save the full ECU and gearbox diagnostic reports and freeze-frame conditions before clearing faults. Record software versions, patches, hardware, fuel, gear, temperature, rpm, load and the exact symptom. Use the current vehicle- and software-specific fault entry; do not assign a code to a map solely from a forum post.
  2. Check power supply, sensor and actuator faults and relevant air, fuel, ignition and transmission behavior. Compare pedal, indicated and clutch torque requests and estimates, active limitation sources, air-mass setpoint and estimate, manifold and upstream pressure, throttle, lambda, ignition and gear where supported. Align samples and establish what each logger actually reports.
  3. For a reproducible event, compare the modified configuration with a known healthy baseline and inspect the source-specific selected reference, correction and monitoring paths. A logger reaching a display ceiling does not prove the physical engine or every internal signal has reached that value. Do not force an on-road fault reproduction.
  4. A NefMoto port-injection discussion contains a participant's uncertainty over torque versus fuel-mass-flow monitoring during an MPI modification. It illustrates that a similar symptom can have competing explanations; the discussion does not establish a universal diagnosis or fix. Use the matched diagnostic information and validate any repair or calibration change with the monitoring and protective behavior intact.

Related: torque model calibration · DSG torque coordination · fuel system and MPI upgrades · tuning and log diagnosis.

Sources