U112B – Interrupted communication with Central Electronic Module (CEM), Bus signal/message faults, Message missing (Volvo)

Volvo-specific code — factory diagnostic data

U112B means the power steering control module has stopped receiving an expected message from the Central Electronic Module on a Volvo XC40. In real use, that can trigger steering-related warnings, network faults, or feature dropouts even if the vehicle still drives. According to Volvo factory diagnostic data, this is a manufacturer-specific code for interrupted communication with the CEM, with a bus signal or message fault described as message missing. The FTB subtype -87 matters here. It identifies a missing message condition, not a direct short or sensor failure. That distinction points your diagnosis toward network communication, module power and ground, connector integrity, and message flow verification before any module replacement.

U112B Quick Answer

U112B sets when the PSCM does not receive a required CEM message over the vehicle network. On a Volvo, that usually means a communication interruption, missing network traffic, or a power, ground, wiring, or connector problem affecting one of those modules.

What Does U112B Mean?

The official Volvo definition says interrupted communication with the Central Electronic Module, bus signal or message faults, message missing. In plain English, the PSCM expected to hear from the CEM and did not. That matters because the steering module depends on shared network information to make correct control decisions and to coordinate with other vehicle systems.

What the PSCM actually checks is message presence and timing on the network. It does not directly prove the CEM has failed. SAE J2012-DA U-code wording stays general by design, and the -87 subtype only narrows the fault to a missing message condition. For diagnosis, treat this code as a suspected trouble area. Then confirm whether the message vanished because of a network interruption, a CEM issue, a PSCM issue, or a power or ground fault that stopped either module from communicating.

Theory of Operation

Under normal conditions, the Volvo CEM acts as a central traffic manager for many body and network functions. The PSCM listens for specific CEM messages and uses them as part of its operating strategy. Those messages may include status, authorization, configuration, and coordinated system data. The exact message set varies by Volvo platform, so service information must confirm which network path and message the PSCM expects on the XC40.

This code sets when that expected message does not arrive within the allowed time window. A missing message can come from several different failures. The CEM may drop offline. The PSCM may lose the ability to hear the bus. Wiring damage, connector spread, corrosion, low system voltage, or another network fault can also interrupt traffic. That is why this code never proves a bad module by itself. You must verify network integrity and module power and ground first.

Symptoms

Communication loss with the CEM often shows up as a network pattern, not as one isolated steering complaint.

• Scan tool behavior: The CEM or PSCM may respond intermittently, drop off the module list, or show multiple communication codes.
• Warning messages: The driver may see steering, chassis, or general electrical system warnings in the cluster.
• Steering assist change: Power steering assist may reduce, become inconsistent, or enter a limited operating mode.
• Feature dropouts: Other body or convenience functions may act erratically if they depend on CEM network traffic.
• Intermittent fault pattern: The problem may appear during startup, low voltage events, or after hitting bumps.
• Multiple stored U-codes: Several modules may log missing-message or communication faults at the same time.
• No-start or wake-up issues: In some cases, the vehicle may show abnormal wake-up behavior or delayed module communication after key-on.

Common Causes

• Intermittent loss of CEM network messages: The PSCM sets U112B when expected Central Electronic Module traffic drops out long enough to flag a message missing fault.
• Poor CEM power or ground feed: Voltage loss at the Central Electronic Module can interrupt message transmission without leaving the module completely offline.
• High resistance in CAN network wiring: Corrosion, fretting, or partially damaged wiring can distort bus signals and make CEM messages unreadable to the PSCM.
• Loose or contaminated connector terminals: Terminal spread, moisture, or oxidation at the CEM, PSCM, or network junction can create an erratic communication loss.
• Network short to power or ground: A short on either communication line can collapse normal bus bias and block message exchange between Volvo control modules.
• Open circuit in one CAN conductor: A break in CAN high or CAN low can leave some communication active while causing missing-message faults in specific modules.
• Aftermarket electrical equipment interference: Spliced accessories, trackers, remote start hardware, or non-OEM repairs can disturb the XC40 network and interrupt CEM traffic.
• PSCM power or ground instability: The steering control module may falsely report missing CEM messages if its own supply or ground drops out under load.
• CEM internal fault or software issue: Internal module failure or corrupted logic can stop or corrupt the specific messages the PSCM expects to receive.

