Tuning Wiki

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

Page organisation in this revision
Page type
Technical article
Subject
Tuning
Parent
Bosch ME7.1
Applies to
Bosch ME7.1
Tool groups
None
Manufacturers
Audi

Applicability and the two temperature paths

This guide concerns the Audi S4 2.7-litre V6 biturbo described in Audi Self-Study Programme 198 and NefMoto's ME7.1 discussions. Other ME7 installations may use different sensors, models, enrichment logic and logger names. Identify the ECU software, exhaust hardware and fitted sensors before interpreting a log.

Audi describes an exhaust-temperature sender on each cylinder bank, G235 and G236, situated in the exhaust manifolds upstream of the turbochargers. It says the stock Motronic can enrich the mixture for temperature control. A sender failure can also trigger a reduced charge-pressure strategy and an emergency enrichment characteristic. These are stock S4 functions, not proof that a particular modified image still has the same configuration. Audi SSP 198, exhaust-temperature control and senders

In a NefMoto discussion of calculated and actual EGT, contributors distinguish the modelled before-catalyst temperature tabgm_w from sender-related values named tats_w and tats2_w in the discussed software. These are different quantities and locations, so equal values are not expected. Verify signal aliases, bank assignment, scaling and sensor availability in the definition for the actual ECU.

Why a flat reading can mislead

For the original S4 sender, Audi specifies an accuracy of ±5 °C within its 950–1025 °C measurement range. That narrow range is a property of the documented sensor, not a universal range for all ME7 applications. A displayed value at or near a bound may reflect the channel's range, scaling or substitution rather than the true temperature: check the diagnostic definition and sender circuit before interpreting a plateau. Faults and wiring should be investigated on both banks.

Audi describes temperature control around 980 °C for its stock application. That is manufacturer context for the original hardware and strategy, not a universal target for modified engines, other sensors, measurement positions or fuels. A probe at a different location cannot be assumed to reproduce a modelled before-catalyst value or an upstream manifold measurement.

Diagnose an unexpected enrichment event

  1. Record the ECU and calibration, fitted sensor and probe locations, relevant fault codes and any changes to turbochargers, manifolds, downpipes or catalysts.
  2. Log engine speed and load; requested and measured lambda; both sender channels where fitted; modelled exhaust temperature and, where defined, the active component-protection request or status. Include intake and coolant temperatures and ignition/knock data. Confirm units, bank and timestamps.
  3. Determine whether enrichment is actually requested or whether measured lambda differs from the final request. A driver-demand map is only one possible contributor. Use a suitable calibrated wideband where the fitted lambda feedback cannot measure the rich mixture.
  4. Compare both banks, sensor validity and the model trend. A single-bank sensor or wiring fault suggests a different investigation from a model or shared fueling issue; it does not by itself prove the cause.

A separate ME7.5 discussion about an EGT model after hardware changes asks how far the model remains representative with different exhaust components. It does not establish a transferable correction. Use matched, appropriately located measurement and the applicable function documentation to evaluate a changed system; do not infer the correct model or protection settings from a single temperature reading.

Related guides

See ME7.1 S4 fueling and MAF examples, ME7 MAF and lambda log review and ME7 ignition and knock reference. Forum observations are attributed reports; this wiki has not independently reproduced them.