Scope: Simos engineering names are examples from the community SC8S5031_C_OEM Simos 18.1 cross-reference unless a different source is named. Match ECU and gearbox hardware, engine, ASW, calibration, definition and any patches. Verify axes, units, array indices, signs, selectors and logger scaling: extracted labels can conflict. Product display names are not necessarily OEM identifiers. SC8S5031 reference.
Follow the request through the model
The ECU interprets pedal input into a torque request, coordinates limits and converts an indicated-torque setpoint into an air-charge target. A separate model estimates reference torque from air charge and then applies efficiencies and other corrections. Indicated, clutch/output, requested, limited and estimated torque are different quantities; a logged ECU estimate is not a dyno measurement. EcuTek describes fast ignition/fuel/cut and slower air/throttle/turbo/cam paths in its EA888 tuning guide.
Driver interpretation and limits
ip_fac_tq_req_driv_h_vs_dctandip_fac_tq_req_driv_l_vs_dctare example high- and low-vehicle-speed DCT driver-interpretation factor maps;ip_fac_tq_req_driv_h_vs_dct_sandip_fac_tq_req_driv_l_vs_dct_sare sport-program examples. Their published axes are engine speed and pedal percentage and their output is a factor, not Nm or boost. One adjacent extracted caption conflicts with the DCT label; confirm the actual software and selector. DRRQ pedal interpretation.ip_tq_pow_max_atandip_tq_pow_max_mtare community-listed maximum clutch-torque families, whileip_tqi_pow_max_basis an indicated full-load limit in the TQSP reference. Their location in the torque chain differs; check the active power class, transmission and other selectors rather than transferring values between them.ip_tq_lim_gb_prot_max_dctis an ECU-side maximum allowed clutch-torque map for twin-clutch gearbox protection, with speed and gear axes in the example. The documented function includes an autonomous protection state; it is not the TCU's clutch-pressure map and does not establish mechanical capacity.tq_gb_prot_clcandtq_lgrd_gb_protare calculated runtime signals. TRSM gearbox protection.
Torque-to-air and air-to-torque
ip_maf_stk_sp_vvl_cam_h[1][2][1] and ip_maf_stk_sp_vvl_cam_l[1][2][1] are examples from the torque-based air-mass setpoint family: engine speed and indicated torque are inputs and air mass per stroke is the output. ip_tqi_ref_n_m_air_vvl_cam_h[1][2][1] and ip_tqi_ref_n_m_air_vvl_cam_l[1][2][1] are examples of the reference indicated-torque family: speed and cylinder air mass are inputs and torque in Nm is the output. Flap, valve lift and intake/exhaust cam selections matter. The source's extracted flap captions can conflict, so verify actual state and selection rather than assuming an index.
Compare the two relationships across the operating region and selected modes, but do not assume they are exact inverses after efficiencies, losses, corrections and limits. tqi_sp_slow_cbk_sel[0][1], tqi_sp_maf_cbk_sel[0][1] and tqi_pow_max_maf are runtime examples from the air-setpoint reference, not extra calibration maps.
Efficiency and combustion-mode corrections
ip_eff_iga_vvl_cam_h[1][2][1] and ip_eff_iga_vvl_cam_l[1][2][1] are example ignition-efficiency curves selected by flap, lift and cam conditions, with an ignition-angle-difference axis in the published data. ip_tqi_ref_ofs_cmb[7] is an example reference-indicated-torque correction for a combustion mode versus speed and air mass. The index does not identify the same mode on every software version. tqi_ref_iga and tqi_ref_iga_lamb are modelled measurements incorporating ignition-efficiency and, for the latter, lambda-efficiency correction. Sources: ignition efficiency, combustion-mode efficiency, and reference torque.
COBB's MQB example explains that reference-versus-base ignition difference feeds an efficiency calculation used with reference indicated torque. It notes an axis-display issue in its extraction. This is a useful illustration of why changing the ignition reference can affect the torque model; verify the actual tool's axis presentation and do not use that example as a universal equation.
Limit coordination signals
The TQSP engine-torque limit reference lists tq_pow_max_bas for a hardware-restriction torque limit, tq_pow_max_bas_fil for a filtered basic limit used in driver-request scaling, tq_pow_max_bas_trans for a transmission-type full-load clutch torque limitation, and tq_pow_max_cam_in for an inlet-cam fault-related limit. These are runtime measurements, not editable maps; a single value does not establish which limit ultimately controlled the request.
Diagnosing a limit
On supported COBB MQB applications, Driver Requested Torque Scalar, Driver Requested Torque, Torque Maximum Clutch, Torque Maximum Engine, Torque (Actual), Torque Value for Air Mass Set Point and Torque Limitation Source are display/logging names, not OEM map identifiers. Compare them with air-mass setpoint and actual, flap/lift/cam state, gear, pressure, wastegate, lambda and ignition. The source documents some limitation-source codes, but their meaning and availability must be checked for the actual tool and vehicle. COBB MQB monitor definitions.
A Simos 18 load and torque discussion considers the distinction between modelled torque and physical output and the possible gearbox consequences of under-reporting. Its contributors' interpretations are useful leads, not independently verified calibrations or a substitute for a matched ECU/TCU test.
A flat log can reflect a limit, sensor range, data scaling or sampling. Investigate the active source and both ECU and gearbox requests before altering calibrations. EcuTek's Golf R example calls its pedal and air-path displays Driver Interpretation Map, Maximum Torque AT/MT, Maximum Torque Final and Reference Air Charge; these are product labels and do not imply every ECU uses the same selection. EcuTek EA888 guide.
Detailed valve-train guides: camshaft timing · valve lift tuning.
Detailed air-path guides: air charge modelling · throttle control.
For monitored torque deviations, process-monitoring map examples and safety intervention signals, see Simos 18 torque monitoring and safety plausibility.
For pedal interpretation and driver-request map examples, see Simos 18 accelerator pedal and driver torque request.
Related: torque and DSG overview · torque model calibration · DSG torque coordination · DQ250 pressure and adaptation · bigger turbo tuning · log diagnosis.
Example from a Simos 18.1 file comparison
Scope of example: A user-supplied comparison of a Simos 18.1 stock file, Stage 1 and Stage 1 pops-low, with a WinOLS CSV definition export. LTEditor identified box code 5G0906259E and software 111SC800H6G00000. The files and definitions are not publicly available, so this is a single, independently unverified file-comparison observation, not a recommended calibration. The source’s stock values matched supported byte and 16-bit entries after accounting for table transposition. Selection, runtime logic, operating conditions and checksum suitability were not independently established.
In this comparison, selected ip_tq_pow_max_at[0][0] entries changed from 350 to 380 Nm, ip_tqi_pow_max_bas[0] from 380 to 410 Nm, and ip_tq_lim_gb_prot_max_dct from 370 to 445 Nm. A selected ip_tqi_ref_n_m_air_vvl_cam_h entry changed from 520.4375 to 445 Nm. These are examples from different places in the torque chain: a higher limit or a lower reference estimate alone does not establish actual torque, active limitation, or gearbox capacity. Verify axes, active selector and ECU/TCU interaction.