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.
ECU and TCU have separate jobs
The engine ECU reports modelled torque and responds to gearbox torque requests. The transmission controller has its own torque limits, clutch, hydraulic, shift and adaptation controls. The EcuTek DQ250 and DQ381 guides describe use of engine torque in their documented systems, including pressure control; both identify accurate ECU torque estimation as important. A lower reported torque is not a measurement of reduced clutch load. The EcuTek pressure derivation includes stated uncertainty and should not be generalised to every DSG.
Simos ECU intervention examples
The SC8S5031 TRSM gearbox-intervention reference identifies ip_t_tq_gb_intv_down[2] and ip_t_tq_gb_intv_up[2] as ramp times down or up to driver request at the end of a gearbox intervention. The published example uses transmission-related speed and gear axes, with time in seconds. They are engine-ECU post-intervention ramp calibrations, not TCU shift-duration maps; confirm index, selectors and direction in the actual software.
lv_tq_gb_intv_ramp_down, lv_tq_gb_intv_ramp_up and state_gb_intv_dec_fast are runtime flags/state, not calibration maps. Check the logger's enum and timing; a state alone does not prove the cause of a shift complaint. ip_tq_lim_gb_prot_max_dct is a separate ECU-side gearbox-protection clutch-torque limit, with rpm and gear axes in the published TRSM protection example; it is not a gearbox pressure control.
The same SC8S5031 intervention reference lists tq_gb_intv_dec_fast and tq_gb_intv_dec_slow as fast and slow decreasing gearbox-intervention torque signals in Nm; tq_gb_intv_req_ena_fast is the requested and enabled fast-path torque, while tqi_gb_intv_dec_slow is an indicated-torque quantity. These are runtime measurements rather than maps, and they represent different stages or torque quantities. Availability, sign, no-request values and alignment depend on the matching logger and ECU software. They are not direct measured clutch torque.
In the documented DQ250 example, shift-time maps are described as using accelerator position and the gear-change type to select an initial target; the author explains that torque reduction, pressure, overlap and ramp limits can affect the realized shift. Distinguish a TCU time target from the duration actually observed across a gear change, and from the Simos post-intervention ramp time above. Compare the same shift, mode, load and gearbox temperature before drawing conclusions.
Protection fallback versus shift requests
The community SC8S5031 TRSM gearbox-protection extraction lists ip_tq_gb_prot_tcu_lih_dct as a DCT torque-limit map for an autonomous gearbox-protection state, with engine speed n in rpm and vehicle speed vs in km/h as axes and Nm output. Its copied table prose instead says CVT. Resolve that contradiction and the actual state and selection in matched software before interpreting it; this is an ECU-side protection-path calibration, not the normal gear-change torque request or a measured clutch limit. c_t_hld_tq_lim_gb_prot_dct is described separately as a DCT protection-ramp delay in seconds. Its presence does not establish that the fallback was active or justify changing it to hide a fault.
The TRSM intervention extraction also identifies lv_tq_gb_intv_plaus_dec_fast and lv_tq_gb_intv_plaus_inc_fast as runtime plausibility flags for decreasing and increasing fast requests. They are diagnostic context, not calibration tables or direct clutch-force measurements. Confirm flag polarity, ECU software, log availability and request timing before interpreting an apparent mismatch. clf_tq_gb_intv_dec_ena_slow is a separate calibration field described as enabling the slow decrease path; its encoded meaning and active bit selection must be verified in the target.
DQ250 six-speed example
EcuTek's DQ250 guide uses product labels including Clutch Target Torque Correction Clutch 1 & 2, Maximum Torque Clutch 1 & 2 and Line Pressure Setpoint (torque). Its interpretation of some pressure and protection calculations is qualified by the author. These are TCU controls for the documented example, not Simos ECU identifiers or recommended values. Pressure request, actual pressure, solenoid current, clutch slip and adaptation are distinct. See the existing DQ250 clutch-pressure and adaptation guide.
DQ381 seven-speed example
The EcuTek DQ381 guide describes TCU labels Torque Actual (& Efficiency), Torque Limit (Depleting & Efficiency), Maximum Torque (gearbox protection), Maximum Torque (temperature), Target Torque P4 1 & 2 and Target Pressure P4 1 & 2. EcuTek describes P4 targets in the adaptation context and explicitly notes that its torque-to-pressure derivation is not fully documented. Preserve that uncertainty and check the exact TCU and tool definition. These limits and requests do not establish actual pressure or physical torque capacity.
The COBB seven-speed guide also uses product labels Target Gear Change Time and Clutch Overlap. Shift time, overlap, torque reduction and clutch pressure interact; a shorter table target alone does not establish a completed or mechanically sound shift. COBB's six-speed guide describes its six-speed schedules with axle torque and throttle axes and engine-speed output, unlike its documented seven-speed schedules with vehicle-speed output. Verify gear, mode, direction, ratios and actual TCU software before comparing or transferring a schedule.
DQ381 shift crossover and torque recovery
In EcuTek's DQ381 documentation, the product-labelled Overlap times (mode gear) maps use clutch input torque and input speed for overlap targets. The guide describes Clutch Overlap time Temperature Compensation as a fluid-temperature-dependent blend and Minimum Clutch Overlap Time as a mode-specific lower target limit. These are TCU controls for its documented example, not direct measurements of clutch slip, pressure or completed shift time. Use the correct software, gearbox type, mode and shift direction; the stated relationship between requested torque and clutch pressure remains partly inferred in that guide.
The same guide labels Torque Reduction After Driver Demand as a post-upshift or downshift torque-reduction control with a motor/clutch-torque input. It describes Maximum Torque Rate of Change (Input Shaft Differential Speed) and a separate Maximum Torque Rate of Change (Launch Control) as different ramp constraints. These TCU product labels do not identify the ECU's ip_t_tq_gb_intv_up[2] or ip_t_tq_gb_intv_down[2], which describe an ECU-side intervention-ending ramp. The author says some time-target selection and torque-to-pressure details remain unconfirmed; do not assume a single table determines the complete shift or that raising limits proves clutch capacity.
EcuTek's DQ381 example ROM notes identify Kre_GrNpKi_kf and Kre_GrNpKp_kf as integral and proportional controller amplifications against engine torque and hydraulic temperature. They are gearbox-controller map names from a particular development file with upgraded clutch packs, not Simos 18 ECU maps or transferable values. Confirm axis, units, calibration and hardware before interpretation.
Logging and adaptation
Where supported, align ECU and TCU timestamps and compare engine torque request/limit/estimate, throttle, ignition, engine speed and gear with the gearbox's reported engine torque, target gear, shift state, torque-reduction request and active state, clutch speeds/slip, pressure and gearbox temperature. COBB lists (DSG)Engine Torque, (DSG)Torque Reduction Request, (DSG)Torque Reduction Active, (DSG)Clutch 1 Slip, (DSG)Clutch 2 Slip, (DSG)Line Pressure and (DSG)Line Pressure Set Point for selected MQB vehicles. It notes some intervention flags have unknown full enumerations; these are monitors rather than maps and are not available on every vehicle. COBB DSG monitor list. Compare actual and target quantities and remember controlled slip can occur during an intended handover.
EcuTek specifies adaptation after programming in its documented DQ250 and DQ381 workflows; consult the correct current vehicle, software and tool procedure, capture faults and existing state, and do not assume a blanket reset is appropriate for every flash or complaint. A large numeric torque field or patched representation is not a verified clutch, gearbox or hardware rating.
Comparing reports of clutch slip and shift feel
COBB describes its (DSG)Clutch 1 Slip and (DSG)Clutch 2 Slip monitors as calculated, and the individual clutch temperatures as inferred from overall transmission temperature. Its clutch pressure and line pressure channels have different labels and purposes; pressure setpoint, current, slip and inferred temperature are not interchangeable, and channel support varies. COBB MQB DSG monitor list.
In a 2019 Stage 2 Golf R discussion, the owner reported a slipping sensation around 3,500 rpm in higher-load conditions, then reported that it disappeared after switching to a different Stage 2 tuning file, with the final ECU and TCU file combination unspecified. The owner also reported a short-lived improvement after another TCU-file revision. Software changes and test conditions were not controlled, underlying logs and physical clutch condition were not independently verified, and the ECU and gearbox identities need confirmation. The account motivates collecting matched pressure, torque and speed evidence; it does not establish a general defect in a particular tuner or rule out clutch or hydraulic wear.
In a separate seven-speed owner's account, a perceived slow 2–3 shift after changing ECU/TCU software later seemed to improve following repair of an exhaust leak. The owner revised their interpretation toward altered shift sound. There is no matched shift-time or slip trace and no established causation: exhaust sound alone cannot establish clutch slip or prove a mechanically sound shift.
For gear-dependent torque and boost ceilings, see Simos 18 torque and boost by gear.
Related: torque and DSG overview · torque model calibration · DSG torque coordination · DQ250 pressure and adaptation · bigger turbo tuning · log diagnosis.
Automatic schedule and manual mode
In COBB’s documented six-speed and seven-speed MQB DSG guides, the described automatic shift schedules are used in automatic modes rather than Tiptronic manual mode. The seven-speed example places upshift and downshift thresholds together as vehicle-speed outputs; the six-speed example separates upshift and downshift tables with engine-speed outputs. When investigating unexpected shifts, record mode, pedal position, gear and speed before deciding which schedule or other intervention applies. This is guidance for the COBB examples, not proof of every TCU variant’s behaviour.