This reference examines torque-related characteristics in SC2C3031_Ce_ro.a2l, found in a publicly indexed archive labelled as Simos 12.2. The file describes an enriched EA888 project with structure C30 and EPK SC2C300. Those are claims in the file, not independently verified proof of factory origin, usage rights, completeness or compatibility with the accompanying HEX or any vehicle.
Driver request and monitoring
The file describes ip_fac_tq_req_driv_drof as a driver-torque-request factor for a drive-off situation. Its axis inputs are engine speed and accelerator-pedal activation. This name describes a factor, not an independently measured torque output; the definition does not establish whether it is active in a given state or how it combines with other requests.
Separately, ip_fac_tq_req_driv_dct_mon is described as a scaling factor for requested clutch torque with a dual-clutch transmission. Its inputs reference engine speed and accelerator-pedal activation at a monitoring level. Similar entries are named for automatic, CVT and manual transmission configurations. The names and axes provide research leads, not proof that each function is present, selected or used on a particular car. Do not assume that changing a monitoring-related factor changes the ordinary torque request in the same way, or use one to conceal an implausible model.
Protection and fault-related limits
Two separate maps, ip_tqi_tcha_prot and ip_tqi_tcha_prot_bpa, are described respectively as torque limitations during turbocharger protection because of errors and because of a boost-pressure actuator error. Both reference engine speed and ambient pressure; the file describes the ambient-pressure quantity as measured or adapted. A plausible displayed ambient value alone is therefore not proof of a live sensor measurement. The labels do not establish the active fault, actual torque limit or resulting actuator position.
The file also describes ip_tq_max_vs_err as a torque limitation for a vehicle-speed signal error, using a moving mean engine-speed input. ip_fac_tqi_pow_lim_pi is described as a factor limiting indicated torque after pre-ignition detection, with engine speed among its inputs. These examples illustrate that a torque-related calibration can be conditional on a fault or protection state; they do not specify the actual values or establish that a given car is intervening. Follow the current vehicle-specific diagnostic procedure rather than changing a limit to hide a fault.
Efficiency-mode torque and transitions in C30
In the same A2L, ip_tq_pow_max_eco[0] and ip_tq_pow_max_eco[1] are described as target clutch-torque limitations during active efficiency mode. Each references axis-point definitions named ldp_n_tq_pow_max_eco and ldp_gear_tq_pow_max_eco, but both axis input quantities are explicitly NO_INPUT_QUANTITY. The axis-point names suggest speed and gear as possible contexts, but they do not identify the actual runtime signals or what selects either indexed map. Do not infer the active gear, drive mode or numerical limit solely from the names.
Separate curves ip_tq_lgrd_pow_eco_down and ip_tq_lgrd_pow_eco_up describe maximum allowed torque steps during efficiency-mode activation and deactivation respectively. A further ip_fac_lgrd_pow_eco_pv_grd is labelled as a factor in torque-step calculation based on pedal gradient during those transitions. These are distinct descriptions from the target limit maps. Their declared axis inputs are also NO_INPUT_QUANTITY; the labels do not establish the underlying signals, formula, calibrated values or when a real car selects the strategy.
When investigating a mode-dependent response, compare a verified mode indicator with pedal, engine speed, gear, requested and estimated torque, and relevant transmission intervention where accurately defined. Repeat tests at matched conditions and check timestamps. A change in response alone does not prove one of these maps was selected; the indexed file is unverified and is not a tuning recipe.
Using a definition alongside a log
- Record the ECU part and software identifiers, calibration, transmission, fuel, modifications and complete fault scan. Establish the origin and permitted use of the definition and match it to the actual binary before assuming that symbols or conversion factors apply.
- Where the logger and ECU support correctly defined channels, compare pedal, engine speed, torque request and limits, transmission context, relevant fault status and measured engine response under repeatable conditions. Distinguish requested and estimated torque from independent measured output.
- Verify axes, units, scaling, map selection and operating modes against the exact software. A definition describes metadata; it does not supply the running calibration values, establish which table wins or prove an intervention. Preserve the actual read and confirm the chosen tool’s recovery capability before any write.
This C30 example is separate from the seller-labelled 12.1 file in the Simos 12.1 torque and load review. For combustion-mode and fuel-pressure selection labels from this same C30 A2L, see the Simos 12 injection guide; neither example proves compatibility with another ECU.
Source and verification scope
Publicly indexed archive containing SC2C3031_Ce_ro.a2l. Characteristic descriptions, axis inputs and measurement descriptions inspected 17 November 2026. SHA-256 of the extracted A2L: 7b5194ebeac25329b69ec0880251fc9e9ce50e4a795b72fd8608f6314c052fad. The hash identifies the examined text; it does not verify authenticity, rights, calibration values, compatibility or runtime behaviour.