Removed text is struck through; added text is highlighted.
This guide examines torque demand and the relationship between torque and air charge in the EA888 Evo4 examples described by COBB and EcuTek. EcuTek lists Simos 19.3 and 19.6 in its Evo4 product scope. The table names and counts below are product-specific descriptions for supported files; verify the exact ECU, software, definition and operating mode before assuming they apply.
Request, limit and delivered output
COBB's Mk8/8Y tuning guide presents a simplified chain: accelerator position contributes to driver torque demand, which is related to an air setpoint and then a boost target. Limits can act at more than one point. Driver demand, permitted torque, estimated torque, measured pressure and actual wheel output are different quantities. Changes to a request map do not prove that the engine obtained the requested air or torque.
COBB identifies Driver Clutch Torque Demand and Torque Demand From Accelerator Pedal among its editor's tables. It also describes limits dependent on gear, engine speed, ambient air density and drive mode. Those names help locate candidates in a matching COBB definition; they are not universal binary addresses. A table displayed in an editor can be inactive, effectively neutral at stock values, or active only under particular conditions. Investigate which condition and limit applies before changing it; do not remove protective limits to conceal a fault.
Torque-to-air and return model
In COBB's described strategy, the Mass Air Set Point for Torque Intervention tables relate requested torque and engine speed to an air target. Its guide describes 24 tables, split between two intake-flap groupings, with interpolation; it explicitly says the selection circumstances for individual tables are not fully defined. That count belongs to the documented COBB example, not every Simos 19 software version.
COBB identifies a corresponding set of Reference Indicated Torque tables used to check the resulting airflow, and a Maximum Cylinder Air Set Point limiter. Changing one side of the relationship without checking the corresponding references and limits can leave a mismatched model. Verify each table's axes and units, which indexed conditions are relevant, and consistency across the operating range. Indicated torque is a modelled combustion contribution before mechanical losses; it is not the same as actual measured crank or wheel torque.
COBB illustrates a stock Mk8 Golf R table whose values reach 1,500 mg/stroke in part of the displayed range, then shows an extrapolated example. That is one published calibration example, not a family-wide sensor limit, required edit or safe target. Axis rescaling and extrapolation change the region over which the controller interpolates; they require a matching definition and verification over both modified and unchanged areas. Preserve sensible low-load behaviour and compare the result against measured operation rather than treating the example's numbers as a tune.
Transmission coordination and custom features
Gearbox requests and communicated engine torque matter on automatic applications. EcuTek's Evo4 product overview warns that under-reporting torque to avoid transmission limits may cause slip or harsh shifts. Its Evo4 tuning guide discusses reference air-charge and indicated-torque headroom in a tool-specific context. Treat gearbox limits and the accuracy of reported torque as part of the system; a lower reported number is not evidence of lower actual clutch loading.
EcuTek's RaceROM product can add mode-specific torque and other targets on supported files. A custom feature's active mode and enable state must be checked before interpreting its maps. It is not evidence that every original Simos 19 ECU has the same map-switching strategy. Tool support and transmission capabilities change; confirm the exact ECU, software and current product coverage.
Practical log review
Record engine, ECU and calibration identifiers, gearbox, fuel, hardware, software and feature-file versions, active drive or map-switch mode, ambient conditions and faults. Establish a healthy, comparable baseline.
Where supported, compare accelerator and throttle positions, engine speed and gear, driver torque demand, relevant torque limits and estimated torque, air setpoint and estimate, and boost or manifold setpoint and actual. A low request with a low result is a different investigation from an unmet high request.
Review intake-flap and cam states, charge and coolant temperatures, lambda target and actual, ignition and per-cylinder knock correction, fuel pressure and gearbox intervention where available. Verify whether channels are measured, commanded, calculated or substituted and align their sample times.
Make changes only against a definition matched to the actual file, and verify affected conditions and neighbouring cells in controlled testing. A model that looks smooth on a graph does not prove it accurately represents combustion or delivered torque.
COBB's Mk8 engine monitor list shows examples of driver requested torque, clutch protection and main torque limits, modelled torque loss, flap position and air-related channels. Availability and meanings vary by monitor set and software. Its datalogging review notes that requesting too many channels can reduce sample rate on some systems; use focused, comparable traces when necessary.
Sources
COBB Mk8 Volkswagen / 8Y Audi tuning guide. Demand, limit and air-model tables for its supported products; its stock Golf R table and extrapolation are illustrative. Accessed 17 November 2026.
EcuTek EA888 Evo4 product overview and Evo4 engine tuning. Product scope, reference tables and transmission torque-reporting caution. Accessed 17 November 2026.
COBB Mk8 engine monitor list and Mk8/8Y datalogging review. Tool-specific channels and logging-rate considerations. Accessed 17 November 2026.
Open each version to inspect formatting, tables and photographs.
Revision 1: Simos 19 EA888 Evo4 torque demand and air model
This guide examines torque demand and the relationship between torque and air charge in the EA888 Evo4 examples described by COBB and EcuTek. EcuTek lists Simos 19.3 and 19.6 in its Evo4 product scope. The table names and counts below are product-specific descriptions for supported files; verify the exact ECU, software, definition and operating mode before assuming they apply.
Request, limit and delivered output
COBB's Mk8/8Y tuning guide presents a simplified chain: accelerator position contributes to driver torque demand, which is related to an air setpoint and then a boost target. Limits can act at more than one point. Driver demand, permitted torque, estimated torque, measured pressure and actual wheel output are different quantities. Changes to a request map do not prove that the engine obtained the requested air or torque.
COBB identifies Driver Clutch Torque Demand and Torque Demand From Accelerator Pedal among its editor's tables. It also describes limits dependent on gear, engine speed, ambient air density and drive mode. Those names help locate candidates in a matching COBB definition; they are not universal binary addresses. A table displayed in an editor can be inactive, effectively neutral at stock values, or active only under particular conditions. Investigate which condition and limit applies before changing it; do not remove protective limits to conceal a fault.
Torque-to-air and return model
In COBB's described strategy, the Mass Air Set Point for Torque Intervention tables relate requested torque and engine speed to an air target. Its guide describes 24 tables, split between two intake-flap groupings, with interpolation; it explicitly says the selection circumstances for individual tables are not fully defined. That count belongs to the documented COBB example, not every Simos 19 software version.
COBB identifies a corresponding set of Reference Indicated Torque tables used to check the resulting airflow, and a Maximum Cylinder Air Set Point limiter. Changing one side of the relationship without checking the corresponding references and limits can leave a mismatched model. Verify each table's axes and units, which indexed conditions are relevant, and consistency across the operating range. Indicated torque is a modelled combustion contribution before mechanical losses; it is not the same as actual measured crank or wheel torque.
COBB illustrates a stock Mk8 Golf R table whose values reach 1,500 mg/stroke in part of the displayed range, then shows an extrapolated example. That is one published calibration example, not a family-wide sensor limit, required edit or safe target. Axis rescaling and extrapolation change the region over which the controller interpolates; they require a matching definition and verification over both modified and unchanged areas. Preserve sensible low-load behaviour and compare the result against measured operation rather than treating the example's numbers as a tune.
Transmission coordination and custom features
Gearbox requests and communicated engine torque matter on automatic applications. EcuTek's Evo4 product overview warns that under-reporting torque to avoid transmission limits may cause slip or harsh shifts. Its Evo4 tuning guide discusses reference air-charge and indicated-torque headroom in a tool-specific context. Treat gearbox limits and the accuracy of reported torque as part of the system; a lower reported number is not evidence of lower actual clutch loading.
EcuTek's RaceROM product can add mode-specific torque and other targets on supported files. A custom feature's active mode and enable state must be checked before interpreting its maps. It is not evidence that every original Simos 19 ECU has the same map-switching strategy. Tool support and transmission capabilities change; confirm the exact ECU, software and current product coverage.
Practical log review
- Record engine, ECU and calibration identifiers, gearbox, fuel, hardware, software and feature-file versions, active drive or map-switch mode, ambient conditions and faults. Establish a healthy, comparable baseline.
- Where supported, compare accelerator and throttle positions, engine speed and gear, driver torque demand, relevant torque limits and estimated torque, air setpoint and estimate, and boost or manifold setpoint and actual. A low request with a low result is a different investigation from an unmet high request.
- Review intake-flap and cam states, charge and coolant temperatures, lambda target and actual, ignition and per-cylinder knock correction, fuel pressure and gearbox intervention where available. Verify whether channels are measured, commanded, calculated or substituted and align their sample times.
- Make changes only against a definition matched to the actual file, and verify affected conditions and neighbouring cells in controlled testing. A model that looks smooth on a graph does not prove it accurately represents combustion or delivered torque.
COBB's Mk8 engine monitor list shows examples of driver requested torque, clutch protection and main torque limits, modelled torque loss, flap position and air-related channels. Availability and meanings vary by monitor set and software. Its datalogging review notes that requesting too many channels can reduce sample rate on some systems; use focused, comparable traces when necessary.
Sources
Revision 1: Simos 19 EA888 Evo4 torque demand and air model
This guide examines torque demand and the relationship between torque and air charge in the EA888 Evo4 examples described by COBB and EcuTek. EcuTek lists Simos 19.3 and 19.6 in its Evo4 product scope. The table names and counts below are product-specific descriptions for supported files; verify the exact ECU, software, definition and operating mode before assuming they apply.
Request, limit and delivered output
COBB's Mk8/8Y tuning guide presents a simplified chain: accelerator position contributes to driver torque demand, which is related to an air setpoint and then a boost target. Limits can act at more than one point. Driver demand, permitted torque, estimated torque, measured pressure and actual wheel output are different quantities. Changes to a request map do not prove that the engine obtained the requested air or torque.
COBB identifies Driver Clutch Torque Demand and Torque Demand From Accelerator Pedal among its editor's tables. It also describes limits dependent on gear, engine speed, ambient air density and drive mode. Those names help locate candidates in a matching COBB definition; they are not universal binary addresses. A table displayed in an editor can be inactive, effectively neutral at stock values, or active only under particular conditions. Investigate which condition and limit applies before changing it; do not remove protective limits to conceal a fault.
Torque-to-air and return model
In COBB's described strategy, the Mass Air Set Point for Torque Intervention tables relate requested torque and engine speed to an air target. Its guide describes 24 tables, split between two intake-flap groupings, with interpolation; it explicitly says the selection circumstances for individual tables are not fully defined. That count belongs to the documented COBB example, not every Simos 19 software version.
COBB identifies a corresponding set of Reference Indicated Torque tables used to check the resulting airflow, and a Maximum Cylinder Air Set Point limiter. Changing one side of the relationship without checking the corresponding references and limits can leave a mismatched model. Verify each table's axes and units, which indexed conditions are relevant, and consistency across the operating range. Indicated torque is a modelled combustion contribution before mechanical losses; it is not the same as actual measured crank or wheel torque.
COBB illustrates a stock Mk8 Golf R table whose values reach 1,500 mg/stroke in part of the displayed range, then shows an extrapolated example. That is one published calibration example, not a family-wide sensor limit, required edit or safe target. Axis rescaling and extrapolation change the region over which the controller interpolates; they require a matching definition and verification over both modified and unchanged areas. Preserve sensible low-load behaviour and compare the result against measured operation rather than treating the example's numbers as a tune.
Transmission coordination and custom features
Gearbox requests and communicated engine torque matter on automatic applications. EcuTek's Evo4 product overview warns that under-reporting torque to avoid transmission limits may cause slip or harsh shifts. Its Evo4 tuning guide discusses reference air-charge and indicated-torque headroom in a tool-specific context. Treat gearbox limits and the accuracy of reported torque as part of the system; a lower reported number is not evidence of lower actual clutch loading.
EcuTek's RaceROM product can add mode-specific torque and other targets on supported files. A custom feature's active mode and enable state must be checked before interpreting its maps. It is not evidence that every original Simos 19 ECU has the same map-switching strategy. Tool support and transmission capabilities change; confirm the exact ECU, software and current product coverage.
Practical log review
- Record engine, ECU and calibration identifiers, gearbox, fuel, hardware, software and feature-file versions, active drive or map-switch mode, ambient conditions and faults. Establish a healthy, comparable baseline.
- Where supported, compare accelerator and throttle positions, engine speed and gear, driver torque demand, relevant torque limits and estimated torque, air setpoint and estimate, and boost or manifold setpoint and actual. A low request with a low result is a different investigation from an unmet high request.
- Review intake-flap and cam states, charge and coolant temperatures, lambda target and actual, ignition and per-cylinder knock correction, fuel pressure and gearbox intervention where available. Verify whether channels are measured, commanded, calculated or substituted and align their sample times.
- Make changes only against a definition matched to the actual file, and verify affected conditions and neighbouring cells in controlled testing. A model that looks smooth on a graph does not prove it accurately represents combustion or delivered torque.
COBB's Mk8 engine monitor list shows examples of driver requested torque, clutch protection and main torque limits, modelled torque loss, flap position and air-related channels. Availability and meanings vary by monitor set and software. Its datalogging review notes that requesting too many channels can reduce sample rate on some systems; use focused, comparable traces when necessary.
Sources