B16A7 – Lost communication with pedestrian protection sensor bus (left) (Lexus)

B16A7 means your Lexus ES lost communication with the left pedestrian protection sensor bus. You may still drive normally, but the pedestrian protection function can stop working or get limited. According to Lexus factory diagnostic data, this code indicates “Lost communication with pedestrian protection sensor bus (left).” In plain terms, one control module cannot “see” the left-side sensor network it expects to hear from. That matters because the system relies on fast, consistent messages. When messages drop out, the module sets a communication loss DTC and may disable related protection features.

B16A7 Quick Answer

This Lexus-defined code means the vehicle can’t communicate with the left pedestrian protection sensor bus. Diagnose it like a network fault first: power, ground, connector integrity, and bus continuity before any parts.

What Does B16A7 Mean?

Official definition: “Lost communication with pedestrian protection sensor bus (left).” What the module detected: one module expected valid data from the left pedestrian protection sensor bus, but it did not receive it for a calibrated time. What it means in practice: the Lexus ES may disable or limit pedestrian protection related functions and store a body DTC.

What the module actually checks: it monitors network message presence, timing, and plausibility from the left-side pedestrian protection sensor bus. It does not “test” a single sensor directly with this DTC. Why that matters: a broken wire, weak ground, water intrusion at a connector, or a module that lost power can all look identical on the scan tool as “lost communication.” You must confirm bus power, ground, and signal integrity before you condemn any sensor or module.

Theory of Operation

On Lexus platforms, the pedestrian protection system uses a dedicated sensor bus for fast event reporting. Multiple devices share the bus, and one supervising ECU expects regular messages from the left-side network. Under normal conditions, each device powers up, joins the bus, and transmits status and event data at defined intervals.

B16A7 sets when the supervising module stops receiving those left-side bus messages. A shorted bus line, an open circuit, or a device that drags the network down can cause the dropout. Low supply voltage to a bus device can also create distorted messages. Intermittent connection issues often trigger this code after vibration, moisture, or temperature change.

Symptoms

B16A7 usually shows up as a communication problem first, then a feature limitation second.

• Scan tool Left pedestrian protection sensor bus devices may not appear, show “no communication,” or drop offline intermittently
• Warning message Pedestrian protection or related safety system warning on the cluster may appear
• Feature disabled Pedestrian protection function may switch off or show limited operation
• Stored history Code may store as current, then flip to history after a key cycle
• Intermittent behavior Symptoms may change with bumps, rain, or after a car wash
• Multiple DTCs Other body communication codes may set at the same time
• Failed self-check System may fail an initialization or self-test during startup

Common Causes

• Open circuit in the left pedestrian protection sensor bus wiring: A broken wire stops data flow and the Lexus module logs a lost communication fault.
• High resistance from corrosion at a left-side bus connector: Corrosion raises resistance and distorts the bus signal until modules drop off the network.
• Poor terminal tension or a partially backed-out pin: A loose terminal creates intermittent contact that looks like a momentary bus outage.
• Short to ground on a bus line: A grounded communication line collapses bias voltage and prevents normal message traffic.
• Short to battery voltage on a bus line: Battery feed on a signal line overwhelms the network and forces a no-communication condition.
• Shared power or ground fault for the left pedestrian protection sensor bus node: A weak feed or ground makes the node reset or go offline, even when wiring looks intact.
• Water intrusion in the left front harness path: Moisture wicks into wiring and connectors, then causes cross-talk, shorts, and intermittent opens.
• Physical harness damage near the left front bumper area: Impact damage, rubbing, or prior body repairs can pinch or cut the bus wiring.
• Faulty left-side bus node (sensor or interface module on that bus): An internal fault can stop the device from broadcasting, which the rest of the system reads as a communication loss.

Diagnosis Steps

Use a scan tool that can run a full Lexus network scan and display body/SRS-related data. Have a DVOM, back-probes, and a test light or load tool for circuit loading. Keep wiring diagrams and connector views ready. If available, use an oscilloscope to check bus signal integrity during a wiggle test.

