DTC B10A2:00 [SKYACTIV-D 1.5]


id0102q2215200

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
•  The following DTCs are not detected:
―  SAS control module: U0073:00, U0151:00, U0336:00
Drive cycle
•  1
Self test type
•  CMDTC self test
Sensor used
•  PCM
FAIL-SAFE FUNCTION
•  Not applicable
VEHICLE STATUS WHEN DTCs ARE OUTPUT
•  Inhibits the starter operation during cranking while a collision signal from the SAS control module is received continuously.
•  Stops fuel injection control
•  Stops engine coolant fan control
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.
am3zzw00014908

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 [SKYACTIV-D 1.5].)
3.  After switching the ignition off, switch the ignition back ON and leave for 5 s or more.

PID Item/Simulation Item Used In Diagnosis

•  Not applicable

Function Inspection Using M-MDS

STEP

INSPECTION

RESULTS

ACTION

1
PURPOSE: RECORD VEHICLE STATUS AT TIME OF DTC DETECTION TO UTILIZE WITH REPEATABILITY VERIFICATION
Note
•  Recording can be facilitated using the screen capture function of the PC.
•  Record the snapshot data on the repair order.
Go to the next step.
2
PURPOSE: 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.
3
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.
4
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.
•  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
•  Clear the DTC from the PCM memory using the M-MDS.
•  Implement the repeatability verification procedure.
•  Perform the DTC Reading Procedure.
•  Is the same DTC present?
Yes
Repeat the inspection from Step 1.
•  If the malfunction recurs, replace the PCM.
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.
No
DTC troubleshooting completed.