10.07.2015 Views

general information - Martin Nez

general information - Martin Nez

general information - Martin Nez

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4-24 FI SYSTEM DIAGNOSISSELF-DIAGNOSTIC PROCEDURESNOTE:* Do not disconnect couplers from the ECM, the battery cablefrom the battery, ECM ground wire harness from the engine ormain fuse before confirming the malfunction code (self-diagnostictrouble code) stored in memory. Such disconnection willerase the memorized <strong>information</strong> in ECM memory.* Malfunction code stored in ECM memory can be checked bythe special tool.* Before checking malfunction code, read SELF-DIAGNOSISFUNCTION “USER MODE and DEALER MODE” (4-16 to-18) carefully to have good understanding as to what functionsare available and how to use it.* Be sure to read “PRECAUTIONS IN SERVICING” (4-3)before inspection and observe what is written there.• Remove the left frame cover. (8-4)• Connect the special tool to the dealer mode coupler at the wiringharness, and start the engine or crank the engine for morethan 4 seconds.• Turn the special tool’s switch ON and check the malfunctioncode to determine the malfunction part. 09930-82720: Mode select switchSELF-DIAGNOSIS RESET PROCEDURE• After repairing the trouble, turn OFF the ignition switch andturn ON again.• If the malfunction code indicates (C00), the malfunction iscleared.• Disconnect the special tool from the dealer mode coupler.NOTE:* Even though the malfunction code (C00) is indicated, the previousmalfunction history code still remains stored in the ECM.Therefore, erase the history code memorized in the ECM usingSDS.* The malfunction code is memorized in the ECM also when thewire coupler of any sensor is disconnected. Therefore, when awire coupler has been disconnected at the time of diagnosis,erase the stored malfunction history code using SDS.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!