Tuning Wiki

Simos 8.2 is an engine-management variant documented on Audi naturally aspirated 3.2-litre V6 FSI applications. It should be identified from the actual vehicle and ECU software, rather than inferred from the broader Simos 8 family.

Processor

AutoTuner's ECU compatibility export of 28 October 2026 and its Simos 8.2 announcement list the Infineon TC1796 as the microcontroller of Simos 8.2. The announcement names the Audi 3.2 V6 FSI (265 hp) as its listed vehicle and offers OBD and bench read and write. These are tool-vendor statements, not manufacturer documentation, and the vehicle list may be incomplete.

Documented application and identification

Audi's 2009 Q5 introduction identifies the 3.2 FSI engine with code CALB and 199 kW as using Simos 8.2. This is a documented application, not a complete fitment list. A CMDFlash release also lists an Audi S5 3.2 FSI ECU numbered 8T0907559 and a Q5 3.2 FSI numbered 8R0907559 under Simos 8.2. Record the full ECU hardware and software identifiers, engine code, vehicle and transmission before choosing a protocol or calibration. [1] [2]

Air and valve-lift control

On the documented Q5 CALB engine, Audi describes intake-side Audi valvelift (AVS): sliding cam pieces select smaller or larger intake cam lobes, changing intake-valve lift and duration. Electrically operated solenoids position the cam pieces under ECU control. This makes the physical lift changeover and its operation relevant when diagnosing a transient or drivability complaint; do not assume that every Simos 8.2 application has the same hardware or calibration. [1]

For comparison, the Simos 8.1 overview covers Audi's published descriptions for earlier V6 FSI examples. Its specific changeover strategy should not be assumed to apply unchanged to this ECU.

For CALB actuator implausible-signal codes and the vehicle-scoped Audi service bulletin, see V6 FSI valve-lift actuator diagnosis.

Calibration and logging

A commercial map pack for the specific Q5 calibration 8R0907559G 0004 advertises definitions for torque requests, requested engine load, base ignition, injection phase and rail pressure. These are the seller's labels, not independently verified function names, addresses, axes or evidence that definitions transfer to other software. Establish a definition against the exact read and validate its meaning before changing it. [3]

A practical baseline is to record fault codes and fuel quality, then compare available requested and actual engine load, throttle, cam position and rail pressure alongside engine speed, lambda and individual-cylinder knock corrections. Check valve-lift operation when available and compare repeat runs at similar temperatures. Channel availability and interpretation depend on the ECU software and diagnostic equipment; these are suggested observations, not claims that every channel exists on every variant.

A public example from 8R0907559G 0004

The seller’s page displays one 12-column by 16-row table named Optimal engine torque. It labels the horizontal axis “Fuel per stroke” in mg/st, the vertical axis engine speed in rpm and the values in Nm; at its displayed 420 mg/st and 4,000 rpm intersection it shows 261.2 Nm. This is the seller’s representation of one table in one file, not an independently established factory function, validated unit or measured crankshaft torque. The other named maps’ positions and axes are not exposed by the public list.

For interpretation, first confirm the table boundaries, representation, axis values, units and conditions against the exact ECU file and a reliable definition. The horizontal-axis label alone does not establish that the data is fuel quantity rather than another load or air variable; a torque-related label also does not establish that the table is the active driver demand or a safe target. Use matched logs and suitable independent output measurements when testing a controlled change, and do not copy the sample cell to another calibration.

Reading and writing

The 2013 CMDFlash v3.2.0.116 release note lists CAN read, write, checksum and recovery for the stated S5 and Q5 identifiers, in the context of corrected reading issues. This is historical product-specific coverage, not a guarantee for another software version, tool or an unmodified ECU. Confirm the tool's current application list and recovery procedure for the exact ECU. [2]

Distinguish a physical read, a calibration-only read and a supplied or virtual original; establish exactly what memory each contains and what the selected recovery method requires. The seller of the example above explicitly says its original file is not a full backup and does not include EEPROM. Do not treat a matching part number or purchased original alone as proof of recovery compatibility. [3]

PCMflash's module 57 manual, page 49, separately lists read, write and checksum functions for its 3.2 V6 Simos 8.2 coverage. The entry does not establish a full-memory read, a recovery method or compatibility with every 8.2 software version; confirm the current protocol and file scope for the identified ECU.

Sources

  1. Audi of America, 2009 Audi Q5 Vehicle Introduction (SSP 994803), third-party text mirror: CALB engine management and AVS description.
  2. CMDFlash v3.2.0.116 release note: historical tool coverage and listed identifiers.
  3. Auto-Remap, 8R0907559G 0004 Simos 8.2 map-pack listing: seller's file-specific labels and file-scope statement.
  4. AutoTuner: Continental Simos8.2. Tool-vendor announcement; MCU and named vehicle. Accessed 19 November 2026.
  5. AutoTuner ECU compatibility list (PDF export dated 28 October 2026). Tool-vendor listing of ECU type and microcontroller. Accessed 19 November 2026.

Directly applicable articles

Shared family guidance

From parent families. Broader context does not establish compatibility with this ECU or software version.