Diagnosis Steps

Use a professional scan tool with full Volvo network access, a quality digital multimeter, and wiring information for the XC40 platform. A lab scope helps with intermittent bus faults. You also need basic terminal inspection tools. Avoid continuity-only testing. This fault demands scan data review, loaded power and ground checks, and network integrity testing.

1. Confirm U112B in the PSCM and record all stored, pending, and history codes. Save freeze frame data, especially vehicle speed, ignition state, and related network DTCs. Review whether the fault appears current or intermittent. Freeze frame shows when the code set. A scan tool snapshot serves a different job. Use a manual snapshot during a road test if the concern happens intermittently.
2. Run a complete network scan before touching connectors. Check whether the CEM appears on the scan tool network list and whether other modules also report missing CEM messages. Inspect relevant fuses and main power distribution feeds first. A communication code often starts with lost module power, not a failed bus line.
3. Verify PSCM and CEM power and ground under load. Do not trust static battery voltage readings or simple continuity checks. Perform voltage-drop testing with the circuit operating. Ground drop should stay below 0.1 volt under load. If a feed or ground drops excessively, repair that fault before any bus diagnosis.
4. Inspect the CEM, PSCM, and accessible network connectors closely. Look for backed-out terminals, corrosion, water intrusion, terminal spread, overheated pins, and harness damage near brackets or pass-through points. On Volvo vehicles, a connector can look seated yet still have poor terminal tension. Correct any obvious connection issue before deeper testing.
5. With ignition off and the battery disconnected, measure resistance between CAN high and CAN low at an accessible network connector. A healthy terminated bus typically reads about 60 ohms. A reading near 120 ohms or open circuit points toward an open leg or missing termination. A very low reading suggests a shorted network segment or module.
6. Reconnect the battery and switch ignition on. Check CAN high and CAN low bias voltage to ground at an accessible point. Perform this test only with the network powered. Ignition-off voltage readings do not provide a valid reference. On a healthy CAN network, both lines usually sit near 2.5 volts at rest. A line pulled high, low, or flat often exposes a short or loaded bus.
7. Compare scan data from the PSCM with network status from other modules. Look for loss of steering-related data, repeated CEM resets, or multiple message-missing faults that occur together. If only the PSCM reports U112B, focus on the PSCM branch, connector quality, and local power or ground stability. If many modules report CEM message loss, shift attention toward the CEM or main network backbone.
8. If the fault remains intermittent, wiggle-test the harness and connectors while monitoring network status and module communication. Watch for the CEM dropping off the scan tool, steering assist warnings, or sudden data interruptions. Follow with a road test and capture a scan tool snapshot during the event. That snapshot helps isolate whether vibration, steering load, or ignition state triggers the dropout.
9. Check for evidence of aftermarket wiring, previous collision repair, or non-factory splices near module power feeds and network wiring. Remove or isolate suspect add-on equipment if it shares power or communication circuits. Many intermittent Volvo communication faults trace back to disturbed wiring rather than a failed control module.
10. After you repair the verified cause, clear all codes and repeat the network scan. Confirm the CEM stays online, the PSCM no longer logs U112B, and related functions operate normally. Perform a key cycle and road test. Recheck for pending or returning communication faults before releasing the vehicle.

Professional tip: The FTB suffix -87 matters here because it identifies a message missing subtype, not a direct command to replace the CEM or PSCM. Treat U112B-87 as proof that expected network traffic disappeared. Then prove why it disappeared. On the XC40, that usually means checking module power, grounds, connector integrity, and bus health before you condemn any control unit.

Possible Fixes

