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 6 is a Siemens petrol engine-management family. Audi identifies it on a documented naturally aspirated 3.2 FSI V6 A6; individual suffixes and software must be verified on the controller. A direct-injection or 3.2-litre Audi does not by itself identify the ECU.

Applications and identification

Audi's August 2005 A6 3.2 FSI technical data specifies Siemens Simos 6, a 3,123 cm³ V6 with petrol direct injection, electronically controlled throttle, cylinder-selective lambda and adaptive knock control. It describes a manifold-pressure-based system and a two-stage intake manifold with charge-motion flaps. The sheet identifies the family, not a 6.2 or 6.3 suffix.

Audi Self-Study Programme 325 describes the 2005 A6 3.2 FSI engine AUK and its Siemens management. Separately, a Prins LPG installation document identifies a petrol ECU as Simos 6.2 A for its AUK application. That is a supplier's specific installation example, not a complete factory fitment list or a universal pinout.

Record the actual ECU label and diagnostic identification, hardware and software numbers, calibration, engine, gearbox and installed fuel system before choosing a file. Audi's later SSP 411 compares its new Simos 8.1 system with “Simos 6D2” on a previous 3.2 V6 FSI. It does not establish that every later 3.2 uses Simos 6 or that its calibration is interchangeable with the earlier one.

Air and fuel system on the documented A6 engine

SSP 325 describes pressure-and-engine-speed-based air-mass determination, continuous inlet and exhaust camshaft adjustment, a two-position intake system and flap-position monitoring on its 3.2 FSI example. Airflow, throttle and manifold or charge-motion flap behaviour should be interpreted for the exact engine and operating mode; do not apply a supercharged Simos 8 wastegate or bypass procedure to this naturally aspirated example.

The same programme describes a demand-controlled low-pressure fuel system and a separate direct-injection high-pressure system. On its example, low-pressure sensor G410 and high-pressure sensor G247 provide different measurements, and the high-pressure pump's metering valve N290 controls the quantity supplied. A low rail-pressure reading alone does not prove that the high-pressure pump is the cause. Compare requests, measurements, the low-pressure supply and fault information using the actual vehicle's current diagnostic procedure. Audi SSP 325, 3.2 FSI fuel system and management.

For the separate variable-length and charge-motion systems, and Audi’s scoped vacuum-leak bulletin, see Simos 6 3.2 FSI intake flaps and vacuum diagnosis.

Calibration and diagnosis

Establish a fault-free mechanical baseline and record fuel, modifications and calibration identifiers. Where supported by the exact ECU and logger, compare engine speed, pedal and throttle position, intake-manifold pressure and temperature, camshaft requested and actual positions, manifold-flap state, lambda and fuel corrections for each bank, ignition and individual-cylinder knock corrections, and requested and actual fuel pressures. Verify the names, units and whether values are measured, commanded or substituted before drawing a conclusion.

For a naturally aspirated engine, manifold pressure and air charge are still useful for diagnosing restrictions and load calculation, but a turbo boost target is not a feature established by the cited A6 specification. Cam timing, intake switching, fuel delivery and ignition can all affect the result. Faults, hardware changes and calibration changes need to be distinguished in comparable logs; a torque request or estimated value is not an independent measurement of output.

Public sources used here establish system operation and some tool coverage, but not a validated map sequence, offsets or universal ignition and fuelling settings. Match the definition, scaling and axes to the exact software and confirm map behaviour; do not transfer Simos 8 or Simos 12 definitions by name alone.

Simos 6 OBD strategy: misfire and mixture adaptation

A rehosted document entitled Siemens “Simos 6” OBD System Strategy describes misfire detection and fuel correction in a Simos 6 strategy. Its public copy does not identify an exact ECU part number, software revision or vehicle application; it is useful system context, not proof that the following behaviour or channels apply unchanged to the A6 example above.

The document describes estimating engine roughness from the time taken by crankshaft segments and comparing it with an operating-point threshold. The base threshold depends on load and engine speed, with a coolant-temperature correction during warm-up. It also describes adapting sensor-wheel tolerances during fuel cut in defined speed ranges, and says some multiple-misfire patterns can be difficult to distinguish from normal rotation. A scanner displaying no misfire is therefore not conclusive proof of good combustion, particularly if the monitor was not operating or the conditions differed.

In the documented strategy, an emissions-related counter uses 1,000 crankshaft revolutions, while a separate catalyst-damage evaluation uses weighted events over 200 revolutions. These are ECU monitor intervals, not necessarily the refresh period, units or reset behaviour of a scan tool's displayed counters. The source describes a flashing malfunction indicator for the catalyst-damaging condition. If an engine misfires or the warning flashes, avoid continued loaded testing and diagnose the fault using the vehicle-specific repair instructions.

The same source describes a preliminary mixture calculation corrected using the upstream oxygen sensor, and adaptation in two load/speed regions: an additive correction in one and a multiplicative correction in the other. Each is learned in its respective region but influences the wider operating range. It also describes a downstream-sensor trim loop. Compare the actual tool's documented bank, units and adaptation conditions before interpreting a reading; an elevated correction indicates compensation, not by itself whether air leakage, fuel supply, injectors or sensor error is responsible. Record faults and operating conditions before clearing adaptations, and assess any calibration change only against a healthy, comparable baseline.

File and tool scope

FG Technology's vehicle list names Simos 6.2 and 6.3 with product-specific programming coverage. A commercial Simos 6.2 file listing describes its offering as calibration/map data rather than a complete ECU or EEPROM backup. Neither source guarantees that a particular file contains the areas needed for recovery. Verify the exact ECU and software, read scope, file format, checksums and recovery method with the selected tool before writing.

Sources