Initial SRS Diagnostic Procedure

WARNING: This page is about a different car, the 1995 Mitsubishi Eclipse, 1995 Eagle Talon, 1995 Dodge Avenger, and 1995 Chrysler Sebring. However, it is still accessible from the selected car via links, so may be relevant.

WARNING: Read and understand all air bag service precautions to prevent accidental air bag deployment and personal injury. See SERVICE PRECAUTIONS .

NOTE: Ensure fuses No. 11 and 18 are okay. See Fig 1 . Ensure battery is fully charged. If battery voltage is too low, SRS warning light will come on. When battery voltage is restored to normal, light will go out. Codes remain stored for no more than about 7 days. Codes can be stored no more than 250 times. After servicing, reconnect negative battery cable. Erase codes using Multi-Use Tester II (MUT-II,MB991502). Check SRS warning light to verify system operation. See TESTING - SYSTEM OPERATION CHECK .

Fig 1: Identifying SDU Connector Terminals

Courtesy of MITSUBISHI MOTOR SALES OF AMERICA.

CAUTION: Ensure ignition is off before connecting or disconnecting MUT-II at Data Link Connector (DLC). SDU connector is a double-locking mechanism. DO NOT use excessive force when disconnecting SDU connector.

Before proceeding, read and understand all air bag service precautions. See SERVICE PRECAUTIONS . Turn ignition on. If SRS warning light comes on for about 7 seconds and then turns off, SRS is functioning properly at this time. If SRS warning light does not come on, or comes on and stays on, insert Read Only Memory (ROM) Pack into MUT-II.
Turn ignition switch to LOCK position. Connect MUT-II to DLC. See Figure . Turn ignition on. If MUT-II does not display CAN'T COMM, go to step 4).
If MUT-II displays CAN'T COMM, try to communicate with other systems (engine control, etc.). If MUT-II cannot communicate with other systems, go to MUT-II CANNOT COMMUNICATE WITH OTHER SYSTEMS. If MUT-II can communicate with other systems, go to MUT-II CAN COMMUNICATE WITH OTHER SYSTEMS.
Use MUT-II to retrieve code(s). Record code(s) and service data (fault duration and number of times memory was erased). Go to appropriate CODE procedure.