1. Confirm B16A7 and record DTC status. Save freeze frame data and note ignition state, vehicle speed, battery voltage, and any related communication or body/SRS codes. Freeze frame shows when the fault set. Use a scan tool snapshot later to capture an intermittent dropout during a road test.
2. Run a complete network scan and check if the left pedestrian protection bus node(s) appear online. Note any “not equipped/not responding” entries and compare them to known equipment on the Lexus ES. If the scan tool cannot see multiple modules, diagnose the main network first.
3. Check fuses and power distribution that feed the pedestrian protection system and related body/SRS circuits. Verify fuse integrity with a loaded test. Do not rely on visual inspection alone. A fuse can pass continuity but fail under load.
4. Verify module and bus-node power and ground under load before probing signal circuits. Use voltage-drop testing while the circuit operates. Target less than 0.1 V drop on grounds. A high-resistance ground can pass a static voltage check and still cause dropouts.
5. Perform a focused visual inspection of the left front harness routing and connectors for this bus. Look for water intrusion, bent pins, backed-out terminals, and previous repair signs. Pay attention to areas near the bumper, inner fender, and any clips or brackets that can pinch wiring.
6. Disconnect and inspect connectors related to the left pedestrian protection sensor bus. Check for terminal spread, corrosion, and seal damage. Reseat connectors with positive engagement. If you find moisture, address the source and clean or repair terminals as needed.
7. With ignition ON, measure communication line bias voltage at a convenient connector on the left pedestrian protection sensor bus. Ignition-off readings do not apply because the bus bias only exists when powered. Compare the readings side-to-side between bus lines if the design uses a two-wire network. A stuck-high or stuck-low line points to a short or a module pulling the network down.
8. Isolate the fault by unplugging bus nodes one at a time, if service information allows safe disconnection. Cycle ignition and repeat the network scan after each change. If communication returns after unplugging a specific node, that node or its connector likely drags the bus down.
9. Check continuity and short-to-power/short-to-ground on the bus wiring only after you confirm proper power and ground. Use a meter to verify each bus line does not short to chassis ground or battery feed. Flex the harness during testing to locate intermittent opens.
10. If you have an oscilloscope, monitor the bus waveform with ignition ON during a wiggle test. Watch for dropouts, heavy noise, or a flat-line condition. Correlate the disturbance to harness movement or a specific connector.
11. After repairs, clear DTCs and rerun a full network scan. Perform a road test and use a scan tool snapshot to capture live data if the issue was intermittent. Confirm B16A7 does not return as pending or confirmed after the required drive cycle logic for this Lexus system.

Professional tip: Lost-communication faults often come from power or ground quality, not the data wires. Load-test feeds and perform voltage-drop checks first. When you suspect a bus pull-down, unplug nodes methodically and rescan each time. That approach prevents unnecessary sensor replacement and quickly identifies the device that takes the network offline.

Possible Fixes

• Repair open, shorted, or high-resistance wiring in the left pedestrian protection sensor bus circuit path.
• Clean, dry, and restore connector integrity on left-side bus connectors, then replace damaged terminals or seals as needed.
• Restore proper power or ground to the affected bus node by repairing fuse, splice, ground point, or feed wiring faults.
• Correct harness routing and protection to prevent future rubbing, pinching, or water intrusion.
• Replace the specific left-side bus node (sensor/interface module) only after isolation testing proves it pulls the bus down or fails to communicate with known-good circuits.
• Perform required Lexus initialization, calibration, or health-check routines after repairs when service information calls for it.

Can I Still Drive With B16A7?

You can usually drive a Lexus ES with B16A7, but treat it as a safety-system warning, not a nuisance light. This code means the vehicle lost communication with the pedestrian protection sensor bus on the left side. When the network drops out, the system may not detect a qualifying impact correctly. Some vehicles will disable pedestrian protection functions and store a warning message. Avoid aggressive driving, and do not assume any pedestrian protection feature will operate. If the code appears with other body, SRS, or collision-related codes, park the vehicle and schedule diagnosis. Communication faults can spread across shared power, grounds, or network splices.

How Serious Is This Code?

B16A7 ranges from moderate to serious, depending on what else fails with it. If the code sets alone and the warning clears after key cycles, you may have an intermittent harness or connector issue. If the code stays current, the pedestrian protection system may stay offline. That changes how the vehicle manages pedestrian protection events during an impact. Treat the system as potentially compromised until you verify the network, power, and grounds. This is not a drivability code, so the engine typically runs normally. However, diagnosis often overlaps with SRS and body network strategy on Lexus. Use the correct scan tool, and follow safety procedures near any impact or deployment components.

Common Misdiagnoses

Technicians often replace the left-side pedestrian protection sensor or a related module as soon as they read “lost communication.” That wastes money when the real fault sits in the bus wiring, a corroded connector, or a loose ground. Another common mistake involves checking only continuity with the battery disconnected. Communication faults often show up only under load or vibration. Shops also miss freeze-frame and code status, then chase a history code with no active fault. Finally, people overlook shared power feeds and splice points. A single poor connection can drop multiple left-side sensors and trigger B16A7 even when each sensor tests fine.

Most Likely Fix

The most common confirmed repair direction for B16A7 involves restoring stable communication on the left pedestrian protection sensor bus. Start with connector and harness inspection on the left-front area and any in-line connectors that serve that bus. Verify clean power and ground with a voltage-drop test under load before you touch parts. If you find high resistance, moisture intrusion, or terminal tension issues, repair the wiring and terminals, then retest network communication with the scan tool. If the bus wiring and power/grounds test good and the module still drops offline, you can then justify sensor or module replacement, followed by required Lexus initialization steps.

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