Mitsubishi Lancer Evolution X. Manual - part 238

MULTIPORT FUEL INJECTION (MFI) DIAGNOSIS

TSB Revision

MULTIPORT FUEL INJECTION (MFI)

13A-17

CAUTION

To prevent damage to scan tool MB991958, always turn the 
ignition switch to the "LOCK" (OFF) position before con-
necting or disconnecting scan tool MB991958.
1. Connect scan tool MB991958 to the data link connector.
2. Turn the ignition switch to the "ON" position.
3. Select "System select."
4. Choose "from 2006 MY" under "MODEL YEAR".
5. Check that "Vehicle Information" contents are correct.
6. Choose "MFI".
7. Select "Actuator Test."
8. Choose an appropriate item and select the "OK" button.

HOW TO DIAGNOSE THE CAN BUS LINES

Required Special Tools:

•  MB991958: Scan Tool (M.U.T.-III Sub Assembly)

• MB991824: V.C.I.
• MB991827: USB Cable
• MB991910: Main Harness A

AC608435

Data link connector

MB991827

MB991824

MB991910

AB

MULTIPORT FUEL INJECTION (MFI) DIAGNOSIS

TSB Revision

MULTIPORT FUEL INJECTION (MFI)

13A-18

CAUTION

To prevent damage to scan tool MB991958, always turn the 
ignition switch to the "LOCK" (OFF) position before con-
necting or disconnecting scan tool MB991958.
1. Connect scan tool MB991958 to the data link connector.
2. Turn the ignition switch to the "ON" position.
3. Select "CAN bus diagnosis" from the start-up screen.
4. When the vehicle information is displayed, confirm that it 

matches the vehicle whose CAN bus lines will be 
diagnosed.

• If they matches, go to step 8.
• If not, go to step 5.

5. Select the "view vehicle information" button.
6. Enter the vehicle information and select the "OK" button.
7. When the vehicle information is displayed, confirm again 

that it matches the vehicle whose CAN bus lines will be 
diagnosed.

• If they matches, go to step 8.
• If not, go to step 5.

8. Select the "OK" button.
9. When the optional equipment screen is displayed, choose 

the one which the vehicle is fitted with, and then select the 
"OK" button.

HOW TO READ PROVISIONAL DIAGNOSTIC 
TROUBLE CODES

Required Special Tools:

• MB991958: Scan Tool (M.U.T.-III Sub Assembly)

• MB991824: V.C.I.
• MB991827: USB Cable
• MB991910: Main Harness A

If detecting the malfunction during the first drive cycle, the ECM 
temporarily stores the diagnosis code as the provisional diag-
nosis code. If detecting the same malfunction during the next 
drive cycle, the ECM determines that the malfunction exists. 
The ECM outputs the diagnosis code. On Scan Tool 
MB991958, it is possible to display the stored provisional diag-
nosis code which the ECM had detected during the first drive 
cycle. This makes it possible to confirm in one drive cycle 
whether the malfunction could happen again after the repair.

.

AC608435

Data link connector

MB991827

MB991824

MB991910

AB

MULTIPORT FUEL INJECTION (MFI) DIAGNOSIS

TSB Revision

MULTIPORT FUEL INJECTION (MFI)

13A-19

CONFIRMATION METHOD

CAUTION

To prevent damage to scan tool MB991958, always turn the 
ignition switch to the "LOCK" (OFF) position before con-
necting or disconnecting scan tool MB991958.
1. Connect scan tool MB991958 to the data link connector.
2. Turn the ignition switch to the "ON" position.
3. Select "System select."
4. Choose "from 2006 MY" under "MODEL YEAR".
5. Check that "Vehicle Information" contents are correct.
6. Choose "MFI".
7. Select "Special Function" from MFI Screen.
8. Select "Provisional DTCs" from Special Function Screen.

PERMANENT DTC

The permanent DTC(PDTC) is stored in the EEPROM of the 
engine control module (ECM) as the permanent status, which 
checks that the malfunction of the emission related compo-
nents/ the system has not been repaired yet. When detecting 
the malfunction necessary to illuminate the malfunction indica-
tor lamp (SERVICE ENGINE SOON or Check Engine Lamp), 
the ECM illuminates the MIL and stores the appropriate DTC as 
the permanent DTC in the EEPROM concurrently. The usual 
DTC is stored in the EEPROM aside from this. The ECM can 
store up to 6 PDTCs. The ECM, therefore, cannot store the 7th 
and subsequent PDTCs. If the temporary malfunction causes 
the malfunction indicator lamp to be illuminated and then the 
reinstatement during the subsequent driving causes it to be 
extinguished, the PDTC is erased. Also if the ECM checks that 
the DTC malfunction is fixed during the driving after the DTC 
repair is completed, the PDTC is erased. The permanent DTC, 
however, is not erased by disconnecting the battery terminal or 
erasing with the scan tool (M.U.T-III). The permanent DTC can 
be erased if all readiness statuses are erased or not completed 
at the time of reprogramming the ECM. If must be erased while 
the vehicle is repaired, the PDTC can be erased by the proce-
dures shown below. If must be erased because of the failure to 
pass the Inspection and Maintenance (I/M) test, the permanent 
DTC can also be erased by the following procedure:

.

AC608435

Data link connector

MB991827

MB991824

MB991910

AB

MULTIPORT FUEL INJECTION (MFI) DIAGNOSIS

TSB Revision

MULTIPORT FUEL INJECTION (MFI)

13A-20

PROCEDURES FOR ERASING PERMANENT DTC

1. Check that the DTC is not stored. If the DTC is stored, 

perform the DTC troubleshooting, then repair the DTC.
NOTE: The order of step 2 and 3 can be exchanged.

2. Drive the vehicle at least once under the conditions 

satisfying all the following requirements:

• The total driving (engine running) time must be more than 

10 consecutive minutes. 

• More than 30 seconds of idling must be included in the driv-

ing

• More than 5 consecutive minutes of driving at more than 40 

km/h (25 mph) must be included in the driving.    

3. Drive the vehicle at least two times in the drive cycle pattern 

suitable for the permanent DTC. (Refer to OBD-II DRIVE 
CYCLE for the drive cycle pattern.) If the DTC does not have 
the drive cycle pattern, start and stop the engine. Wait 15 
seconds or more to start again after the stop. Repeat at least 
2 times.

4. Restart and stop the engine.
5. Check that the permanent DTC is erased. If the permanent 

DTC is not erased, check the DTC or the provisional DTC. If 
the malfunction code is stored, repair the DTC. Try to erase 
the permanent DTC again (from Step 1 to 5). If the 
malfunction code is not stored, the drive cycle pattern (Step 
3) monitoring the malfunction can possibly be insufficient.