DTC B10A2:00 [PCM (SKYACTIV-D)]
id0102t5215200
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:
|
|
Drive cycle
|
• 1
|
|
Self test type
|
• CMDTC self test
|
|
Sensor used
|
• PCM
|
|
Fail-safe
|
• Inhibits the DENOx/DESOx control.
|
|
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
Function Explanation (DTC Detection Outline)
am3zzw00014908
|
Repeatability Verification Procedure
PID Item/Simulation Item Used In Diagnosis
Function Inspection Using M-MDS
Step |
Inspection |
Results |
Action |
---|---|---|---|
1
|
PURPOSE: RECORD VEHICLE STATUS WHEN DTC WAS DETECTED TO UTILIZE WITH REPEATABILITY VERIFICATION
• Record the freeze frame data/snapshot data.
|
—
|
Go to the next step.
|
2
|
PURPOSE: VERIFY RELATED REPAIR INFORMATION OR SERVICE INFORMATION AVAILABILITY
• Verify related Service Bulletins, on-line repair information, or Service Information availability.
• Is any related Information available?
|
Yes
|
Perform repair or diagnosis according to the available 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 Troubleshooting Diagnostic 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.
(See DTC INSPECTION.)
• Are any DTCs present?
|
Yes
|
Go to the applicable DTC inspection.
Go to Troubleshooting Diagnostic Procedure to perform the procedure from step 1.
|
No
|
Go to Troubleshooting Diagnostic Procedure to perform the procedure from step 1.
|
Troubleshooting Diagnostic Procedure
Step |
Inspection |
Results |
Action |
---|---|---|---|
1
|
PURPOSE: VERIFY THAT VEHICLE IS REPAIRED
• Install/connect the part removed/disconnected during the troubleshooting procedure.
• Clear the DTC recorded in the memory.
(See CLEARING DTC.)
• Replicate the vehicle conditions at the time the DTC was detected using the following procedure.
• Perform the DTC inspection for the PCM.
(See DTC INSPECTION.)
• Is the same Pending DTC present?
|
Yes
|
Refer to the controller area network (CAN) malfunction diagnosis flow to inspect for a CAN communication error.
If the CAN communication is normal, perform the diagnosis from Step 1.
• If the malfunction recurs, replace the PCM, then go to the next step.
|
No
|
Go to the next step.
|
||
Repair completion verification
|
PURPOSE: VERIFY IF OTHER DTCs DISPLAYED
• Perform the DTC inspection.
(See DTC INSPECTION.)
• Are any other DTCs displayed?
|
Yes
|
Repair the malfunctioning location according to the applicable DTC troubleshooting.
|
No
|
DTC troubleshooting completed.
|