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 9.1 is a Siemens/Continental petrol engine-management variant. Volkswagen and SEAT training material identify it on particular 1.2-litre three-cylinder engines with intake-manifold injection. The examples below are applications documented by those sources, not a complete fitment list.

Documented applications

Volkswagen SSP 447, The Polo 2011, identifies Simos 9.1 on the CJLA 1.2-litre, 55 kW three-cylinder petrol engine. It describes intake-manifold injection, individual ignition coils and lambda-controlled exhaust treatment. The figures and engine arrangement are specific to that documented Polo application.

SEAT's Ibiza 2008 self-study programme 120 identifies Simos 9.1 on the BZG 1.2-litre 12-valve engine, rated at 51 kW in its example. See the wiki's three-cylinder engine reference for further engine-code context. Do not identify an ECU by engine size, model or year alone: record its part number, hardware and software identification and the installed fuel and emission equipment.

Two commercial Polo 1.2 file listings use the identifier 03D906023 but list different software strings, S912010000000 and S912016000000. These are sellers' identification claims, not independently verified files or definitions. They illustrate why a common ECU number alone is not enough to establish the software, maps or interchangeability; check the identifier and file actually read.

Diagnosis and calibration

The VW and SEAT examples are naturally aspirated petrol engines, so a turbo boost-control procedure is not a useful assumption for them. Check fault codes, engine mechanical condition, intake and exhaust leaks, fuel delivery, ignition and oxygen-sensor operation before changing a calibration. Investigate a fault or discrepancy rather than trying to mask it by raising a limit.

Where the ECU and diagnostic tool support them, record engine speed, load, throttle and pedal position, lambda feedback and fuel trims, ignition timing, knock correction and coolant and intake-air temperature. Confirm units and whether the value is measured, commanded or calculated. A calibration definition must match the actual software, and each map's axes, scale and role must be verified. The available factory material establishes engine application and hardware; it does not provide validated map addresses or a performance tuning recipe.

A file-specific pedal request example

Auto-Remap’s Fabia 1.2 64 hp listing identifies a Simos 9.1 file as 03D906023 5415 and advertises a 12-map WinOLS CSV export. The seller labels three maps as torque requests in standard conditions, one as optimal engine torque, two as requested engine load, two as airflow through the throttle, two as injection and two as base spark. These are seller-supplied names for that listing, not verified factory names or evidence that the same maps, counts or addresses apply to another version. The two listing pages were reviewed through indexed text; direct requests returned HTTP 403 when checked. Their identifiers also appear in the seller’s Fabia map-pack catalogue.

The public page displays one table labelled Torque request during standard condition with 16 pedal-percentage columns and 12 engine-speed rows. The seller labels the output as a percentage; at its displayed 45.02% pedal and 1,504 rpm the cell reads 73.0%. The listing does not establish what the output percentage is referenced to, the conditions under which this table is selected, or whether the labelled axis and scaling are correct for a real vehicle. It is an illustration of the seller’s interpretation, not a measured torque, a safe tuning target or a value to copy.

The seller’s separate 03E906023Q 4485 listing advertises the same category and map-name counts and displays a similarly labelled 16-by-12 sample. At 800 rpm and 3.91% pedal its displayed value is 23.0%, while the 5415 page shows 28.7% at that same displayed intersection. Identical names and counts do not establish matching axes, offsets, values, software or interchangeability between the two files. The seller describes a CSV definition export without tuned values and states that its accompanying original excludes EEPROM and is not a full backup. Confirm the actual file and a recovery route, then independently verify map boundaries, axes, units and use against the identified software before making a controlled change.

A public file and definition research lead

A public TorqueCloud directory lists a 512 KB file named Simos91_wellon_read.bin alongside a WinOLS .kp file whose name includes S912018400000. A separate commercial catalogue entry associates that software string with a Fabia Simos 9.1 example. The public directory does not document the source, usage rights, software identity of the BIN, map contents or how the files were produced; co-location and a similar identifier are not evidence that they match each other or the vehicle in hand.

Treat these as leads for further investigation, not a validated factory definition or a ready-to-flash file. Identify the actual controller, verify the source and applicable permissions, and independently validate file format, provenance, map boundaries and scaling. A physical read, an editor project and a complete recovery image are separate things; the directory listing alone does not establish what any file contains.

Reading and writing

The Dimsport New Genius application list names a Simos 9.1 K-line read and identification entry for that product. It is a historical product-coverage statement, not evidence that all Simos 9.1 units can be read or written by all tools. Confirm the current tool, connection, file type, checksum and recovery procedure for the specific ECU before programming; keep an original read suitable for the selected tool.

The PCMflash manual, module 17, separately lists a K-line calibration protocol for Simos 9.1 1.2 BME/BZG/CGPA with a stated 512 KB file and read, write and checksum check/correction. This is specific to that tool and protocol, not evidence of coverage for every Simos 9.1 revision or of EEPROM or complete recovery-data access. Confirm current support and file scope for the identified controller. A checksum can establish file integrity under the supported algorithm; it does not prove the calibration matches the ECU or is suitable for the engine.

For throttle alignment, response and idle investigation, see Simos 9.1 1.2 MPI throttle adaptation and response diagnosis.

Sources