Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Reference hub
Subject
Engine ECU
Parent
Simos
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

Simos 11 is a Volkswagen Group petrol engine-management family. Škoda workshop documentation identifies it on selected naturally aspirated 1.2 MPI three-cylinder engines. Identify the controller and its exact software before selecting a definition or flashing procedure.

Applications and identification

The Škoda Fabia II, Roomster and Rapid 1.2 MPI workshop manual (August 2012, technical data pages 1–4) lists Simos 11 on CGPA, CHFA and CJLA examples from the May 2011 changeover, and on CGPB examples. The same table lists Simos 9 on earlier CGPA, CHFA and CJLA examples. It does not give a Simos 11 suffix, and the changeover month alone is not proof of the controller fitted to an individual car. Record the label, hardware, software and calibration identifiers as well as the vehicle and engine code.

In that manual, CGPA is a 1,198 cm³ three-cylinder, 12-valve, 51 kW MPI example; the table lists two lambda probes for the usual CGPA configuration and notes that the EU-2 DDK version has one upstream probe; it lists no turbocharger or camshaft adjustment. The CGPB and CHFA configurations differ. These are engine- and market-specific details, not common features of every Simos 11 application. An Engineering Mechanics 2016 paper describes a Simos 11-controlled 1,198 cm³ Škoda laboratory engine with the same 51 kW and 12-valve characteristics. Its liquid-LPG injector experiment is a research setup, not proof of a factory LPG application or of a particular ECU suffix.

Some tool catalogues associate 11.1 with 1.2 TSI badges: Microtronik's SEAT list includes both an Ibiza 1.2 12v and several 1.2 TSI entries. Conversely, SEAT SSP 136 describes its 1.2 TSI with Simos 10. Treat these as differently scoped records, not proof of ECU interchangeability or of the fitted ECU in an unspecified TSI. Simos 10 has its own overview.

Research example: liquid LPG

In a 2016 liquid-LPG injection study, researchers used a three-cylinder Škoda laboratory engine controlled by Simos 11 and compared experimental injector-end designs with and without nozzle heating. They report that rapid evaporation and cooling can cause ice at the outlet and describe nozzle heating as a measure for their research design. Their illustrated pressure traces are from the injector end, at one engine speed and several loads; they are not petrol rail-pressure targets or Simos 11 map values.

The paper describes an experimental alternative-fuel installation, not a factory Simos 11 LPG conversion or a validated calibration recipe. A change to fuel delivery involves the installed fuel system and injector characteristics as well as control software. Establish the actual equipment, fuel and supplier documentation before drawing conclusions from an experiment on another setup.

MPI baseline and fuel-system checks

Before calibration changes, investigate stored faults, ignition and misfires, intake leaks, lambda behaviour and fuel delivery. Where available, log engine speed and load, throttle position, lambda target and actual, fuel trims, ignition timing, knock correction and temperatures. Verify the logger's units, sample rate and whether each value is measured or calculated; availability varies with software and tool. A repeatable baseline helps separate a pre-existing fault from a calibration effect.

For the engines covered by the August 2012 Škoda MPI manual, its operating-pressure procedure measures at the fuel feed line with the engine running and specifies 3.92–4.20 bar using its stated gauge and procedure (pages 120–121 in the Czech edition). This is a workshop test specification for that documented fuel system, not a universal Simos 11 target or a tuning recommendation. Follow the applicable current service instructions for the individual vehicle and gauge connection. The manual also describes checking injector leakage, spray pattern and delivered quantity under controlled test conditions (pages 155–157 in the Czech edition), which can help explain mixture problems before altering fuel maps.

Throttle adaptation after ECU replacement

The English Škoda 1.2 MPI workshop manual, edition 08.2012, describes throttle control unit J338 in a component group that includes CGPA, CGPB and CJLA. It says to carry out adaptation with the vehicle diagnostic tester when replacing the engine control unit. Its component overview also identifies intake-manifold pressure and temperature senders as inputs in this engine group. The manual covers engines with both Simos 9 and Simos 11: use the actual vehicle identification and current guided procedure, rather than treating this as a universal post-flash instruction or assuming every adaptation should be reset after tuning.

Record existing diagnostic faults and relevant operating conditions before performing a service adaptation. If the throttle does not adapt or the engine behaves abnormally, investigate the fault using the applicable diagnostic procedure before attributing it to a calibration map.

Calibration and reading

Map definitions and their axes, units and scaling must match the exact software. The sources here do not establish a universal Simos 11 torque or fuel map layout, safe numerical increases, or transferable addresses. Avoid assuming a pressure control strategy from a different engine or copying definitions merely because the ECU family name is similar.

Microtronik's Simos 11.1 product page lists OBD read, virtual read and write for its tool. That is a product-specific coverage statement; check current support, preparation and recovery for the actual ECU and software. A virtual original need not contain the vehicle's current calibration, and a calibration read is not necessarily a complete memory image. Confirm the original file scope, checksum handling, stable power and recovery method before writing.

Specific Simos 11.1 identification and map-listing example

Two public Polo CGPB diagnostic scans illustrate why the whole ECU identification matters. One owner-posted scan reports software part number 03E 906 019 M, hardware 03E 906 019 B and component SIMOS11.1 H03 9877. A separate owner-posted scan reports the same software and hardware part numbers, but component version H03 8949. These are individual community-reported records, not proof that the files are interchangeable. Record the actual part numbers, hardware and complete component/software version, coding and the provenance of the ECU read; do not identify a definition from the vehicle badge or a partial part number alone.

For a different research lead, Auto-Remap's 03E906019M 9877 listing advertises a Polo Simos 11.1 CSV map export with 17 labels. The public groups include nine standard-condition torque requests, calculated, optimal and maximum-torque labels, two spark-base labels, two injection labels and requested engine load. The names describe the seller's export; the public list does not disclose the other maps' sizes, axes or addresses, and a name alone does not prove the map's identity, active conditions or effect. Its identification resembles the first scan, but that does not establish that the sold file is a match for that car or any other ECU.

The seller also displays one example called Torque request during standard condition, with a 12-by-12 table, accelerator pedal percentage across its columns, engine speed in rpm down its rows and percentage values. The visible speed axis contains two separate rows both labelled 1,200 rpm but with different values. The page does not explain that duplication, whether rounding is involved, the percentage reference or the actual control conditions. Treat the display as a seller-provided example requiring verification in the underlying file, not a validated pedal map or a tuning target. Do not infer interpolation or modify an axis from the web rendering alone.

The seller describes the export as a CSV rather than factory DAMOS/A2L and states that its supplied original is not a full backup and excludes EEPROM. Confirm exact file identity, data boundaries, axis values, units and function against the actual read before any controlled comparison. The supplier's list is not evidence that every listed map requires alteration or that a particular numerical change is safe. The baseline, fault and naturally aspirated MPI checks above remain essential.

Sources