Scope. The ECU examples below are from the community SC8S5031_C_OEM Simos 18.1 reference. Map names, software selectors, gearbox configuration, drive modes, axes and units must be checked against the target ECU. Some extracted descriptions disagree with field labels. No map addresses or universal settings are implied.
From pedal position to torque request
The pedal is an input to a torque-oriented engine-management system, not a direct instruction for the throttle plate to open by the same percentage. EcuTek describes driver demand entering Simos 18's coordinated torque calculation, with air-path and faster ignition/fuel interventions contributing to the result. Limits, gearbox requests, traction control and operating conditions can alter delivered response. EcuTek EA888 engine-tuning guide.
Making the pedal request rise more quickly can make part-pedal response feel sharper. It does not by itself increase a hardware or ECU torque ceiling, and the same pedal angle need not produce the same output in every gear or driving mode. A request, a limit and the modelled delivered torque are distinct. A sudden change in pedal scaling can reduce fine control at low speed.
SC8S5031 interpretation maps
The DRRQ pedal interpretation reference lists separate scaling-factor maps for gearbox and vehicle-speed situations. These factors are not themselves torque in Nm:
ip_fac_tq_req_driv_h_vs_dctandip_fac_tq_req_driv_l_vs_dctare labelled high- and low-vehicle-speed driver-interpretation maps for DCT. The displayed axes are engine speednand pedal valuepv_av_hin percent; the output is a factor. Their copied functional-description text refers to a different transmission, so verify the source and active selector rather than trusting the caption alone.ip_fac_tq_req_driv_h_vs_mtandip_fac_tq_req_driv_l_vs_mtare corresponding high/low speed manual-transmission examples. Their axis references have rpm and pedal-percentage units; the rpm input is markedonline_dummy, so its exact runtime source needs confirmation.c_vs_thd_min_dctandc_vs_thd_max_dctare vehicle-speed thresholds used in low/high scaling-factor selection. Corresponding manual thresholds includec_vs_thd_min_mtandc_vs_thd_max_mt. The reference describes interpolation between thresholds for its relevant path; verify the complete selector and calibration in the target.ip_fac_tq_req_driv_spt_mtis a sport-mode driver-demand factor for manual transmission against an rpm-labelled axis whose input isNO_INPUT_QUANTITY.clf_req_driv_spt_driv_modselects driving modes associated with sport pedal maps; the exact bit meaning and selection must be matched to the ECU.ip_fac_tq_req_driv_drofis a drive-off request factor against engine speed and pedal value. Its function is separate from a full-load torque limit. Off-road and reverse-related fields also appear in the reference, but their presence does not prove those paths are fitted or enabled.
Compare signals rather than labels alone
fac_pt_tq_req_driv and fac_eng_tq_req_driv are runtime factors; tq_pt_driv_req and tq_eng_driv_req are torque-request measurements in the cited DRRQ reference. The source distinguishes the driver's request to the powertrain from the powertrain request to the combustion engine. They are not interchangeable dyno torque measurements, and their names or availability can differ between loggers.
Compare accelerator position, drive mode, vehicle speed, gear, driver request, applicable torque limit and modelled torque with throttle position, air-charge and boost targets, and active intervention. Record the same pedal sweep at comparable speed and conditions. The COBB MQB monitor descriptions distinguish driver-requested torque and other product-specific torque channels; check units, sampling and supported vehicles.
Aftermarket interpretation and diagnosis
EcuTek's EA888 RaceROM guide describes accelerator multipliers and drive-mode-dependent torque limits for its own feature. They are product-specific controls, not guaranteed translations of the OEM DRRQ map names. Selection, maximum request, gearbox coordination and protections must be evaluated for the installed feature.
- Record ECU software, engine and gearbox, drive mode, selected aftermarket map, fuel and fault codes. Verify pedal sensor and brake-switch operation and attend to electrical or mechanical faults first.
- Compare low-speed manoeuvring, steady part-pedal operation and controlled transitions using repeatable conditions. Note traction or gearbox interventions and the active low/high-speed or mode selection where supported. Do not use uncontrolled public-road testing to force a response.
- A large request without corresponding output can reflect a limit, traction intervention, air-path capacity or other control state. Investigate the active constraint before treating the pedal table as the cause.
- Maintain pedal plausibility, safety and transmission-related monitoring. Changes should preserve predictable progression and closed-throttle behavior; a more aggressive request is not proof of increased engine capacity.
For gear-dependent ceilings, see Simos 18 torque and boost by gear.
Related: torque model calibration · throttle control · traction control · DSG torque coordination · switchable maps.
Sources
- Community SC8S5031 DRRQ pedal interpretation — image-specific map and signal definitions; copied descriptions can conflict.
- EcuTek EA888 engine tuning and EA888 RaceROM tuning — application- and product-specific control descriptions.
- COBB VW/Audi MQB monitor list — product-specific logging definitions.
HP Tuners display names and selection
The Simos Wiki HP Tuners table notes describe Max Torque 0–2 Power Class 0–4 and Torque Percent High / Low / Transmission under Engine → Torque Management → Driver Demand. In that community description, a pedal/rpm-based percentage is applied to a maximum-torque lookup, with different tables associated with transmission, speed and drive mode. The author explicitly says further testing is needed to confirm selection of the maximum-torque tables. These are HP Tuners display names and an interpretation of particular calibrations, not universal OEM identifiers. Identify the active table and selector with the matching definition and logs before making changes; do not assume all variants should be made identical.