• Repair power supply faults: Restore proper fused feeds, ignition feeds, or ground connections to the CEM or PSCM after voltage-drop testing confirms excessive loss.
• Clean and secure network connectors: Correct terminal tension problems, corrosion, moisture intrusion, or partially seated connectors at the CEM, PSCM, or network junction points.
• Repair damaged CAN wiring: Fix open circuits, shorted conductors, chafed harness sections, or high-resistance network wiring that testing has verified.
• Remove aftermarket wiring interference: Eliminate non-factory splices or accessories that load, interrupt, or backfeed the Volvo communication network.
• Restore proper network termination: Correct a missing or compromised terminating path if resistance testing shows an open termination condition.
• Update or configure module software: Perform Volvo-approved software correction only after power, ground, and network circuits pass testing and service information supports that step.
• Replace the failed module only after proof: Replace the CEM or PSCM only when testing confirms correct external circuits and the module still drops messages or communication.

Can I Still Drive With U112B?

You can sometimes drive a Volvo XC40 with U112B, but you should not treat it as harmless. This code means the PSCM lost a required message from the Central Electronic Module. The FTB subtype -87 identifies a message missing condition, not a confirmed failed part. If steering assist feels normal and no warning messages appear beyond a stored code, the fault may be intermittent and the vehicle may remain drivable for short trips. Stop using the vehicle right away if steering effort changes, multiple network warnings appear, or other modules drop offline. The CEM sits at the center of many Volvo network functions. A communication fault there can spread beyond power steering logic. Drive only after you confirm basic operation, and prioritize diagnosis before the fault becomes a no-start, reduced-function, or steering-assist complaint.

How Serious Is This Code?

The seriousness depends on whether U112B stands alone or appears with broader network faults. In the mildest case, it acts like an inconvenience. You may see a stored code with no active symptom because the PSCM briefly missed one CEM message during low voltage, startup instability, or a connector interruption. The risk rises fast when the code returns current, sets active warnings, or accompanies steering-related messages. On a Volvo, the PSCM relies on stable network traffic to make correct assist decisions and to coordinate with other vehicle systems. If the CEM message stays missing, steering assist strategy may change or default. That creates a real drivability and safety issue, especially at low speed parking maneuvers or sudden avoidance inputs. Treat an active code as important. Treat it as urgent if steering feel changes, the vehicle logs multiple U-codes, or the scan tool loses communication with several modules.

Common Misdiagnoses

Technicians often replace the PSCM first because the code appears in that module. That wastes money. U112B only tells you what the PSCM detected. It does not prove the PSCM failed. Another common mistake is blaming the CEM without checking power supply stability, fuse feeds, grounds, and connector fit at both modules. Volvo network faults often start with low system voltage, water intrusion, terminal spread, or harness strain near module connectors. Some shops also clear codes and road test once, then assume the fault is gone. Intermittent message-missing faults need repeatable verification. Check whether the scan tool can communicate with the CEM, review network-related companion codes in every module, inspect shared powers and grounds under load, and verify that live data from the CEM stays present before any module replacement decision.

Most Likely Fix

The most common confirmed repair direction is restoring reliable communication between the PSCM and the CEM, not replacing parts on the first visit. That usually means correcting a power, ground, connector, or network wiring fault that interrupts message flow. On some Volvo cases, battery voltage instability or poor terminal contact triggers the missing-message event, so charging-system and voltage-drop checks matter early. If testing proves the CEM drops offline, loses proper powers or grounds, or stops transmitting required data while the network wiring remains intact, then CEM-side repair or replacement becomes a valid path. If the PSCM alone loses the message while the rest of the network remains stable, focus on the PSCM connector, local harness, and module power and ground integrity first. After repair, confirm the fix over multiple drive cycles because monitor enable conditions vary by vehicle and system.

Repair Costs

Network and communication fault repairs vary by root cause — wiring/connectors are often the source, but module-level repairs or replacements can be significantly more expensive.

Last updated: April 11, 2026