U1106 – Lost communication with electric parking brake module (Toyota)

Toyota-specific code — factory diagnostic data

U1106 means your Toyota C-HR has a network communication problem with the electric parking brake system. In the real world, that can leave the parking brake warning on, disable auto-hold, or make the parking brake act inconsistently. According to Toyota factory diagnostic data, this manufacturer-specific code indicates the Main body module lost communication with the electric parking brake module. Because Toyota controls this code’s definition, the exact network path and module naming can vary by platform. Treat U1106 as a pointer to a communication breakdown, not proof that the parking brake module failed.

U1106 Quick Answer

U1106 sets when the Main body module cannot communicate with the electric parking brake module. Diagnose the network, power, grounds, and connectors before replacing any module.

What Does U1106 Mean?

Official definition: “Lost communication with electric parking brake module.” The Main body module expected to “see” the electric parking brake module on the vehicle network, but it did not. In practice, the C-HR may lose parking brake-related functions and store other network codes at the same time.

What the module is checking and why it matters: The Main body module monitors message traffic and module presence on the network. It sets U1106 when messages from the electric parking brake module stop arriving, arrive corrupted, or fail a timing expectation. That matters because you must prove whether the fault comes from lost power/ground to the parking brake module, an open/short in the network wiring, excessive resistance at a connector, or a broader network issue that affects multiple ECUs.

Theory of Operation

On Toyota networks, the Main body module acts as a central coordinator for body features. It communicates with other ECUs using network messages rather than direct switch-to-motor wiring. The electric parking brake module reports its status, accepts commands, and shares fault information over the network.

U1106 sets when that normal message exchange stops. A loss of module power, a weak ground, or high resistance in a connector can silence the electric parking brake module. A shorted network circuit, poor terminal tension, or water intrusion can also block messages. The code stays general by design, so diagnosis must determine whether the problem sits at the module, the wiring, or the shared network segment.

Symptoms

Communication-loss codes show up on the scan tool first, then as feature loss or warnings.

• Scan tool Electric parking brake module missing from the ECU list, or it drops offline intermittently during a health check
• Warning message Parking brake warning lamp or “EPB” warning displayed
• Auto-hold Auto-hold function inoperative or cancels unexpectedly
• Parking brake operation Parking brake does not apply or release as expected, or it requires repeated attempts
• Multiple U-codes Additional network communication DTCs stored in the Main body or other body-related modules
• Intermittent behavior Concern worsens with bumps, moisture, or after recent repairs near harness routing
• Stored history Code logs as history after low battery events or jump-starting

Common Causes

• Electric parking brake module power supply fault: A blown fuse, poor fuse contact, or failed relay removes module power and the network stops hearing it.
• High-resistance ground at the EPB module: Corrosion or a loose ground point lets the module boot but it resets under load and drops off the network.
• Open circuit in the communication line(s) between EPB and body network: A broken wire or backed-out terminal interrupts message traffic and triggers a lost communication DTC.
• Short to ground or short to battery on the communication circuit: A pinched harness or water intrusion can pull the line low or high and block network signaling.
• Connector pin fit or corrosion at the EPB module or junction connectors: Spread terminals and oxidation add resistance and create an intermittent “module missing” condition.
• Network junction, splice, or gateway issue: A fault at a Toyota network junction connector or gateway path can isolate the EPB module from the main body module.
• Battery voltage instability or low system voltage: Low voltage during cranking or jump-start events can reset the EPB module and set a communication loss code.
• Aftermarket electrical accessory interference: Poorly grounded accessories can inject noise or load a shared power/ground and disrupt module communications.
• Electric parking brake module internal fault: Internal power regulation or processor failures can stop the module from transmitting even when power and ground test good.

Diagnosis Steps

Use a scan tool that can run a Toyota full network scan and view body/chassis data. Have a DVOM, back-probe pins, and a test light or sealed-beam headlamp for load testing. Use basic hand tools for trim access. If you plan to check bus resistance, use a battery disconnect tool and follow memory-saver practices as needed.

