LEMON Manuals: Even more car manuals for everyone
Home >> Mercedes Benz >> 2001 >> ML430 >> Repair and Diagnosis >> Engine Performance >> Tune-Up >> Mixture Formation - 163 Chassis (3 Of 4) >> Self-Diagnostic System >> Notes on ME-SFI diagnostic trouble code memory - AD07.61-P-2000-10B

Notes on ME-SFI diagnostic trouble code memory - AD07.61-P-2000-10B

Notes on diagnostic trouble code memory 

The ME-SFI control module (N3/10) has a diagnostic trouble code memory. The detection of faults and their storage is differentiated as follows:

The diagnostic trouble code memory is erased when the vehicle battery is disconnected.

Faults which no longer occur are erased automatically from the diagnostic trouble code memory after max. 40 warm-up phases  .

USA ONLY , not for Model 463: the CHECK ENGINE malfunction indicator lamp comes on if the fault has already been stored in the last driving cycle  "CHECK ENGINE" malfunction indicator lamp goes off if a fault is no longer detected for 3 driving cycles under the same operating conditions (as stored for fault identification).

A warm-up phase or one trip is as follows:

warm-up phase 

trip 

One driving  cycle for a test comprises

The stored faults can only be read out using the HHT  with ignition "ON" or with "engine running".

The pulse display as well as the diagnosis via duty cycle display are no longer necessary.

USA ONLY , not for Model 463: in line with legal requirements, faults can also be read out at the diagnosis test connector conforming to SAE standard, ISO 9141-2, with a generic scan tool.

Notes on self-adaptation of the mixture formation 

For vehicles with TWC, the lambda control determines the injection time so precisely that the fuel/air ratio in all operating states is always approx. Lambda 1 (corresponds to 14.7 kg air to 1 kg fuel). If faults occur due to:

the ME-SFI 2.0 control module automatically performs a correction of the mixture formation.

The correction variables are continuously calculated and permanently stored. The self-adaptation is performed additively when idling and multiplicatively with partial load. Correction in the rich or lean direction when idling is ± 1.0 ms (injection time) and with partial load has a factor 0.68 -1.32. After repair operations, the ME-SFI 2.0 control module adapts automatically.

Notes on drive authorization system stage 3 (DAS) 

For vehicles with the gasoline injection and ignition system (ME-SFI 2.0) a drive authorization system stage 3 is installed. The drive authorization system is activated by the EIS control module via the CAN data bus to the ME-SFI control module.

After the drive authorization system has been activated, the ME-SFI control module puts the injection system out of operation. The drive authorization system stage 3 can only be activated or deactivated with the electronic key. After the electronic ignition key has been inserted, the EIS enables the engine control system via the CAN data bus. Opening and closing the vehicle with the mechanical key does not affect the drive authorization system. The ME-SFI control module and the EIS control module are permanently locked to one another by an identification code. This identification cannot be deleted (see HHT actual values "drive authorization system" menu item 3/7). A trial exchange of the ME-SFI control module or the EIS control module in another vehicle is therefore not possible  .

IMPORTANT

If, for checking purposes, a new ME-SFI control module is installed, only a maximum of 40 starting operations may be performed and then the control modules are permanently locked to one another. Before starting for the first time, a variant coding must be performed for the ME-SFI control module using the HHT. In addition, identification must be initiated and the vehicle identification number must be entered (see HHT actual values "drive authorization system" menu item 3/7).

Notes on automatic detection of the lower mechanical limit stop and the full opening of the throttle valves of the actuators 

The limit positions of the throttle valves are detected by the actuator and stored in the ME-SFI control module.

After replacing the ME-SFI control module or the actuator, the mechanical limit stop for the throttle valve and the full-load position must be detected and stored again.

To do this, delete the stored data using HHT and program new data. When connecting the new ME-SFI control module to terminal 30 (B+) for the first time, the control module automatically performs an adaptation of the actuator with the ignition "ON" (lower mechanical limit stop and full-load position of the throttle valve).

Conditions for programming operation: 

If all the conditions are met, leave the ignition switched on for at least 60 seconds  , then switch off the ignition for at least 10 seconds  !

The programmed value is only stored in the memory after 10 starting cycles, provided the voltage is not interrupted. If, for example, the battery is disconnected after the 9th starting cycle, the programming operation must be repeated.

Notes on sensor adaptation for smooth operation test 

After replacing the ME-SFI control module, crankshaft sensor, starter ring gear or engine mount, a sensor adaptation must be performed as follows:

Vehicles as of 02/98 

Notes on output dynamometer/tachometer dynamometer 

ESP or ASR chassis control systems must not be put out of operation by disconnecting the control modules because the wheel speed signals transmitted via the CAN data bus are needed in the ME-SFI and ETC control modules.

To switch off the brake and engine control intervention in the ESP and ASR systems, the function must be canceled in the respective control module as follows:

A. Operations without hand-held-tester 

B. Operations with hand-held-tester 

(BAS/ESP or BAS/ASR malfunction indicator lamp must go on!)

Once the operation is completed, reconnect the connector and delete diagnostic trouble code memory with hand-held-tester! 

Notes on variant coding 

ME-SFI 2.0 control modules have a variant coding. The coding can only be performed with the hand-held-tester (automatically and manually, see notes on HHT "variant coding").

For the coding, the following vehicle versions must be noted: