DTC B10A2:00 [MZR 1.6]

id0102h3215200

Note

• To determine the malfunctioning part, proceed with the diagnostics from “Function Inspection Using M-MDS”.

Details On DTCs

DESCRIPTION

Vehicle collision

DETECTION CONDITION

Determination conditions

•  A collision signal from the SAS control module is received.

Preconditions

•  Not applicable

Drive cycle

•  1

Self test type

•  CMDTC self test

Sensor used

•  PCM

FAIL-SAFE FUNCTION

•  Stops fuel injection control

•  Stops fuel pump control

•  Stops ignition control

•  Stops engine coolant fan control

VEHICLE STATUS WHEN DTCs ARE OUTPUT

•  Stops fuel pump operation when ignition is switched ON

•  Delays starter operation during cranking for maximum 1.2 s.

POSSIBLE CAUSE

•  Vehicle is involved in collision (collision signal from SAS control module is received)

•  SAS control module malfunction

•  PCM malfunction

DESCRIPTION	Vehicle collision
DETECTION CONDITION	Determination conditions	• A collision signal from the SAS control module is received.
Preconditions	• Not applicable
Drive cycle	• 1
Self test type	• CMDTC self test
Sensor used	• PCM
FAIL-SAFE FUNCTION	• Stops fuel injection control • Stops fuel pump control • Stops ignition control • Stops engine coolant fan control
VEHICLE STATUS WHEN DTCs ARE OUTPUT	• Stops fuel pump operation when ignition is switched ON • Delays starter operation during cranking for maximum 1.2 s.
POSSIBLE CAUSE	• Vehicle is involved in collision (collision signal from SAS control module is received) • SAS control module malfunction • PCM malfunction

System Wiring Diagram

• Not applicable

Function Explanation (DTC Detection Outline)

• During a collision, the SAS control module sends a collision signal to the PCM via the CAN signal. The PCM records a DTC by receiving a collision signal.

• This DTC does not indicate a part malfunction. It indicates operation of fail-safe from safety assurance during a vehicle collision.

am3zzw00014063

Repeatability Verification Procedure

1. Switch the ignition ON and leave for 5 s or more.

2. Clear the DTC from the PCM memory using the M-MDS. (See CLEARING DTC [MZR 1.6].)

3. After switching the ignition off, switch the ignition back ON and leave for 5 s or more.

4. Using the M-MDS, display DTCs and verify that DTC U0151:00 is not displayed. (See ON-BOARD DIAGNOSTIC TEST [MZR 1.6].)

PID Item/Simulation Item Used In Diagnosis

• Not applicable

Function Inspection Using M-MDS

STEP

INSPECTION

RESULTS

ACTION

1

VERIFY RELATED SERVICE INFORMATION AVAILABILITY

•  Verify related Service Information availability.

•  Is any related Service Information available?

Yes

Perform repair or diagnosis according to the available Service Information.

•  If the vehicle is not repaired, go to the next step.

No

Go to the next step.

2

PURPOSE: VERIFY IF OPERATION IS NORMAL AFTER VEHICLE COLLISION

•  Ask customer about vehicle collision experience.

•  Has the vehicle in for servicing been involved in a collision in which the air bag is deployed?

Yes

Explain to the customer that the DTC is recorded as a result of a vehicle collision.

Go to the troubleshooting procedure to perform the procedure from Step 1.

No

Go to the next step.

3

PURPOSE: VERIFY IF DIAGNOSTIC RESULT IS AFFECTED BY DTC RELATED TO SAS CONTROL MODULE

•  Switch the ignition off, then ON (engine off).

•  Perform the SAS control module DTC inspection using the M-MDS.
(See DTC INSPECTION.)

•  Are any DTCs present?

Yes

Go to the applicable DTC inspection.

(See DTC TABLE.)

Go to the troubleshooting procedure to perform the procedure from Step 1.

No

Go to the troubleshooting procedure to perform the procedure from Step 1.

STEP	INSPECTION	RESULTS	ACTION
1	VERIFY RELATED SERVICE INFORMATION AVAILABILITY • Verify related Service Information availability. • Is any related Service Information available?	Yes	Perform repair or diagnosis according to the available Service Information. • If the vehicle is not repaired, go to the next step.
No	Go to the next step.
2	PURPOSE: VERIFY IF OPERATION IS NORMAL AFTER VEHICLE COLLISION • Ask customer about vehicle collision experience. • Has the vehicle in for servicing been involved in a collision in which the air bag is deployed?	Yes	Explain to the customer that the DTC is recorded as a result of a vehicle collision. Go to the troubleshooting procedure to perform the procedure from Step 1.
No	Go to the next step.
3	PURPOSE: VERIFY IF DIAGNOSTIC RESULT IS AFFECTED BY DTC RELATED TO SAS CONTROL MODULE • Switch the ignition off, then ON (engine off). • Perform the SAS control module DTC inspection using the M-MDS. (See DTC INSPECTION.) • Are any DTCs present?	Yes	Go to the applicable DTC inspection. (See DTC TABLE.) Go to the troubleshooting procedure to perform the procedure from Step 1.
No	Go to the troubleshooting procedure to perform the procedure from Step 1.

Troubleshooting Diagnostic Procedure

Intention of troubleshooting procedure

• Step 1—2

― Verify that the primary malfunction is resolved and there are no other malfunctions.

STEP

INSPECTION

RESULTS

ACTION

1

PURPOSE: PERFORM DTC INSPECTION AND VERIFY IF MALFUNCTIONING PART IS PCM

•  Always reconnect all disconnected connectors.

•  Clear the DTC from the PCM memory using the M-MDS.
(See CLEARING DTC [MZR 1.6].)

•  Implement the repeatability verification procedure.
(See Repeatability Verification Procedure.)

•  Perform the DTC Reading Procedure.
(See ON-BOARD DIAGNOSTIC TEST [MZR 1.6].)

•  Is the same DTC present?

Yes

Repeat the inspection from Step 1.

•  If the malfunction recurs, replace the PCM.
(See PCM REMOVAL/INSTALLATION [MZR 1.6].)

Go to the next step.

No

Go to the next step.

2

PURPOSE: VERIFY IF THERE IS ANY OTHER MALFUNCTION

•  Is any other DTC or pending code stored?

Yes

Go to the applicable DTC inspection.

(See DTC TABLE [MZR 1.6].)

No

DTC troubleshooting completed.

STEP	INSPECTION	RESULTS	ACTION
1	PURPOSE: PERFORM DTC INSPECTION AND VERIFY IF MALFUNCTIONING PART IS PCM • Always reconnect all disconnected connectors. • Clear the DTC from the PCM memory using the M-MDS. (See CLEARING DTC [MZR 1.6].) • Implement the repeatability verification procedure. (See Repeatability Verification Procedure.) • Perform the DTC Reading Procedure. (See ON-BOARD DIAGNOSTIC TEST [MZR 1.6].) • Is the same DTC present?	Yes	Repeat the inspection from Step 1. • If the malfunction recurs, replace the PCM. (See PCM REMOVAL/INSTALLATION [MZR 1.6].) Go to the next step.
1		No	Go to the next step.
2	PURPOSE: VERIFY IF THERE IS ANY OTHER MALFUNCTION • Is any other DTC or pending code stored?	Yes	Go to the applicable DTC inspection. (See DTC TABLE [MZR 1.6].)
2		No	DTC troubleshooting completed.