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.
Low-side pressure sensor: an Audi service example
Audi technical service bulletin 24 07 19, 2015106/3 covers illuminated malfunction indicators with P310B and/or P129F on specified 2005–2007 A4 and A6 3.2 FSI vehicles, among other applications. Audi describes fuel intrusion into low-side pressure sender G410 as a possible source of an incorrect signal. The bulletin does not identify a Simos 6 suffix or establish that every such fault is a sensor fault; check the exact vehicle, current repair information and other fault codes.
Its separate 3.2 FSI procedure requires the listed fault and no other fuel-delivery electrical fault clearly indicating a failed component. After the specified idle and shut-down conditions, it compares measuring-value block 103, field 1 with an independent low-pressure mechanical-gauge reading adjusted by adding 1 bar. The bulletin says the block reading is normally about 1 bar above the gauge reading, so the unadjusted difference alone is not a failed sensor. Under those exact test conditions it gives a deviation of more than ±1.0 bar from the adjusted reading as indicating a likely G410 issue. These block numbers, correction and tolerance belong to this procedure; do not transfer them to another engine, logger or operating state. Follow the current vehicle-specific workshop procedure and use the specified equipment and fuel-system precautions.
This distinction matters when interpreting a tuning log: an implausible reported low-side pressure can come from the measurement path as well as actual fuel delivery. A genuine supply fault can also affect the high-pressure system, so check the signal and supply independently before changing pump control or assuming a rail-pressure problem is a calibration limit. The bulletin describes sensor replacement and a subsequent basic setting only when its conditions are met; it is not a blanket replacement instruction.
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.
Calibration file and tool identification examples
ECUFILES lists an Audi A6 2.4 V6 automatic under Simos 6.2 with software identifier S6300FL000000. The seller explicitly describes the file as partial map data, leaves its hardware field blank and displays a size of “200000” without stating the number base on that page. These are seller-reported details, not proof of the ECU suffix, actual file contents, hardware match or a complete memory image. A software string alone does not identify the car or confirm a full recovery file.
A separate Dimsport ECU application list names Simos 6.2 with MPC561/562/563/564 processor variants, New Trasdata plug-ins 174 and 214, and New Genius protocol FLASH_0215. This is an historical tool catalogue, not a claim that each processor uses each plug-in or that all ECU areas are readable using every method. Match the actual controller and current tool instructions, then record which memory regions and format a read contains. Neither the processor family nor file size alone establishes compatibility or a usable restoration path.
Research file: S6300FL and 2.4 MPI
A public directory labelled Simos 6.23 contains a file named ORG READ and an adjacent WinOLS map-pack file whose name includes S6300FL000000. On 17 November 2026, the 2,097,152-byte ORG READ file contained the readable strings S6300FL000000, 4F0910552R, 4F0907552D, 2.4l V6 MPI and BDW. The inspected bytes had SHA-256 c8d19ba6545fb696aff69308ef25efe1903198190b690625716b34d7440e488b. The directory label, filename and embedded strings are unverified metadata: they do not prove the file is factory original, a complete recovery image, or a match for the adjacent map pack. No map names, axes or scaling have been verified from that pack.
A ZipTuning listing associates the same part and software strings with an A6 2.4 MPI and calls it Simos 6.3; ECUFILES uses the Simos 6.2 label for its 2.4 V6 example above. These seller descriptions do not establish the identity of a controller or interchangeability of its files. The public file's MPI text describes a different injection system from the 3.2 FSI direct-injection example on this page. Verify the fitted injection system and ECU identification, establish the provenance and memory scope of a read, and match definitions to its actual software before using a 3.2 FSI fuel or injection calibration on a 2.4 MPI engine.
Sources
- Audi A6 3.2 FSI technical data, Germany, August 2005. Factory Simos 6 and 3.2 FSI system description. Accessed 17 November 2026.
- Audi SSP 325: A6 2005 assemblies, 3.2 FSI section. AUK engine, air system, direct-injection fuel supply and sensor/fault context. Accessed 17 November 2026.
- Prins VSI-DI installation document, Audi A6 3.2 AUK. Supplier's Simos 6.2 A example; no universal application or pinout claim. Accessed 17 November 2026.
- Audi SSP 411: 2.8 and 3.2 FSI with Audi valvelift, English third-party rendering. Comparison naming Simos 6D2 and the later Simos 8.1. Accessed 17 November 2026.
- FG Technology OBD driver list and V-Tuning Simos 6.2 file listing. Vendor-specific coverage and file-scope statements. Accessed 17 November 2026.
- Siemens “Simos 6” OBD System Strategy, sections 3 and 6, rehosted by Volkswagen Technical Site. Crankshaft roughness and adaptation concepts; the public copy does not establish a specific software version or vehicle application. Accessed 17 November 2026.