SEAT's Self-Study Programme 158 describes a third-generation 1.8 TSI installation using Simos 12 with both direct injection (FSI) and intake-port injection (MPI). Its mode and fault descriptions apply to that documented installation; an ECU family name alone does not establish that another engine has port injectors or uses the same strategy.
Identify the system before interpreting a log
Audi's eSelf-Study Programme 920243 lists Simos 12 on its North American CNSB, CNTA and CYFB examples but identifies those examples as having direct injection without intake-manifold injectors. A log or calibration from that equipment cannot be assumed to contain the same active MPI functions as the SEAT example. Record the engine, market, installed injectors, ECU hardware and calibration identifiers, transmission, fuel and any modifications.
In the SEAT text, “double injection” refers to the engine having FSI and MPI systems. It also describes operating conditions with two direct injection events in a cycle. These are different uses of the word “double”; a trace reporting multiple direct pulses does not by itself prove that port injectors are active.
Operating modes in the SEAT example
SEAT says the described installation uses FSI and MPI separately, with the chosen mode depending on engine state and coolant temperature. The ECU considers coolant temperature, pedal and engine speed, among the signals listed in the programme. Its table describes:
- Engine start in FSI mode, with three direct injections during compression in the stated example.
- Cold idle and part-load using direct injection; the table describes intake- and compression-stroke direct events.
- Warm idle and part-load using one MPI event; higher load returning to FSI, with the table distinguishing two direct events at high load from one at high load and high speed.
The table uses 45 °C as the coolant-temperature division in this illustration. That is a training example for the documented strategy, not a universal transition setting, a recommended calibration value or proof of the mode on a particular car. Actual mode selection and diagnostic channels must be verified against the current ECU software and operating conditions. SEAT SSP 158, double-injection section.
While the SEAT example is running in MPI mode, SEAT describes periodically returning briefly to FSI to flush the direct-injector openings. A brief mode change or direct-injection event during an otherwise port-injected period can therefore be intentional; it does not by itself demonstrate a fault. Conversely, a requested mode is not proof that every injector delivered correctly.
Pressure sensors and fallback
SEAT identifies G410 in the low-pressure fuel distribution line and G247 in the high-pressure rail. For the stated system, its sensor-loss descriptions say a missing G410 signal causes an FSI fallback and a missing G247 signal causes an MPI fallback. The programme also describes an operational-mode fallback if one injection system fails, with reduced performance possible for an FSI fault. These are descriptions of particular faults and this installation, not a promise that a car can safely be driven with a fuel-system fault or that every Simos 12 behaves identically.
With a suitable diagnostic tool, investigate the stored fault, signal, wiring and physical fuel supply using the correct service procedure. Where available and properly defined, compare requested and reported pressures for both circuits, injection mode and pulse channels, lambda target and actual, fuel corrections, rpm, load, pedal and coolant temperature. Confirm channel units, pressure reference, sampling and whether the displayed value is measured, commanded or substituted. A stable or plausible reported number does not establish a functioning sensor if the ECU is using a fallback.
Calibration and validation
Identify the actual calibration and file before changing fuel-related maps. Injector data, operating-mode windows, injection timing and mixture targets depend on the hardware and software. A richer commanded lambda, higher pressure request or changed mode does not by itself establish adequate delivery or an improvement. Check the available fuel system, fault status and the relevant transition in comparable logs before diagnosing a flat power result or altering a calibration. A software definition's label is not proof of the map's function.
TuningBot's Simos 12 guide makes the same broader distinction between a requested value, an intervention and an achieved result. It is general identification and diagnostic guidance; it does not publish a verified Simos 12 injection-mode map or universal settings.
Separate Simos 12.2 definition example: fuel-pressure selection
A publicly indexed archive labelled for a Jetta 2.0 TSI contains an A2L file named SC2C3031_Ce_ro.a2l. Its header describes an enriched Simos 12.2 EA888 project, structure C30, with EPK SC2C300. These are claims in the file; its origin, rights, completeness and match to a specific ECU or the accompanying HEX are not verified. This is a separate 12.2 research example, not a definition for the SEAT 1.8 engine above.
In that definition, id_fup_sp_sel_cmb_mod is described as an index for choosing a basic fuel-pressure setpoint table according to the requested combustion mode. Its axis references include a combustion-mode index and coolant temperature. The file also defines multiple ip_fup_sp_bas_sel tables; the first two refer to engine speed and a mass-fuel-flow setpoint used for fuel-pressure determination. These labels suggest a reason to investigate mode and table selection together, but do not show which table is selected at a given time, actual setpoints or physical rail pressure. Verify the actual binary, software, channel definitions and behaviour before interpreting or changing a map.
The same file also illustrates why labels and axes must be checked separately: the description of ip_fup_sp_max refers to TCO, while its axis refers to tfu, which the file’s measurement description calls fuel temperature. The file separately describes tco as coolant temperature. The cause of that difference is unknown; neither interpretation should be assumed correct from this A2L alone. Obtain a verified definition and compare the actual operating data. The inspected A2L’s SHA-256 was 7b5194ebeac25329b69ec0880251fc9e9ce50e4a795b72fd8608f6314c052fad on 17 November 2026; the hash identifies the examined text, not its authenticity or vehicle fit.
Sources
- SEAT Self-Study Programme 158: 1.8 TSI third generation, Continental Simos 12, French edition, sensor and double-injection sections. Mode table, flushing and sensor-loss descriptions for its documented installation. Accessed 17 November 2026.
- Audi eSelf-Study Programme 920243: 1.8L and 2.0L Third Generation EA888 Engines. North American CNSB, CNTA and CYFB equipment examples, each listed with Simos 12. Accessed 17 November 2026.
- TuningBot: Simos 12 identification and calibration checks. General baseline, requested-versus-achieved and logging guidance. Accessed 17 November 2026.