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
Diagnostics
Parent
Bosch ME7.5
Applies to
Bosch ME7.5
Tool groups
Not recorded in this older revision
Manufacturers
Not recorded in this older revision

Connection mode follows software

S4Wiki’s current connection table groups files by the protocol entries implemented in their firmware. It explicitly lists the ME7.5 1.8T 8E0909518 group with SLOW-0x01. The family label alone is not enough to choose an init address.

Source-reported groupME7Logger connectionQualification
ME7.5 1.8T: 8E0909518*SLOW-0x01The source describes 0x01 as KWP2000 for this group, without a 0x11 entry or SLOW-0x00 sequence
06A906032* and 8N0906018CJ listed in the other rowSLOW-0x11 in the source tableKeep this explicit file-group distinction; do not select the mode from “1.8T” alone
Other part numbers or revised softwareEstablish from the matching documentation or firmware evidenceA wildcard in the source is a reported grouping, not proof for an altered or unidentified file

The logger’s Connect setting is in the communication section of its .ecu configuration. Record the actual connection mode, complete identification and working configuration revision with the log. Do not apply the S4 double-slow-init workaround to a group the source says lacks that sequence.

Diagnostic code assignments differ

The source explains that the market/configuration codeword CWCDCUM can assign different fault codes to related control checks. Its examples include:

Example fileAssignments reported by S4Wiki
06A906032HJThe ratio/plausibility check associated with S4 P1557 is reported as P0234 / 16618; underboost as P0235 / 16619
06A906032NL and 8N0906018CJOverboost and the ratio check can both report P0234; underboost reports P0299 / 16683
Other ME7.5 softwareEstablish the diagnostic mapping and its enabling conditions for that file

Consequently a P0234 in those documented files is not, on its own, proof that actual pressure simply exceeded requested pressure. It may represent the different pressure-ratio/plausibility function. Identify the software and active check, then examine the signals and conditions behind it.

Build a useful diagnostic log

  1. Save the full identification and fault/freeze-frame information available from the diagnostic tool.
  2. Identify which request, measured/modelled pressure and pressure ratio the function uses.
  3. Log the permitted load, pressure request and response, relevant MAF/model signals, and wastegate command where available.
  4. Inspect charge-air leaks, sensor/definition plausibility, N75 and wastegate behaviour in relation to that evidence.
  5. Keep any fallback or adaptation state visible when comparing repeated observations.

The shared logging and torque/load guides explain the signal roles. This page supplies the source-specific ME7.5/1.8T context for choosing a connection and interpreting the code; it does not establish an address map for a different binary.

Source context and adaptation

Adapted, paraphrased and reorganised from S4Wiki contributors’ Tuning, revision 5324, under Creative Commons Attribution 4.0 International. This wiki adds scope labels, cross-links and interpretation notes. The cited software observations have not been independently reproduced by this wiki.

Source sections: Connection modes, Boost control DTCs.

Sources

Curated reference notes. Applicability follows the cited sources; hardware testing by this wiki is not implied.