Menu +
Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

DTC B10A2:00 [PCM (SKYACTIV-G 2.0)]

< Previous Next >

2016 – MX-5 – Engine

DTC B10A2:00 [PCM (SKYACTIV-G 2.0)]

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

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.

Repeatability Verification Procedure

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 REPAIR INFORMATION AVAILABILITY

  • Verify related Service Bulletins and/or on-line repair information availability.

  • Is any related repair information available?

Yes

Perform repair or diagnosis according to the available repair 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

Yes

Go to the applicable DTC inspection.

(See DTC TABLE [SAS CONTROL MODULE (STANDARD DEPLOYMENT CONTROL SYSTEM)].)

(See DTC TABLE [SAS CONTROL MODULE (TWO-STEP DEPLOYMENT CONTROL SYSTEM)].)

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

Yes

Repeat the inspection from Step 1.

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 [PCM (SKYACTIV-G 2.0)].)

No

DTC troubleshooting completed.

< Previous Next >

© 2014 Mazda North American Operations, U.S.A.