Tuning Wiki
Applies to

Check the hardware and software limits stated in this article.

This page examines boost requests and electronic wastegate control in the supported EA888 Evo4 examples documented by COBB and EcuTek. Volkswagen identifies Simos 19.6 in its North American EA888 Evo4 GTI, Golf R, Atlas and Arteon examples. EcuTek lists both 19.3 and 19.6 in its Evo4 product scope. The features and monitor names below belong to the cited products and compatible software; they must not be assumed to exist or behave identically in every Simos 19 calibration.

Demand, limit and boost response

COBB's Mk8/8Y tuning guide describes a simplified path from accelerator demand through driver torque demand and an air-mass setpoint to a required boost target. It also notes limits at multiple points. This is useful orientation for the guide's supported cars, not a complete map-by-map execution trace. A requested torque, a permitted limit, an air target and an achieved pressure are different values.

The COBB example names Maximum Intake Manifold Pressure Set Point and Manifold Pressure Set Point Limit as pressure-related limiting tables. Their presence in an editor does not prove either is active in every operating condition. The guide also describes turbocharger modelling, diagnosis and protection. Pressure and speed limits, temperature corrections, an external torque request and hardware condition may interact; a pressure deficit alone does not establish which one is responsible.

Electronic wastegate and RaceROM override

COBB describes electronically actuated wastegate control with feedback on its supported Mk8/8Y vehicles. Its guide identifies proportional, integral and derivative control terms and cautions that calibration requires understanding the feedback system. An overshoot, oscillation or slow response is evidence to investigate, not proof that one feedback term must be changed. Compare comparable operating conditions, inspect the actuator and air system, and establish the active control mode before changing a control table.

EcuTek's Evo4 RaceROM v1 documentation describes an optional simplified wastegate function. When enabled in its documented feature file, a base wastegate-duty map replaces the base contribution generated by the original flow functions. This is a custom control feature, not an assertion that every stock ECU uses the same map. EcuTek also describes optional blending of cold- and hot-ambient base maps. Check whether the feature is enabled, the selected mode and the exact software before interpreting a table or log.

RaceROM ambient-temperature blending example

In EcuTek’s documented simplified wastegate feature, the optional ambient-temperature blend determines the proportions of the Base Wastegate Duty [Cold ambient] and Base Wastegate Duty [Hot ambient] maps. Its guide describes a blend value of 0 as the cold map alone and 1 as the hot map alone, with intermediate values blending the two. For example, a blend of 0.25 uses 75% of the cold-map output and 25% of the hot-map output at the relevant operating point. This explains the tool’s stated blending convention; it is not a recommended duty cycle or temperature threshold. EcuTek Evo4 RaceROM v1.

When comparing response in different weather, record ambient temperature, active feature and blend configuration as well as pressure target and actual, wastegate command and feedback. EcuTek also describes separate petrol and ethanol base-map blending. Check the actual feature version and active inputs before attributing a change to one map: the blended base contribution does not by itself establish final actuator position, pressure or closed-loop correction.

Pressure ceilings and units

In that RaceROM guide, per-mode boost target max maps are ceilings on the requested boost, not fixed pressure commands. EcuTek specifies that these particular maps use gauge pressure in hPa. The ECU can request less than the ceiling, and actual pressure can differ from the request. A boost limit, the requested pressure and the reported measured or modelled pressure should therefore be compared as separate quantities.

Gauge pressure is relative to ambient pressure; absolute pressure includes ambient. For the same location and conditions, absolute pressure equals gauge pressure plus ambient pressure. Do not add or subtract ambient blindly: first verify the sensor location, logger's units and reference, and whether its quantity is measured or calculated. Pressure upstream of the throttle, manifold pressure and compressor pressure ratio are not interchangeable. EcuTek notes that its target pressure ratio can differ from boost target because it accounts for atmospheric conditions and intake pressure losses.

Sensor scaling and turbo-speed data

EcuTek’s Evo4 engine tuning guide distinguishes the pre-throttle boost or PUT/TMAP sensor from the manifold MAP sensor. Its Simos 19 examples also describe SENT sensor configuration and a frequency-to-speed scaling map for turbo speed sensors. These are descriptions of its supported software; they do not establish which sensors or maps are fitted or available on every vehicle.

