CAN Bus Corruption from the ABS/PSM Hydraulic Control Unit

Fault Codes Observed

Multiple modules were logging faults simultaneously. That alone is a significant diagnostic signal.

Initial Assumptions

The fault pattern - erratic cluster behaviour, CAN communication errors, and a sensor fault - would lead most technicians toward one of three initial hypotheses:

• The instrument cluster itself had failed.
• There was a wiring fault, most likely in the CAN bus or at a sensor connector.
• One of the control modules had failed and was corrupting the bus.

The secondary air code (P0413) would typically be treated as unrelated and filed away. The rear right wheel speed sensor fault would point suspicion at the sensor, its wiring, or the reluctor ring. These are not unreasonable starting points. The problem is that they treat the fault codes as though they are the fault, rather than a description of effects.

What Was Tested

Over the course of the diagnosis, the following were replaced or tested:

• Instrument cluster - replaced, no change in behaviour
• Ignition switch - replaced, no change
• DME, immobiliser module, body control module - all replaced, no change
• Rear right ABS sensor - resistance checked and found to be within specification
• Wiring harness - continuity and insulation checks carried out, no fault found

This represents significant component substitution without resolving the underlying fault. At this point, the diagnostic approach needed to change direction.

What Didn't Add Up

Several things pointed away from the parts already replaced.

The instrument cluster sweep is a well-documented symptom of the cluster losing its CAN connection and resetting. Replacing the cluster does not fix a CAN problem - it simply installs a different node onto the same corrupted bus. The fact that replacement changed nothing confirmed the cluster was a victim, not the cause.

Replacing the DME, immobiliser, and body control module is similarly treating effects. If multiple modules are logging communication faults simultaneously, the bus itself is the problem, not the nodes on it. Swapping individual nodes on a corrupted bus will not resolve the underlying corruption.

The rear right wheel speed sensor reading within resistance specification is telling. A correct resistance measurement does not rule out a signal fault, but a wheel speed fault appearing alongside multiple CAN errors on a PSM-equipped car points more readily to the PSM module misreporting, or to a CAN message containing the wheel speed data being corrupted or absent.

The P0413 secondary air code is almost certainly a red herring - logged because the DME briefly lost communication with related modules and recorded the absence of confirmation from the air valve circuit.

The absence of any wiring fault found during conventional checks is consistent with an intermittent fault driven by electrical noise rather than a broken conductor.

Why the Fault Codes Were Misleading

Codes 5520 and 5522 confirm that CAN frames were missing or malformed. They do not identify which node was responsible for the corruption. Every module on the bus logged these, because every module was affected.

P1601 (CAN timeout, instrument cluster) was logged by the DME because the cluster had dropped off the bus and was no longer acknowledging messages. The cluster was not the source of the fault - it was a node that had been destabilised by the same bus corruption affecting everything else.

The rear right wheel speed sensor fault (4210) is perhaps the most misleading code in the set. The sensor itself was functioning correctly. The PSM module receives the sensor signal accurately - but when the PSM module is intermittently unable to transmit onto the CAN bus, the wheel speed data it should be sharing with the DME and cluster is absent. Those modules interpret the absence of data as a sensor fault and log accordingly. The sensor had nothing wrong with it.

P0413 is a pure cascade. The DME expected a CAN-communicated confirmation that never arrived, and logged the associated component as faulty. The secondary air valve was never the issue.

Breakthrough

With conventional component replacement exhausted, the diagnosis moved to functional testing at the system level. The ABS/PSM hydraulic control unit was disconnected. This removed it from the network in two distinct respects: as a CAN node, and as a high-current electrical load.

With the unit isolated, the cluster behaviour normalised, the CAN communication errors stopped appearing, and the wheel speed sensor fault ceased. The disconnection test had isolated the source - not just a software node on the network, but the device responsible for the electrical disturbance that was making the network unreliable in the first place.

On reconnection, the fault did not immediately return. This is consistent with intermittent behaviour driven by marginal supply conditions rather than a continuous hard fault. Confirming the unit as the source required load testing, not a simple reconnect check.

Root Cause: System-Level Explanation

The 986 PSM system uses a Bosch ABS 5.3 hydraulic control unit. This unit contains two distinct functional blocks: the hydraulic control module (the electronic control unit itself, which is a node on the CAN bus) and the hydraulic pump motor.

The pump motor is a high-current device. On a 12V vehicle system, it draws significant current when active - sufficient to cause measurable voltage sag on the supply rail if the electrical system has any weakness: an ageing battery, a marginal ground connection, or increased circuit resistance through corroded connectors.

