This guide concerns coordination between the engine ECU and DQ381 transmission controller on documented Mk8 EA888 Evo4 examples. EcuTek lists Simos 19.3 and 19.6 in its Evo4 ECU support; this does not mean every vehicle with either ECU has the same gearbox or software. Identify both controllers and their exact hardware and calibration before applying any tool-specific guidance. [1]
Separate the requests, limits and reported torque
The engine ECU and transmission controller coordinate torque over the vehicle network. In EcuTek's Mk8 example the TCM limits torque from the ECM; engine torque is also reported to the TCM. These are different pieces of information travelling in different directions. A driver request, the torque permitted by an applicable limit, an engine's estimated torque and the physical torque carried by the clutch are not interchangeable. A numerical ECU channel alone does not establish the load at the clutch. [1]
EcuTek warns that under-reporting engine torque to the TCM may cause clutch slip or harsh shifts. Lowering a reported number does not lower the real load. Investigate the matched engine and transmission calibrations and their limits together; do not use an inaccurate torque signal to hide an incompatible combination. [1]
EcuTek's Evo4 engine tuning guide describes ECU-side torque-limit maps by drive mode, power class and gear. Its RaceROM base-limit override applies to certain engine-side limits; EcuTek states it does not override the TCM torque limit received over CAN. The relevant map names, feature enablement and definitions depend on the matched ECU file. Raising an ECU map or enabling a tool feature therefore does not establish that the TCM will accept more torque. [2] [3]
Confirm transmission support separately
EcuTek's cited Mk8 overview states that its ProECU product did not provide Evo4 DQ381 programming in the documented release. This is a product-specific statement, not a claim that nobody can tune that transmission. TVS reported DQ381 Gen2 software solutions in its October 2022 development update and noted further bootloader differences on some later vehicles in June 2023. Both are historical supplier statements; confirm present support for the exact TCM hardware, software and vehicle with the chosen provider before planning the work. [1] [4]
Build a focused log
COBB's Mk8 monitor list separates older pre-CCF monitors for v100 maps and tunes made before 15 February 2024 from its fast-logging list. The older list includes Gearbox shift fast requested torque, Engine torque clutch limitation, Engine torque clutch protection, Engine torque limitation (main), and Selected gear. Its fast list includes Current Gear, Current Gear Predicted, Engine Torque (Max Allowed), Maximum Torque at Clutch, Torque at Clutch, Torque Actual, and fast and slow torque set points. These are COBB labels, not universal names or guaranteed signals on every calibration. Confirm availability, definitions, units and sample timing for the actual tool and map. [5]
- Record engine and ECU identifiers, TCM hardware and software, gearbox, tyre and final-drive setup where relevant, active driving mode, fuel, modifications, fluid temperatures and faults. Establish a healthy, comparable baseline.
- Compare driver demand, available torque setpoints and limits, engine speed, current gear and the shift event with throttle, boost target and actual, ignition and relevant temperatures. Note when a change begins, its duration and whether it repeats in the same gear and mode. Sample rate and channel alignment matter; use smaller focused logs if needed. [6]
- A falling ECU torque value near a shift does not by itself prove which controller requested it or which limit was active. Check supported intervention and limit channels, definitions, faults and operating conditions before attributing a cause. A channel named “actual” is not automatically a direct torque measurement or proof of the value received by the TCM.
- If clutch slip is suspected, corroborate with suitable TCM data such as input and output shaft speeds, selected gear and clutch slip or pressure information where supported and properly defined. An engine-only torque trace is insufficient to prove clutch slip or determine clutch pressure. Investigate faults and the mechanical condition as well as calibration.
For engine torque-to-air modelling, see Simos 19 EA888 Evo4 torque demand and air model. For gearbox fault context, see DQ381 and DQ500 gearbox faults and diagnosis.
Sources
- [1] EcuTek: VW AG EA888 Evo4 (Mk8). ECU support, DQ381 programming statement and torque-reporting warning.
- [2] EcuTek: VW AG EA888 Evo4 Engine Tuning. ECU torque maps for the supported product.
- [3] EcuTek: VW AG EA888 Evo4 RaceROM v1. Base-limit override and TCM CAN limit.
- [4] TVS Engineering: EA888.4 MQB EVO Simos 19 release. DQ381 Gen2 supplier development updates dated October 2022 and June 2023.
- [5] COBB: Engine Monitor List MK8 Vehicles. Version-specific engine logging names.
- [6] COBB: MK8 / 8Y Datalogging Review. Logging and sample-rate considerations.
Sources accessed 17 November 2026. Product features and supported controller versions may change.