U114F – Lost communication with power integration module missing message (Toyota)

Toyota-specific code — factory diagnostic data

U114F means the blind spot monitoring system lost a required message from the power integration module. In plain terms, Toyota may disable some driver-assist functions, show a warning, or store related network faults until communication returns. According to Toyota factory diagnostic data, this code means lost communication with power integration module missing message. On a Yaris or Yaris Cross, that does not prove a failed module. It tells you the Blind spot monitor (BSM) B did not receive an expected network message within the allowed time. The real job now is to confirm whether the problem comes from power, ground, wiring, connectors, network integrity, or the sending module itself.

U114F Quick Answer

U114F sets when Toyota’s Blind spot monitor (BSM) B stops receiving an expected message from the power integration module. Treat it as a communication fault first, not as proof that either module has failed.

What Does U114F Mean?

The official Toyota definition says lost communication with power integration module missing message. That means BSM B expected data from the power integration module and did not see it when it should. In practice, the blind spot system may lose needed status information and suspend normal operation.

Technically, this is a manufacturer-specific Toyota network code. The module does not measure a bad sensor signal here. It checks for the presence and timing of a required serial data message. If your scan report includes the FTB subtype -87, use it as diagnostic subtype information only. On this fault, it points to a missing message condition. That matters because diagnosis must focus on communication path integrity, module power and ground, and message availability, not immediate parts replacement.

Theory of Operation

Under normal conditions, Toyota networked modules share operating data across the vehicle communication system. The power integration module provides information that other modules may need for coordinated functions, wake-up logic, or system status. Blind spot monitoring depends on those shared messages to decide when it can operate normally and when it must set a fault.

This code sets when that message flow breaks down. The problem can come from a sender that drops offline, a receiver with unstable power, high resistance at a connector, or a network issue that blocks or delays traffic. Toyota uses general U-code wording by design, so the code identifies the trouble area, not the failed part. You must confirm which module or circuit segment lost communication before you replace anything.

Symptoms

Symptoms usually center on network communication loss and blind spot system availability.

• Scan tool behavior: BSM B may show U114F as current or history, and the power integration module may respond intermittently or not appear consistently on the ECU list.
• Warning message: The vehicle may display a blind spot monitor warning or a message that the driver-assist system is unavailable.
• Feature disabled: Blind spot monitoring may stop operating until the communication path returns.
• Intermittent fault: The warning may come and go after startup, during bumps, or with temperature changes.
• Multiple network codes: Other Toyota modules may store communication DTCs if the same message loss affects more than one controller.
• No obvious drivability issue: The vehicle may drive normally even though the ADAS system has shut down.
• Startup-related issue: The fault may appear during key-on if one module wakes up late or loses stable power.

Common Causes

• Power integration module offline: If the power integration module loses power, ground, or internal startup function, the BSM cannot receive its expected network message.
• CAN bus open circuit: An open in either network wire can block message traffic between Toyota modules and trigger a missing message fault.
• CAN bus short to power or ground: A shorted communication line can pull the network out of its normal bias state and stop valid data exchange.
• Poor module power feed: A weak fuse connection, relay feed issue, or high resistance in the supply path can let a module wake up inconsistently and drop off the network.
• High-resistance ground connection: Corrosion or a loose ground point can cause the module to reset under load and miss scheduled communication messages.
• Connector corrosion or terminal spread: Damaged terminals at the power integration module, BSM, or inline junctions can interrupt CAN signals or module power.
• Harness damage in a shared network section: Chafed, pinched, or water-damaged wiring in a common Toyota network branch can affect multiple modules at once.
• Aftermarket electrical equipment interference: Added trackers, alarms, remote start systems, or accessory wiring can disturb CAN communication or backfeed a module circuit.
• Intermittent module reset event: A module that repeatedly reboots from internal fault or unstable supply voltage can create a missing message code without a hard bus failure.

Diagnosis Steps

You need a capable scan tool with full Toyota network access, a quality digital multimeter, wiring diagrams, and preferably a lab scope. Use the scan tool to review network topology, freeze frame, and related codes. For this communication fault, freeze frame data matters most for vehicle speed, ignition state, and any companion network DTCs.

1. Confirm U114F in Blind spot monitor (BSM) B. Record whether the code shows as pending, current, history, or confirmed. Save freeze frame and note vehicle speed, ignition state, and related DTCs in other modules. Freeze frame shows the exact conditions when the code set. A scan tool snapshot serves a different purpose. Use a snapshot during a drive or wiggle test if the fault acts intermittent.
2. Run a full vehicle network scan before touching connectors. Check whether the power integration module appears on the scan tool module list. Then inspect the related fuses, fusible links, and power distribution paths that feed the networked modules. If the module does not report on the network, treat that as a primary clue.
3. Verify module power and ground under load. Do not rely on continuity or unloaded voltage alone. Backprobe the power integration module and any shared feed to the BSM if the diagram calls for it. Perform voltage-drop tests with the circuit operating. Ground drop should stay below 0.1 volt under load. A weak ground or supply can let the module wake up, then reset and disappear.
4. Inspect connectors and harness routing at the power integration module, BSM, junction connectors, and any exposed harness sections. Look for water entry, backed-out terminals, loose fit, corrosion, terminal spread, rub-through, and signs of previous repair. Pay close attention to areas near body seams, kick panels, and accessory wiring taps.
5. Check for related Toyota communication codes in other modules. If several modules report lost communication with the same module, focus on that module’s power, ground, and network branch first. If only BSM B stores U114F, compare live network status and message reception data, if available, to see whether the issue sits in the BSM side or upstream.
6. With ignition off and the battery disconnected, measure CAN resistance between CAN+ and CAN- at an accessible module connector on the affected network. A healthy bus reads about 60 ohms because two terminating resistors sit in parallel. An open on one conductor often moves the reading toward 120 ohms or OL. A very low reading points toward a shorted network.
7. Reconnect the battery and switch ignition on. Then check CAN bias voltage to ground on both communication lines. Measure with ignition on only, because network bias voltage does not provide a valid reference with the circuit unpowered. On a healthy resting bus, both CAN lines sit near 2.5 volts to ground. A line pinned high, pinned low, or far out of balance indicates a short or loaded bus.
8. If access allows, use a scope to compare network activity at the power integration module and at the BSM side of the circuit. You want to know whether messages reach the branch and whether the signal collapses under vibration or load. This step helps separate a wiring fault from a module that drops offline internally.
9. Perform targeted wiggle testing on the harness and connectors while watching network status, module presence, and live data on the scan tool. If the module disappears, resets, or the code flips current during movement, isolate that section and repair the connection fault before considering any control unit replacement.
10. After repairs, clear codes and run another full network scan. Confirm that the power integration module now communicates normally and that BSM B no longer logs U114F. Drive the vehicle through the freeze-frame conditions when possible. Recheck for pending and confirmed codes. A hard communication fault usually returns quickly on key-on if the problem remains.