CAN bus communication depends on stable differential signalling between CAN-H and CAN-L. The nominal differential voltage is 2V. When the supply rail drops suddenly under pump load, or when the pump generates electrical noise back into the supply, the reference level seen by CAN transceivers throughout the network shifts. More critically, this transient voltage drop and ground reference shift reduces the noise margin available to every CAN transceiver on the bus, leading to corrupted or lost frames. The bus controllers in each node have noise rejection built in, but they are not immune to supply-rail instability. A sufficient transient will cause a node to drop off the bus entirely, or to transmit malformed frames.

When the PSM module drops off the CAN bus - or transmits corrupted data - the following cascade occurs:

• The instrument cluster loses the CAN messages it depends on for gauge drive and warning light logic. It resets or sweeps.
• The DME logs a CAN timeout for the instrument cluster (P1601) because the cluster is no longer acknowledging messages.
• The PSM module itself logs CAN message missing (5522) and CAN data bus faults (5520) because it has lost contact with other nodes.
• Wheel speed data, transmitted over CAN from the PSM module to other control units, is absent or corrupted. The DME or cluster interprets this as a wheel speed sensor fault (4210) and logs accordingly.
• Secondary systems that depend on CAN-communicated status signals log their own faults (P0413) because expected confirmation messages never arrive.

The intermittent nature is explained by the pump duty cycle. The pump does not run continuously - it activates during ABS events, PSM interventions, or during the hydraulic self-test sequence the module runs at start-up. The fault would only present when the pump was active and the supply conditions were marginal enough for the resulting transient to corrupt the bus. On a cool morning with a freshly charged battery, the supply might be stiff enough to absorb the transient. On a warm evening after a long run, with a battery that has some age on it and ground connections with a little resistance, the same pump activation pushes the supply below the threshold at which CAN communication remains reliable.

Observed On-Track Behaviour

During on-track use, the fault manifested as a loss of controllability under heavy braking. The front axle locked heavily, while the driver reported a sensation of reduced braking effectiveness. With the front tyres locked, the vehicle had no lateral grip and ran straight on under braking.

This behaviour is consistent with a loss of ABS/PSM modulation rather than a loss of braking force. From a driver perspective, this can feel like a loss of braking, when in reality it is a loss of controllability due to sustained wheel lock.

Key Takeaways

• The ABS/PSM hydraulic control unit is a CAN node. Faults within it, or on its supply, can corrupt the entire network.
• Multiple simultaneous DTCs across unrelated systems are almost always a bus-level or supply problem, not multiple coincident component failures.
• A wheel speed sensor DTC on a PSM car does not confirm the sensor has failed. It may mean the PSM module is not transmitting the data correctly.
• Replacing CAN nodes that are logging faults does not fix a corrupted bus. It replaces the victims.
• Resistance checks do not diagnose intermittent electrical faults under load. Load testing under operational conditions is required.
• P0413 secondary air code was a cascade effect - a communication absence masquerading as a component fault.
• Intermittent faults that respond to conditions (temperature, battery state, drive cycle) point to marginal supply or ground, not broken wiring.

Recommended Next Steps

1. Load-test the ABS/PSM module supply and ground under pump activation. Measure voltage at the module connector, not at the battery, with the pump running. A drop of more than 0.5V into the module warrants further investigation.
2. Inspect and clean all ground connections associated with the ABS/PSM unit - both chassis grounds and any shared grounds with the CAN network. The 986 ground distribution is detailed in the Sheet 17 group of the 986 wiring documentation.
3. Battery condition test. An ageing battery with elevated internal resistance will compound any marginal ground or supply issue significantly.
4. If supply and grounds test satisfactory, the pump motor itself should be considered. Worn brushes or a developing short within the motor can increase current draw substantially, generating larger transients on an otherwise healthy supply.
5. Before fitting a replacement ABS/PSM unit, confirm all supply and ground paths are good. A replacement unit installed onto a marginal supply will present the same symptoms.
6. Clear all stored DTCs after repair and run the module through a full ignition cycle including the ABS self-test sequence. Confirm no CAN errors are logged before closing the job.

Related Diagnostic Codes

The codes associated with this fault are documented in the EBD OBD-II reference. When encountered in isolation, each of these codes points toward a different system - which is precisely what makes this fault pattern difficult to resolve without a system-level approach.

See the OBD-II fault code reference for full code descriptions and diagnostic context.