Code
P1687
PLYMOUTH
P — Powertrain
No Cluster Bus Message
AI status
Completed
Completed
100%
Causes
- Failed or intermittent instrument cluster (IPC)
- Open, shorted or corroded wiring on the data bus between cluster and other modules
- Bad ground(s) or low battery/low system voltage
- Blown fuse for instrument cluster or data bus power
- Faulty body control module (BCM) or powertrain control module (PCM) affecting the bus
- Aftermarket alarm/head unit/security device interfering with bus
Symptoms
- Blank or non-responsive instrument cluster or intermittent display
- Loss of speedometer/odometer, tachometer or other gauges
- Some or all dash warning lamps do not illuminate or remain on
- Communications errors when using a scan tool; cluster does not appear in module list
- Possible no-crank/no-start or immobilizer/security symptoms if cluster provides security messages
- Other modules showing related communication trouble codes
What to check
- Verify battery voltage is within normal range and connections are clean/tight
- Check instrument cluster and related fuses (inspect visually and test with meter)
- Visually inspect cluster connector(s) and harness for damage, corrosion or water entry
- Scan vehicle with a capable scan tool and confirm whether the cluster appears on the data bus
- Use a DVOM or lab scope to check data-bus signal presence at the cluster connector
- Check for poor chassis and battery grounds near dash/BCM/cluster
Signal parameters
- Serial data bus: dominant and recessive voltage states (idle recessive typically near battery voltage; dominant pulls toward ground)
- Message activity: periodic frames from cluster (packets/sec) — absence indicates no cluster messages
- Typical Chrysler/Class 2 bus baud ~10.4 kbps (verify vehicle-specific rate) — check for data traffic with scope or scan tool
- Check continuity between cluster data pin and BCM/Park harness; expected low resistance (< few ohms) when intact
- Look for shorts to power or ground on data line (unexpected steady voltages)
Diagnostic algorithm
- Record freeze-frame and all active/related codes with a scan tool; note whether cluster is detected on the tool.
- Verify battery voltage (12.4–12.8 V engine off). Recharge if low. Retest after full charge.
- Inspect and test cluster and BCM fuses. Replace any blown fuses and retest for code return.
- Perform a visual inspection of cluster connector and wiring harness for damage, corrosion, or loose pins.
- Check and clean ground points for instrument cluster/BCM. Re-torque fasteners to spec.
- Using a scan tool, attempt to communicate directly with the cluster. If tool cannot see the cluster, suspect cluster, wiring, or bus-level fault.
- Backprobe the data-bus pin at the cluster connector and observe with a scope or lab-quality scan tool for data activity. No activity: proceed to wiring checks.
- Check continuity of the data-bus between the cluster and BCM/PCM; isolate sections of harness if necessary. Look for shorts to power/ground.
- Disconnect non-factory accessories (alarms, remote start, radios) that tap into the wiring. Re-check communications.
- If wiring and fuses are good but no data from the cluster, swap or bench-test instrument cluster per manufacturer procedure (or replace with known-good cluster) as final verification.
- After repair, clear codes and perform a road test/communication check to confirm code does not return.
Likely causes
- Faulty instrument cluster (internal failure)
- Damaged data-bus wiring (open or short to ground/power)
- Bad ground(s) at dash or BCM
- Blown cluster or BCM fuse
- Aftermarket device tied into vehicle wiring causing bus disruption
Fault status
Status
No Cluster Bus Message — instrument cluster not communicating on vehicle serial data bus.
Repair difficulty: Medium
Diagnostic time: 1.0 - 3.0 hours
Similar codes
Your experience will help others
+100 karma for a short comment :)
Was this AI description helpful?
Your feedback helps improve AI descriptions.
👍 Like
0
👎 Dislike
0
Send to email
