DSC codes and dead column cluster
DSC codes and dead column cluster
Hey all I hope I'm posting in the correct thread, I have a stock 2005 R50 I'm just hoping to get some help with the following issues. First I have five different DSC DTCs.
5E14 HISTORY CAN Timeout DME/DDE
5E5C HISTORY RPA push button Error
5E1F ACTIVE ABS/ASC/DSC: VIN not initilised, execute LWS calibration
5E16 ACTIVE CAN Timeout instrument cluster
5E1E ACTIVE CAN Timeout LWS
After these codes popped up my brake lights stay on as well as the column instrument cluster (Chrono package) stopped working. Any insight or input would be greatly appreciated.
5E14 HISTORY CAN Timeout DME/DDE
5E5C HISTORY RPA push button Error
5E1F ACTIVE ABS/ASC/DSC: VIN not initilised, execute LWS calibration
5E16 ACTIVE CAN Timeout instrument cluster
5E1E ACTIVE CAN Timeout LWS
After these codes popped up my brake lights stay on as well as the column instrument cluster (Chrono package) stopped working. Any insight or input would be greatly appreciated.
It looks like you have a communication fault on the CAN bus. This is likely caused by faulty wiring or a faulty module on the network.
I would start with measuring the resistance across the CAN_H and CAN_L wires, it should be 120 ohms.
Check for short to ground on both of those wires too.
Next, use an oscilloscope to look for noise in the signals across the two wires. Unfortunately, more DIYers don't have one.
A less accurate but sometimes effective method is to unplug each of the modules on the network one-by-one, clear the codes and see if they all come back. Plug it back it, move to the next module and repeat. If only some codes re-appear then you've found the faulty module.
I would start with measuring the resistance across the CAN_H and CAN_L wires, it should be 120 ohms.
Check for short to ground on both of those wires too.
Next, use an oscilloscope to look for noise in the signals across the two wires. Unfortunately, more DIYers don't have one.
A less accurate but sometimes effective method is to unplug each of the modules on the network one-by-one, clear the codes and see if they all come back. Plug it back it, move to the next module and repeat. If only some codes re-appear then you've found the faulty module.
Thread
Thread Starter
Forum
Replies
Last Post
jecamp988
R50/R53 :: Hatch Talk (2002-2006)
7
Mar 6, 2023 03:28 PM




