B16A2 – Lost communication with pedestrian protection sensor bus (right) (Lexus)

B16A2 means your Lexus ES lost communication with the right-side pedestrian protection sensor bus. In plain terms, the car cannot reliably “talk” to part of the pedestrian impact detection system. The real-world effect is reduced or disabled pedestrian protection function, plus warning messages or stored body codes. According to Lexus factory diagnostic data, this is a manufacturer-specific code defined as “Lost communication with pedestrian protection sensor bus (right).” Because Lexus controls the network layout by platform, treat this code as a direction for testing. Do not treat it as proof that any sensor or module failed.

B16A2 Quick Answer

B16A2 on a Lexus ES sets when the body-side network cannot receive expected messages from the right pedestrian protection sensor bus. Start by verifying power, ground, and connector integrity to the right-side bus components before replacing any sensor.

What Does B16A2 Mean?

Official definition: “Lost communication with pedestrian protection sensor bus (right).” That means a controlling ECU on the Lexus ES stopped seeing data from the right-side pedestrian protection sensor network. In practice, the system may disable pedestrian protection features and log a communication fault for later diagnosis.

What the module is checking: the ECU monitors network message presence, timing, and plausibility from the right-side pedestrian protection sensor bus. Why it matters: communication-loss DTCs usually come from power/ground faults, wiring damage, connector corrosion, or a bus short. They do not confirm a failed sensor. Per SAE J2012-DA guidance, the DTC points to a suspected area. You must find the root cause with testing.

Theory of Operation

Under normal operation, the Lexus pedestrian protection system uses impact sensors and related circuitry to detect certain front-end impacts. The system then shares status and event data over a dedicated sensor bus. One or more control modules use those messages to make safety decisions and to set warnings.

This code sets when the ECU expects right-bus messages but sees a dropout. A bus short, an open circuit, or low voltage at a bus node can stop message traffic. A loose connector can also create a high-resistance fault that only fails during vibration. The ECU then flags a communication loss for the right-side sensor bus to guide diagnosis.

Symptoms

Communication-loss faults usually show up first on the scan tool and then as safety-system warnings.

• Scan tool behavior Right-side pedestrian protection sensor bus data missing, intermittent, or a related ECU may not respond
• Warning message Pedestrian protection, SRS, or body warning displayed depending on Lexus configuration
• Stored DTCs Additional communication or “lost message” codes in related body/safety modules
• System disablement Pedestrian protection function limited or turned off until faults clear
• Intermittent fault Code returns after bumps, rain, or temperature changes
• Event data blocked System may not record or broadcast expected sensor status on the right bus

Common Causes

• Open or high-resistance in the right sensor-bus harness: A broken conductor or internal corrosion increases resistance and stops data from reaching the network gateway.
• Poor terminal fit at the right pedestrian protection sensor bus connector: Spread pins, fretting, or bent terminals create intermittent contact that drops messages under vibration.
• Water intrusion in the right-side front harness routing: Moisture wicks into connectors and causes corrosion that disrupts bus signal integrity.
• Loss of power feed to the right-side pedestrian protection sensor bus components: A blown fuse, poor power distribution connection, or relay issue removes module bias and the bus goes silent.
• High-resistance ground on the right-side sensor bus circuit: A weak ground point passes a static continuity test yet fails under load, causing resets and lost communication.
• Short to ground or short to battery on a bus line: A rubbed-through harness or pinched loom forces the network line to an invalid state and blocks messaging.
• Connector damage from prior bumper or front-end service: Improper reconnection, pin push-out, or harness strain after repairs commonly triggers communication loss on the Lexus ES.
• Faulty node on the right pedestrian protection sensor bus: A single sensor or bus interface can hold the network down or stop transmitting, but you must prove it with isolation testing first.

Diagnosis Steps

Use a bidirectional scan tool that can run a full network scan and show module status. Have a DVOM, a test light or fused jumper for loading circuits, and back-probing tools. An oscilloscope helps for bus integrity checks. Use Lexus service information to identify the exact right-side bus wiring, power feeds, grounds, and connector locations for your ES.

