EcuTek documents auxiliary multi-port injection (MPI) and ethanol blending for its EA888 Evo4 RaceROM software. This guide explains the relationships among the added hardware, combustion modes, fuel split and logging for supported Simos 19.3 and 19.6 applications. The functions described are EcuTek RaceROM features and software-specific configuration, not evidence that every Simos 19 ECU has MPI hardware or an enabled flex-fuel feature.
EcuTek's Evo4 product overview names both ECU variants in its tool scope. Check the exact vehicle, ECU software, RaceROM version and available features with the supplier before applying any of the following. The Simos 19 family page explains the general torque and air model.
Start with the actual fuel system
Volkswagen's North American EA888 Evo4 training programme describes direct fuel injection and identifies Simos 19.6 for its GTI, Atlas, Arteon and Golf R examples. It does not establish the injection equipment of every market or every 19.3 vehicle. EcuTek describes adding MPI to supported Mk8 vehicles that do not have it; inspect the specific vehicle rather than assuming that its ECU variant establishes its hardware.
Direct injectors deliver fuel into the cylinders. An added MPI system uses port injectors to supply a proportion of the fuel upstream of the intake valves. EcuTek's Evo4 MPI guide lists port injectors, an MPI-capable manifold, a rail and low-pressure plumbing, a pressure sensor and a suitable wiring loom among the additional parts. Verify actual fitment, injector flow data, pressure reference, wiring and the capability of both fuel supplies for the chosen fuel and load.
Why hardware and combustion mode both matter
Physical injectors alone do not establish when or how much fuel they will deliver. EcuTek describes selecting a combustion mode that permits the required injection pulses, configuring the load and engine-speed ranges where that mode can be requested, and ensuring relevant mode inhibits and pulse settings allow scheduling. Its RaceROM MPI enable must correspond to the intended combustion mode. These are conditions in EcuTek's described workflow; do not copy numeric mode selections or airflow thresholds into an unrelated file without verifying the available software and operation.
Injector configuration and the MPI/direct-injection split must then agree with the installed hardware. The split is a commanded allocation of fuel between systems: confirm actual operation with supported channels and mixture feedback, rather than assuming a changed split map proves both sets of injectors are operating. Incorrect injector characterization or a fuel leak can produce misleading corrections and an unsafe mixture. Do not treat a single lambda value as proof that every cylinder or injector is healthy.
Example: how a combustion mode is selected
In EcuTek’s Evo4 MPI example, the coolant-temperature request map selects the operating-point 5 standard map once coolant temperature exceeds 60 °C. That map then requests a combustion mode across load and RPM. The guide gives modes 2 and 9 as examples that can support multiple injection pulses, provided the relevant airflow limit, inhibits, pulse settings and RaceROM MPI enable also permit operation. The temperature, mode numbers and thresholds are descriptions of that documented setup, not values to copy into another calibration. Check the selected operating point and active mode in the actual software before diagnosing why a requested split is absent.
EcuTek’s engine tuning guide also identifies injector size, dead times and pressure corrections as part of port-injector characterisation. Match these to the fitted injectors and fuel system; a nominal flow-rate value by itself does not define their behaviour across voltage and operating pressure.
SCQ110 definition: pressure and knock inhibit labels
A separately indexed SCQ110 A2L describes ip_fup_efp_thd as a fuel-pressure threshold to inhibit MPI. One axis names n; the other declares NO_INPUT_QUANTITY. It separately describes ip_iga_knk_mpi_thd as an ignition-angle threshold to inhibit MPI operation due to knock, with inputs n and tqi_req_cmb. These are separate labels and inputs; they do not establish the numeric thresholds, exact source of every signal, operating logic or which condition is active in a log.
A third entry, ip_fup_mplh_thd, is described as a fuel-pressure threshold to inhibit multiple direct-injection events. Both its axis inputs are explicitly NO_INPUT_QUANTITY; the axis-point names do not prove the actual signals. Multiple DI pulses and MPI are distinct: the file's DI threshold must not be treated as a port-injector enable or as a substitute for a verified combustion-mode definition.
The inspected text describes itself as an enriched Audi/VW Simos 19.3 LK3evo project with EPK VWSCQ110. The inspected file was 60,057,673 bytes, SHA-256 6473bf25107af882ebb3eea6cb0d57c223b2d005451df031ab546bfd1487f45e. Origin, rights, authenticity, ECU match and runtime behaviour are unverified. These file-specific labels are independent of EcuTek's example above and do not prove its feature's selection or any vehicle's hardware. Match and validate the exact software and supported signals before interpreting a missing MPI event; investigate pressure, mode, knock and faults rather than suppressing an inhibit.
Fuel pressure and sensor scaling
EcuTek's MPI guide describes configuring the low-pressure fuel sensor type and its scaling, including whether its pressure reference is gauge or absolute. A pressure channel with the wrong type, units or reference can appear plausible while misleading the control or diagnosis. Match the scaling to the actual sensor and verify its reading using an appropriate known reference and the supplier's procedure.
Separate low-pressure supply from the direct-injection high-pressure rail. The COBB Mk8/8Y guide points out that a low-pressure supply shortfall can contribute to a rail-pressure dip; it does not mean every dip has that cause. Compare pressure setpoints and reported actual values, supply and pump behaviour, operating conditions and fuel-system condition before deciding which component or calibration is limiting. VW's 350 bar high-pressure figure in its documented factory system is not a universal tuning target.
Two supplier examples of ethanol and fuel supply
In its Evo4 RaceROM guide, EcuTek reports that on one development car with a hybrid turbo, intake, stock injectors and a COBB flex-fuel kit, low-side pressure began to fall at about 30% ethanol. The company says the stock low-pressure pump appeared to run out of flow. The guide does not publish the complete log, fuel-flow measurement or all test conditions, so this is a supplier observation for that build, not a proven failure cause or a universal ethanol limit.
Separately, APR's Mk8 GTI Stage 3 OEM-turbo announcement advertises an E60–E85 file for its specified larger Golf R/S3 Continental turbo package and states that its factory fuelling system is retained. That is APR's claim for its own hardware and calibration, not independent evidence that every stock pump can support another build. The two descriptions have different turbos and calibrations and do not establish a common safe blend, fuel-flow limit or comparable test conditions.
For the actual vehicle, establish the fuel and tune, injector and pump hardware, and measure supported low-side and rail-pressure request and actual values together with lambda and operating conditions. Investigate pressure loss and fuel delivery before increasing demand. An ethanol sensor or a published stage label does not by itself demonstrate adequate pump capacity.
Fixed blend or measured ethanol content
EcuTek describes a fixed ethanol value selected by map-switch mode and a CAN-based ethanol sensor input. A fixed value is an assumed blend; it does not measure fuel in the tank or automatically follow a change at the pump. A sensor-based system requires suitable hardware, wiring and configuration. Verify the installed sensor's signal, scaling and communication with the specific tool, including expected behaviour if the input fails or becomes invalid.
In EcuTek's Evo4 RaceROM guide, fuel-quantity corrections use factory alternative-fuel code, while RaceROM provides ethanol-dependent target or blend functions for items including ignition, boost limit, lambda and, when MPI is configured, injection split. Each function's availability and calibration depend on the feature file and ECU software. A higher ethanol reading alone does not establish that the hardware can supply the required fuel.
CAN ethanol input configuration
For the documented Evo4 RaceROM v1, EcuTek distinguishes preset CAN devices from custom inputs. Its custom-device setup identifies the CAN message ID and 11-bit or extended 29-bit format, then configures each channel’s usage, start byte, data format, multiplier and offset; a mask can select particular bits. The guide describes applying the offset after multiplication. The correct settings depend on the transmitting device’s actual message specification and cannot be inferred from an ethanol percentage displayed by another instrument.
EcuTek notes that much of the Mk8 network uses CAN FD, so an ordinary CAN device may not be compatible with every connection. Its guide describes ethanol content as the operating input connected to a function in that version, while other custom channels may be used for logging. Confirm the selected network, device and feature-file compatibility with the supplier, then verify the received ethanol content against a known fuel sample and check how the configured system behaves if input is absent or invalid. A plausible displayed number or a working logged channel alone does not prove that it is selected as the active flex-fuel input.
How the documented blend affects a target
For its Evo4 RaceROM feature, EcuTek describes blending a normal mode-specific lambda target with a flex-fuel lambda target according to the configured blend map. A blend value is a weight, not automatically the measured ethanol percentage. For a purely illustrative calculation, if the normal target were 1.00, the flex target 0.80 and the blend weight 0.25, the weighted target would be 0.95. Those numbers illustrate the arithmetic and are not calibration recommendations.
Boost-limit and MPI/direct-injection split blending are described separately in that guide. Check each function’s own map, blend and enable conditions rather than assuming that the same proportion applies to every output. A blended boost limit remains a ceiling, while a calculated lambda target is a request; neither demonstrates actual pressure, mixture or safe operation. Verify the specific feature version, sensor input and measured feedback under the relevant operating conditions.
The same guide describes an ethanol-content hold under specified RPM and air-charge conditions, intended to address readings affected by flow in some sensor installations. During a hold the displayed or used value may deliberately stop updating; check the configured threshold and operating state before concluding the sensor has failed. Verify actual blend and sensor behaviour after changes rather than assuming the stored value represents every operating condition.
Reviewing a log
- Document fuel and blend, ECU and RaceROM version, injector and pump hardware, pressure-sensor type, fuel-pressure reference and active map-switch mode. Establish a fault-free baseline.
- Where available, record ethanol source and value, operating mode, engine speed and load, low-pressure supply and high-pressure rail target and actual, fuel-pump command, lambda target and actual, fuel corrections, ignition and knock correction. Review injection mode, pulse and split channels only where the logger defines and supports them.
- Read the trace in context: a requested target can be achieved, limited, delayed or missed. Check units, whether a channel is measured or modelled, sample timing and the conditions under which it updates. Investigate a pressure drop, mixture error, misfire or implausible sensor value before increasing demand.
COBB's Mk8 monitor list illustrates separate low- and high-pressure, fuel correction, injection and lambda channels. Channel names and availability are specific to its platform and calibration; do not assume the same labels or meanings in EcuTek. Its datalogging review notes that requesting many channels can slow logging on some platforms.
Sources
- EcuTek VW AG EA888 Evo4 product overview. Simos 19.3 and 19.6 product scope and RaceROM features; exact software compatibility must be confirmed. Accessed 17 November 2026.
- EcuTek VW AG EA888 Evo4 MPI guide. Additional hardware, combustion mode, sensor and injector configuration for its documented workflow. Accessed 17 November 2026.
- EcuTek VW AG EA888 Evo4 RaceROM v1. Fixed and sensor ethanol inputs, target blending, MPI split and ethanol hold. Accessed 17 November 2026.
- Volkswagen SSP 822223: 2.0L EA888 Evo4 Engine, Volkswagen Group of America, version 1.3, November 2022. Factory direct-injection system on its stated Simos 19.6 applications. Accessed 17 November 2026.
- COBB Mk8/8Y tuning guide, Mk8 engine monitor list and datalogging review. Tool-specific pressure, channel and log context. Accessed 17 November 2026.