B1326 – Lost communication with clock device (local – CAN) (Lexus)

B1326 means your 2021 Lexus ES lost communication with the clock device on a local CAN network. For most owners, the real-world effect is simple. The dash clock may reset, drift, or go blank, and some body features may act odd after a restart. According to Lexus factory diagnostic data, this code indicates “Lost communication with clock device (local – CAN).” That definition points to a network message problem, not a confirmed bad clock. Treat it as a communication fault first. Verify power, ground, and CAN integrity before replacing any module.

B1326 Quick Answer

B1326 sets when a Lexus module stops receiving expected CAN messages from the clock device on the local body network. Fixes start with checking network health and clock device power/ground, not swapping parts.

What Does B1326 Mean?

Official definition: “Lost communication with clock device (local – CAN).” In plain terms, one of the body-related modules on your Lexus ES noticed it cannot “see” the clock device on the network. In practice, the clock may not update correctly, may reset, or the vehicle may store body network faults after key cycles. This code does not prove the clock device failed. It proves a module missed clock-device communication.

What the module checks: The reporting module monitors the local CAN bus for periodic identification and status messages from the clock device. It also checks timing and message validity. Why that matters: The same missing-message condition happens with a clock power loss, a poor ground, a connector issue, a CAN-H/CAN-L wiring fault, or another module pulling the network down. Diagnosis must confirm whether the clock device went offline or the network went unstable.

Theory of Operation

On Lexus body networks, modules share information over CAN so each ECU does not need direct wiring to every component. The clock device communicates its status and receives time-setting commands through these CAN messages. The local CAN segment typically supports comfort and body functions. Modules expect regular messages at predictable intervals.

B1326 sets when the expected clock-device messages stop, arrive corrupted, or arrive too late. A power or ground drop can reboot the clock device and interrupt its messages. A high-resistance splice or water intrusion can distort CAN signals and cause message loss. Another ECU can also disrupt the local CAN if it shorts a bus line or floods the network with errors.

Symptoms

These are the most common signs you will see with a Lexus B1326 communication-loss fault.

• Scan tool behavior Clock device missing from the ECU list, shows “no communication,” or drops in and out during a health check
• Clock display Time resets after starting, fails to hold time, or intermittently goes blank
• Intermittent operation Problem changes with bumps, cabin temperature, or after a car wash
• Body DTCs Additional network or body communication codes stored with similar timestamps
• Settings retention User settings tied to time or display behavior may not save consistently
• Start-up anomalies Longer boot time for the display or delayed clock synchronization after key-on
• Low-voltage sensitivity Symptoms worsen after a weak battery event or recent jump start

Common Causes

• Clock device offline on local CAN: If the clock device stops transmitting messages, the body network flags a lost-communication fault.
• Open or high resistance in local CAN wiring: A break or added resistance on the local CAN twisted pair prevents message delivery to the receiving module.
• Short to ground or short to power on a CAN line: A short forces the bus dominant or corrupts frames, which blocks normal communication.
• Poor power or ground supply to the clock device: Low supply voltage or a weak ground lets the clock module reset and drop off the network.
• Connector pin fit or terminal corrosion at the clock or junction: Loose tension or corrosion increases resistance and creates intermittent network dropouts.
• Local CAN splice or junction connector issue: A compromised splice, junction, or connector interrupts the branch that feeds the clock device.
• Recent interior service or accessory installation damage: Trim work, radio work, dash repairs, or aftermarket taps can pinch or pierce the local CAN harness.
• Network disturbance from another node on the same local CAN: Another ECU on that local bus can short or load the network and make the clock appear “missing.”

Diagnosis Steps

Use a scan tool that can run a Lexus network health check and show ECU presence. Have a DVOM for voltage-drop testing and a back-probing kit. Use service information for connector views and splice locations. An oscilloscope helps confirm CAN integrity during an intermittent. Plan time for a careful harness inspection around dash and console areas.