1. Confirm DTC B16A2 and run a complete health check. Record freeze frame data for communication faults, including ignition state, vehicle speed, battery voltage, and all related network or body DTCs. Freeze frame shows the exact conditions when the code set. Use a scan-tool snapshot later to catch an intermittent drop during a wiggle test or road test.
2. Before any pin testing, check whether the involved modules appear on the scan tool network scan. Note any modules that show “no communication” or “not equipped.” Then check fuses and power distribution that feed the pedestrian protection system and related body/network circuits. A communication bus cannot operate without correct power feeds.
3. Verify power and ground at the module(s) that manage or interface with the right pedestrian protection sensor bus. Use voltage-drop testing under load, not continuity alone. Load the circuit with the module connected and operating. Keep ground drop under 0.1V with the circuit active. A high-resistance ground can pass a static test and still reset the node.
4. Inspect the right-side harness routing and connectors tied to the pedestrian protection sensor bus. Focus on front bumper areas and any points that see flexing or previous repair. Look for pinched loom, rubbed insulation, water trails, green corrosion, terminal push-out, and loose connector locks. Repair obvious physical damage before deeper testing.
5. Check for related codes that change your test direction. A voltage supply code, a ground code, or a “bus off” type network code often identifies the primary fault. If multiple communication codes set together, treat it as a shared power/ground or network backbone issue first. If only B16A2 sets, focus on the right-side branch and its nodes.
6. With ignition ON, measure communication line bias at the suspect bus circuits at an accessible connector. Do not use ignition-off readings as a reference. Communication networks only show valid bias when powered. If the bias is missing, return to power/ground and fuse checks. If bias exists, move to integrity and isolation checks.
7. Check the bus circuits for shorts and unwanted resistance. Key off and disconnect the affected branch as Lexus service information allows. Test for short to ground and short to battery on each bus line. Then check for abnormal resistance that suggests a partial short or corrosion. Avoid “beep tests” as your only proof. Use meter readings and compare left-to-right branch behavior when possible.
8. Perform an isolation test to locate a single node that collapses the right bus. Disconnect one right-side sensor or branch connector at a time while monitoring scan-tool communication status. When communication returns, you found the branch that contains the fault. Do not replace the disconnected component yet. Confirm by reconnecting it and watching the fault return.
9. If the scan tool supports it, monitor relevant data PIDs and module status while you stress the harness. Use a controlled wiggle test at the right-side connectors and along the bumper harness. Trigger a scan-tool snapshot during the test to capture the moment communication drops. Compare that moment to battery voltage changes to separate a power event from a bus integrity event.
10. Repair the verified root cause. Clear codes and run another complete network scan. Cycle ignition and recheck for pending versus stored results. Many body communication faults act like continuous monitors. A hard fault usually returns immediately on key-on. Confirm the right-side pedestrian protection sensor bus remains online through a road test and a final health check.

Professional tip: When B16A2 points to a right-side pedestrian protection sensor bus, treat it like a branch network problem first. Prove power and ground with voltage-drop under load. Then isolate the branch by unplugging nodes one at a time. This method prevents the common mistake of replacing a sensor that only “stops talking” because the harness or ground cannot support it.

Possible Fixes

• Restore power feed to the right-side pedestrian protection bus: Replace the blown fuse or repair the power distribution fault after you confirm the cause of the overload.
• Clean, repair, and re-pin affected connectors: Correct terminal tension, remove corrosion, and repair pin push-out, then verify stable communication during a wiggle test.
• Repair harness damage in the right-front routing: Fix chafed wires, pinched loom, or water-intrusion paths and re-secure the harness to prevent repeat failures.
• Repair ground integrity for the involved node(s): Service the ground point and confirm less than 0.1V drop under load with the circuit operating.
• Replace a proven failed right-side bus node: Replace the specific sensor/module only after isolation testing shows it collapses the bus and wiring checks pass.
• Correct improper installation after collision or bumper service: Reseat connectors, restore correct routing, and verify all right-side pedestrian protection components appear on the network scan.

Can I Still Drive With B16A2?

You can usually drive a Lexus ES with B16A2 because it flags a communication loss, not an engine control failure. Treat it as a safety-system fault, not a convenience code. If the pedestrian protection system cannot “see” the right-side sensor bus, the vehicle may disable that function and store a warning message. Drive normally, but avoid relying on any pedestrian impact mitigation features until you fix the fault. If you also see SRS warnings, collision-related DTCs, or recent front-end damage, stop and diagnose first. Communication faults often worsen with vibration, water intrusion, or low system voltage.

How Serious Is This Code?

B16A2 ranges from an inconvenience to a real safety concern, depending on what the Lexus platform ties to the right pedestrian protection sensor bus. When the bus drops out due to a loose connector or low battery voltage, you may only get an intermittent warning and stored history. When the bus stays offline, the pedestrian protection function can remain disabled. That raises risk in a pedestrian impact event. This code does not usually affect drivability, shifting, or braking feel. Still, treat it as high priority after any bumper, grille, or front harness work. If any SRS indicator stays on with B16A2, treat the restraint system as potentially compromised and use SRS-safe procedures.

Common Misdiagnoses

Technicians often replace the right-side pedestrian protection sensor or a control module before checking network basics. That mistake happens because the scan tool text sounds like a “bad sensor.” B16A2 only proves the network message stopped. It does not prove the sensor failed. Another common error involves ignoring power and ground integrity under load. A sensor can “look powered” with a meter, yet drop offline when current flows through a corroded splice. Shops also miss water intrusion at the right front connector after bumper repairs. DIY owners often clear codes repeatedly, which erases freeze-frame context and delays finding an intermittent open. Start with bus continuity, connector tension, and voltage-drop checks.

Most Likely Fix

The most frequently confirmed repair direction involves restoring reliable connectivity on the right pedestrian protection sensor bus. Focus first on the right front harness routing, connector pin fit, and any impact or water damage near the bumper area. Cleaning and repairing terminal tension, correcting a backed-out pin, or repairing an open/high-resistance wire often resolves B16A2. If you confirm correct power, ground, and network integrity at the sensor and the bus still stays silent, then suspect the right-side sensor or a network gateway module. After repairs, road-test long enough to prove the fault does not return under vibration and temperature change. Enable criteria vary by Lexus system, so verify with service information.

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 3, 2026