Anti-Lock Brake System (ABS) and Stability Control — 2016 workshop reference 3000

Ignition OFF. Wait one minute then disconnect RCM C310A and C310B. Inspect the RCM installation and verify all fasteners are tightened to specifications. Inspect the RCM mounting surface for damage, corrosion, dirt and other irregularities.

Is the RCM installed correctly and the mounting surface clean and free from damage?

Yes	GO to Pinpoint Test G
No	CLEAR or REPAIR the RCM mounting surface as necessary. TIGHTEN the fasteners to the correct toque specification.

U0104:00, U0405:41, U0405:82

Refer to Wiring Diagrams Cell 42 for schematic and connector information.

Normal Operation and Fault Conditions

With the ignition ON, the CCM sends messages to the ABS module over the HS-CAN2. If the ABS module does not receive these messages within a certain time frame, the ABS module sets a DTC. For information on the messages sent to the ABS module by the CCM, refer to the Network Message Chart. REFER to: Anti-Lock Brake System (ABS) and Stability Control - System Operation and Component Description (206-09 Anti-Lock Brake System (ABS) and Stability Control, Description and Operation).

DTC Fault Trigger Conditions

DTC	Description	Fault Trigger Conditions
	U0104:00 Lost Communication With Cruise Control Module: No Sub Type Information	This DTC sets in continuous memory and on-demand when any of the messages from the CCM are missing. This can be due to a CCM failure, a circuit failure or excessive load on the HS-CAN2.
	U0405:41 Invalid Data Received From Cruise Control Module: General Checksum Failure	This DTC sets in continuous memory and on-demand if the ABS module receives "fault" or "unknown" information in the collision mitigation by braking messages from the CCM instead of valid checksum information.
	U0405:82 Invalid Data Received From Cruise Control Module: Alive / Sequence Counter Incorrect / Not Updated	The CCM sends a rolling counter value to the ABS module. This DTC sets in continuous memory and on-demand if the rolling counter value does not increase past 1.

DTC

Description

Fault Trigger Conditions

U0104:00 Lost Communication With Cruise

Control Module: No Sub Type Information

This DTC sets in continuous memory and on-demand when any of the messages from the CCM are missing. This can be due to a CCM failure, a circuit failure or excessive load on the HS-CAN2.

U0405:41 Invalid Data Received From Cruise

Control Module: General Checksum Failure

This DTC sets in continuous memory and on-demand if the ABS module receives "fault" or "unknown" information in the collision mitigation by braking messages from the CCM instead of valid checksum information.

U0405:82 Invalid Data Received From Cruise

Control Module: Alive / Sequence Counter Incorrect / Not Updated

The CCM sends a rolling counter value to the ABS module. This DTC sets in continuous memory and on-demand if the rolling counter value does not increase past 1.

Possible Causes

Network communication concern CCM ABS module

PINPOINT TEST P : U0104:00, U0405:41, U0405:82

P1 CHECK THE COMMUNICATION NETWORK

Ignition ON. Using a diagnostic scan tool, carry out the Network Test.

Does the CCM pass the Network Test?

Source reference 3000

2016 Mustang workshop publication supplied to Mustang Atlas. Original technical text and illustrations; HTML formatting by Mustang Atlas. Source page numbering is retained for traceability. Follow the configuration, revision, warnings, and cross-references in the material. About this edition.