1. Confirm DTC B1326 and record freeze frame data. Focus on ignition state, battery voltage, vehicle speed, and any related body/network DTCs. Freeze frame shows the exact conditions when the fault set. Use a scan-tool snapshot later to capture an intermittent dropout during a wiggle test or road test.
2. Run a full network scan and note whether the clock device appears as an online ECU. If the scan shows the device missing, treat it as a network-offline problem first. If it appears online, look for intermittent communication loss and history codes. Check for pending versus confirmed status, since a confirmed code often repeats quickly on key-on with a hard fault.
3. Check fuses and power distribution that feed the clock device and the related body network. Do this before any ECU connector testing. Verify each fuse has power on the supply side and load side with the circuit energized. A fuse can pass a visual check and still fail under load.
4. Verify clock device power and ground with voltage-drop testing under load. Turn the ignition ON and command the vehicle into a state where the clock powers up. Measure power feed drop from the fuse output to the clock power pin. Measure ground drop from the clock ground pin to chassis ground while the device operates. Keep ground drop under 0.1V with the circuit operating.
5. Inspect the clock device connector and nearby harness routing. Look for backed-out pins, loose terminal tension, moisture tracks, and corrosion. Check for harness pinch points near trim fasteners and sharp brackets. Pay close attention if the vehicle recently had radio, dash, windshield, or interior trim work.
6. Inspect the local CAN twisted pair between the clock device and the nearest junction/splice. Verify the twist remains consistent and the pair stays intact. Look for aftermarket taps, Scotch-locks, or repairs that changed wire geometry. Confirm any prior repairs use proper splicing methods for network wiring.
7. Check the clock device CAN circuits for shorts with the system powered correctly. Measure for short-to-ground and short-to-power at the harness side with the connector disconnected as directed by service information. If you check CAN bias voltages, do it with ignition ON. CAN bias voltage only appears when modules power up, so ignition-OFF readings mislead.
8. If you have a scope, evaluate CAN signal integrity at the clock connector and at the junction point. Look for a stable, mirrored signal on both CAN lines and clean transitions. Noise, a stuck dominant condition, or a collapsed waveform points to a short, extra load, or a wiring fault. Compare the local bus behavior to a known-good location on the same bus when possible.
9. Isolate the fault if the network shows disruption from another node. If the local CAN supports segmentation, disconnect one branch at a time using approved junction connectors. Recheck ECU presence after each change. This approach helps prove whether the clock device truly fails to communicate or another module drags the bus down.
10. After repairs, clear codes and rerun the network scan to confirm the clock device reports online. Perform an ignition cycle and a short drive to confirm the code stays cleared. If the monitor sets as a Type B logic on this platform, a second drive cycle may be required to confirm the repair. Recheck for pending codes and confirm no new network DTCs appear.

Professional tip: Treat B1326 as a network proof problem, not a parts problem. Prove the clock device has stable power and a low-drop ground first. Then prove the local CAN pair stays intact and undisturbed. When the fault acts intermittent, use a scan-tool snapshot during a harness wiggle test to catch the moment the clock drops offline.

Possible Fixes

• Restore power feed integrity to the clock device: Repair the fuse output, terminal fit, or power supply wiring that fails voltage-drop testing under load.
• Restore ground integrity at the clock device: Clean and tighten the ground point or repair the ground circuit that shows excessive voltage drop.
• Repair local CAN wiring faults: Fix opens, shorts, or damaged twisted pair sections using approved network-wiring repair practices.
• Service connector terminals and seals: Correct backed-out terminals, poor pin tension, or corrosion at the clock device connector or junction connectors.
• Remove improper accessory taps: Eliminate aftermarket splices or taps that disturb CAN impedance or introduce intermittent contact.
• Correct a junction/splice issue: Repair or replace the affected junction connector or splice segment after you prove it interrupts the clock branch.
• Replace the clock device only after verification: Replace the module only after power, ground, and CAN circuit integrity tests pass and the device still drops off the network.

Can I Still Drive With B1326?

You can usually drive a 2021 Lexus ES with DTC B1326, because this code points to a local-CAN communication loss with the clock device. It rarely affects engine operation, braking, or steering. Expect nuisance issues instead, like an incorrect time display or settings that will not retain time after key cycles. Still, treat the warning seriously if other CAN or body DTCs appear. Multiple network codes can signal a wider bus problem that can disable body functions. If the vehicle shows a no-start, repeated battery drain, or multiple modules dropping offline, stop driving and diagnose the network and power feeds first.

How Serious Is This Code?

B1326 ranges from an inconvenience to a sign of a larger body-network fault. When the only symptom is a clock display that resets or freezes, the risk stays low. The car remains safe to operate, and the fix often targets power, ground, or connector integrity. Severity increases when B1326 appears with other communication-loss codes, low-voltage history, or intermittent accessory failures. In those cases, the local CAN may suffer from a short, an open, or a module that loads the network. That condition can cascade into lost functions like illumination control, audio/HVAC interface behavior, or wake/sleep errors that contribute to battery drain.

Common Misdiagnoses

Technicians often replace the clock device or the head unit because the time display looks wrong. That approach wastes money when the real fault sits in power, ground, or local-CAN wiring. Another common error involves clearing codes after a low-battery event and calling the repair complete. Low system voltage can trigger a temporary module dropout that returns under the same conditions. Shops also miss connector fit issues at the clock device or related junction connectors, especially after interior trim work. Avoid guesswork by confirming module presence on the scan tool, checking for other network DTCs, and load-testing power and grounds before any part decision.

Most Likely Fix

The most frequently confirmed repair direction for B1326 focuses on restoring stable power, ground, and clean local-CAN connectivity to the clock device. Start with battery health and charging system verification, then verify the clock device receives solid power and ground under load. Next, inspect and correct connector problems, harness damage, or terminal tension issues that interrupt local-CAN lines. If the scan tool cannot see the clock device after circuit integrity checks, the next step often involves module-level testing with service information and, when required, Lexus-approved programming tools such as Toyota Techstream to confirm configuration and network registration.

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