Professional tip: The FTB suffix -87 adds subtype detail only. Use it as diagnostic direction, not as proof of a failed module. On Toyota network faults, a missing message code tells you what the BSM did not receive. It does not tell you why the message went missing. Prove power, ground, connector integrity, and CAN health before you condemn the power integration module or the BSM.

Possible Fixes

• Repair the verified power or ground fault: Restore the affected fuse feed, relay output, splice, or ground connection after voltage-drop testing identifies the weak point.
• Repair CAN wiring damage: Fix any confirmed open, short, or high-resistance section in the communication pair and protect the harness against repeat chafing or water entry.
• Clean and correct connector faults: Remove corrosion, tighten terminal tension, reseat loose pins, and repair any backed-out or spread terminals at affected Toyota module connectors.
• Remove aftermarket network interference: Disconnect or properly integrate added accessories that disturb CAN traffic, backfeed circuits, or interrupt module wake-up.
• Repair shared junction or splice issues: Restore continuity and terminal integrity in any confirmed junction connector or network splice that serves the power integration module or BSM branch.
• Update or initialize module software if service information calls for it: Follow Toyota procedures only after the electrical and network circuits pass testing.
• Replace the failed module only after circuit proof: Install a module only when power, ground, network integrity, and connector condition all test good and the module still drops offline or fails to communicate.

Can I Still Drive With U114F?

You can usually drive a Toyota with U114F if the vehicle otherwise operates normally, but you should not ignore it. This code tells you the blind spot monitor module lost the expected message from the power integration module. That can disable blind spot warning functions, suppress related alerts, or trigger warning lamps and message-center notices. Basic engine operation often remains normal, because this is a network communication fault, not a direct fuel or ignition fault. Even so, this is not a harmless code on a vehicle that depends on ADAS features for situational awareness. If lane-change support, rear cross traffic functions, or related monitoring features stop working, your risk increases in traffic. Drive only if the vehicle has no other critical warnings and no major drivability symptoms. Confirm system operation manually, use mirrors and shoulder checks, and schedule diagnosis promptly.

How Serious Is This Code?

U114F ranges from an inconvenience to a meaningful safety concern, depending on what Toyota systems lose support when that message drops out. In many cases, the vehicle still drives normally and the main effect is a blind spot monitor warning, stored code, and loss of convenience or driver-assist features. That makes it less urgent than a hard powertrain or brake fault, but not minor. On a Yaris or Yaris Cross with active blind spot monitoring, this code can compromise ADAS performance. Treat that seriously if the driver relies on mirror indicators or cross-traffic alerts. Any repair that involves ADAS modules, radar-related components, networked body electronics, or module replacement may require calibration, initialization, or registration with Toyota-capable scan equipment before the system is safe to trust again. Do not assume a cleared warning means the feature now works correctly. Verify communication, run functional checks, and confirm any required Toyota procedure after repair.

Common Misdiagnoses

Technicians often replace the blind spot monitor module first because that is the module that stored the code. That wastes money. U114F only tells you the BSM B module did not receive the required message. It does not prove the BSM failed, and SAE J2012 makes that point clear for communication codes. Another common mistake is ignoring the power integration module because it still responds on the scan tool. A module can stay online and still miss one message stream due to poor power, poor ground, connector spread, water intrusion, or network errors under load. Shops also miss intermittent faults by checking battery voltage with no load and skipping voltage-drop tests. Some clear the code and road test briefly, then call it fixed before the Toyota enable criteria run again. The cure is simple: scan every related module, compare code direction, verify powers and grounds under load, inspect connectors closely, and confirm network integrity before replacing anything.

Most Likely Fix

The most common confirmed repair direction is restoring reliable communication between the power integration module and the blind spot monitor network path. That often means repairing a loose, corroded, water-damaged, or partially backed-out connector, or correcting a power or ground fault at the module that stopped sending the expected message. The next likely repair direction is harness repair where body wiring flexes or moisture collects. Module replacement comes later, not first. If testing proves the power integration module drops offline, loses a required output, or fails to transmit the expected message while power, ground, and network circuits stay correct, then module replacement and Toyota-specific setup become justified. After any repair, drive long enough for the system monitor to run. Enable criteria vary by Toyota platform, so use service information to confirm when the relevant communication check has completed.

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