1. Confirm U1106 in the Main Body module and save the report. Record freeze frame data if available, especially ignition state, vehicle speed, battery voltage, and any other network DTCs. Freeze frame shows conditions when the DTC set. Use a scan tool snapshot during a road test if the fault acts intermittent.
2. Run a full network scan and note whether the electric parking brake (EPB) module appears in the ECU list. If the EPB module does not report, treat the fault as an “offline module” problem first. If the EPB module reports, treat it as an intermittent communication drop and look for related history or pending codes.
3. Check DTC status as pending versus stored/confirmed. Many Toyota communication monitors behave like two-trip logic for intermittent faults. A pending code suggests a one-time dropout. A stored code that returns quickly points to a hard fault.
4. Inspect battery condition and charging system basics before deep testing. Verify clean battery terminals and solid body grounds. Then check for voltage instability during crank with scan data. Communication modules reset fast when voltage sags.
5. Check fuses and power distribution for the EPB and body network circuits before you measure at any ECU. Inspect each related fuse for a tight fit and heat damage. Confirm the fuse feeds with ignition ON using a test light. A fuse can look good and still fail under load.
6. Verify EPB module power and ground with voltage-drop testing under load. Turn ignition ON and command an EPB function if the scan tool allows. Measure voltage drop on the EPB power feed and ground while the circuit operates. Keep ground drop under 0.1V with the module powered and active.
7. Inspect the EPB module connector and the Main Body related connectors. Look for moisture, green corrosion, bent pins, spread terminals, and partial engagement. Perform a light tug test on each wire near the terminal. Repair pin fit problems before replacing parts.
8. Inspect the harness routing from the EPB module to the body harness. Focus on pinch points, seat tracks, under-console routing, and areas near grommets. Look for shiny rub-through, crushed loom, or prior repair splices. Correct any physical damage and re-secure the harness.
9. Perform communication circuit checks with ignition ON when you check bias voltages. Communication circuits need power to establish normal bias. Back-probe the communication line(s) at the EPB connector and compare to a known-good module circuit on the same network when possible. An obviously stuck-high or stuck-low reading points to a short, not a bad module.
10. If the platform uses a CAN-type link for this EPB communication path, measure bus resistance correctly. Turn ignition OFF and disconnect the battery. Measure resistance between CAN+ and CAN- at an accessible connector. A healthy network typically reads about 60 ohms. Readings near 120 ohms or OL suggest an open or missing termination, and very low resistance suggests a short.
11. Wiggle test to reproduce the dropout while monitoring the network list and data PIDs. Use a scan tool snapshot to capture the moment the EPB module goes offline. Move the harness and connectors in small sections. If communication drops during movement, you found a wiring or terminal issue, not a logic issue.
12. After repairs, clear codes and rerun a full network scan. Confirm the EPB module stays online through several key cycles and an EPB apply/release operation. Road test the Toyota C-HR and recheck for pending and stored U1106. Verification ends the diagnosis.

Professional tip: When U1106 sets in the Main Body module, prove the EPB module can stay powered and grounded under load before you chase network theory. Continuity checks often lie on this fault. A corroded ground can pass continuity, then fail when the EPB wakes up. Voltage-drop testing during an EPB command finds that problem fast.

Possible Fixes

• Restore EPB module power feed: Replace the failed fuse or relay only after you confirm the cause of the overload and verify proper load operation.
• Repair EPB ground path: Clean and tighten the ground point, repair corroded terminals, and confirm less than 0.1V ground drop under load.
• Repair communication wiring faults: Fix opens, shorts, or damaged shielding/twisted pair sections and confirm stable network readings afterward.
• Service connector pin fit and corrosion: Clean, de-pin, or replace terminals as needed and ensure full connector engagement and lock function.
• Correct network junction or splice issues: Repair loose junction connectors or compromised splices that isolate the EPB module from the body network.
• Address battery/charging instability: Correct weak battery, poor terminal contact, or charging issues that reset modules and trigger dropouts.
• Replace the EPB module only after testing: Replace the module only after power, ground, and network integrity tests prove the module stops communicating.

Can I Still Drive With U1106?

You can often drive a Toyota C-HR with U1106, but you should treat it as a brake-system communication warning, not a nuisance light. The Main Body ECU sets this code when it cannot communicate with the electric parking brake (EPB) module. If the EPB cannot apply or release on command, parking safety changes immediately. Avoid steep grades and tight parking situations until you confirm EPB operation. If the parking brake warning stays on, the EPB behaves unpredictably, or the vehicle reports a “parking brake malfunction,” stop driving and diagnose it. Do not assume the hydraulic service brakes will “cover” an EPB fault. This code can also appear with other network codes that change risk level.

How Serious Is This Code?

U1106 ranges from inconvenience to a real safety concern, depending on what the EPB does during the fault. If the EPB still applies and releases normally, the issue may be intermittent network dropouts or a power/ground problem that only occurs during certain conditions. That situation still needs repair, because communication loss can return without warning. If the EPB will not release, will not apply, or the vehicle enters a brake-related fail-safe, treat the vehicle as unsafe to operate. Communication DTCs use intentionally general wording per SAE J2012-DA. The code points to a suspected trouble area, not a failed part. Confirm the root cause with scan-tool communication checks, power and ground voltage-drop tests under load, and network integrity checks.

Common Misdiagnoses

Technicians often replace the EPB actuator or EPB module because the code “names” that module. U1106 does not prove the EPB module failed. It only proves the Main Body ECU lost messages. Another common error involves ignoring shared power and ground. A single weak ground splice or corroded connector can drop the EPB offline and set U1106. Many also miss the difference between “module offline” and “module present but setting its own DTCs.” If the scan tool cannot connect to the EPB module, start with power, ground, and network wiring at the EPB connector. If the scan tool can connect, look for internal EPB codes, bus errors, and intermittent connector fit issues before any parts.

Most Likely Fix

The most frequently confirmed repair direction for U1106 on Toyota platforms involves restoring reliable power, ground, and network connection to the EPB module, not replacing hardware first. Focus on connector pin fit, moisture intrusion, and harness damage at the EPB module and along its routing. Perform loaded voltage-drop tests on the EPB power and ground circuits while commanding EPB apply and release. If the EPB module stays offline on the scan tool after you confirm clean power, ground, and network continuity, then module failure becomes plausible. When replacement becomes necessary, Toyota-level scan tooling typically handles registration, calibration, and health checks. Verify the repair by road testing and cycling the EPB through multiple key cycles, since enable criteria for communication checks vary by system.

Repair Costs

Repair cost depends on whether the root cause is a wheel speed sensor, wiring, connector condition, or the hydraulic control unit. Start with electrical checks before replacing brake system components.

Last updated: April 9, 2026