When fitting a different pressure sensor, identify its location, electrical output, pressure range and absolute or gauge reference, and match its transfer function to the compatible ECU input and calibration. Compare the reported pressure with a suitable independent reference at appropriate points across the working range. An ignition-on, engine-off comparison with ambient can help check the low end, but agreement at one point does not establish correct scaling across the range. A dashboard reading alone does not prove that the ECU’s control signal is scaled correctly.

COBB’s Mk8 monitor list labels turbine speed as modelled in its pre-CCF monitor set. Its separate fast-logging list names Turbo Shaft Speed and Maximum Turbo Speed SP; those names alone do not establish whether a particular vehicle has a physical speed sensor or whether a value is measured or calculated. Confirm the hardware, signal definition and scaling before interpreting a speed trace, and distinguish a speed setpoint or limit from an actual reading. Use limits appropriate to the identified turbo and application.

Evidence from a log

Record the vehicle, exact ECU software, tool and feature-file versions, turbo and intake hardware, fuel, ambient conditions, selected drive or map-switch mode, gear and the nature of the event. Establish a baseline and inspect fault codes before attributing a change to calibration. Where the ECU and logger support suitable signals, compare:

  • Engine speed, accelerator pedal and throttle position, so the pressure trace has a load and driver-request context.
  • Torque demand, relevant reported limits, air-mass setpoint and estimated air charge, distinguishing calculated quantities from direct measurements.
  • Boost or manifold pressure setpoint and actual, ambient pressure, and wastegate command and feedback where available; verify the pressure reference and sensor location.
  • Lambda setpoint and actual, fuel pressure, ignition and individual-cylinder knock correction, temperatures and any available intervention flags.

COBB's Mk8 engine monitor list illustrates separate boost pressure and setpoint, manifold pressure and setpoint, air-mass, torque-limit and wastegate channels. Its list also labels turbine speed as modelled in one monitor set. Availability, units and definitions depend on monitor set, calibration and tool. COBB's datalogging review notes that on some systems requesting too many channels slows sampling; use a focused set and examine the time between samples.

If the logged setpoint is already low, investigate demand, operating mode and applicable limits before treating the wastegate as the cause. If the setpoint is high but the actual value is lower, investigate response, leaks, mechanical and control faults and interventions; the difference does not uniquely identify a component. A change in the observed limit or correction may explain the result only after the timing and measurement are verified. Do not disable diagnostic or protective functions merely to conceal a mismatch.

A published boost-log example

RacingLine release RSR-2023-07A v1.03 includes a simplified bFlash log for its Golf 8 R on a fourth-gear dynamometer pull. It calls this a stock-software example but says the car had its R600 intake fitted. The document covers selected EA888 Gen4 Continental-turbo applications and lists specific ECU IDs across Simos 19.3/19.6; it does not assign every listed ID to an individual ECU variant. Its later Stage 1+ example specifies the supplier’s intake and intercooler. Those hardware and software conditions are part of the example, not requirements or results for every tune.

In the stock-software table, at 1,743 rpm the reported boost setpoint is 1,843 mbar and actual is 1,511 mbar, a difference of 332 mbar; at 2,486 rpm they are 2,238 and 2,249 mbar respectively. These are two samples from one pull, not steady-state thresholds or targets. Early in a rising-load event, the pressure difference can change as the air system responds. The examples do not establish the pressure channel’s sensor location or prove an actuator or calibration fault. Check the time history, pressure reference, throttle, demand and wastegate signal before diagnosing a mismatch.

The same table includes lambda, rail pressure, intake temperature, ignition and four knock channels alongside the pressure values. These contextual values help frame a comparison but are reported logger outputs, not a substitute for verified channel definitions or independent torque measurement. Reproduce conditions as closely as practical and examine the full trace rather than selecting isolated cells. RacingLine’s published results and calibration are supplier-specific; the document does not establish universal safe pressure, mixture or ignition values.

Sources