Absence of CAN2 communication (CAN2 buffer overflow)
• Check connector for CAN-bus 2 on DAS (pin B2 and B11). • Check wiring for CAN-bus: - Measure the resistance (with the battery disconnected) between CAN-high on DAS (pin B2) and CAN-high on any other unit on CAN2 on DAS2. It should be close to zero Ohm. - Measure the resistance (with the battery disconnected) between CAN-low on DAS (pin B11) and CAN-low on any other unit on CAN2 on DAS2. It should be close to zero Ohm. • Check wiring and connector for the ignition signal (pin A1) on the DAS. • Check that no third party controller/instrument is installed. • Check connectors for all ECU:s on the indicated bus. Check for verdigris, broken, unconnected or shorted pins. Disconnect one ECU at a time.
What you'll see
No driver-visible symptom recorded.
System reaction
None.
Diagnostic depth
The fault is validated as present if the ECU tries to send CAN-messages on CAN-bus 2, but no acknowledge is received from other unit(s), and thereby causing the internal buffer in the DAS to overflow. The DTC is set to active when the buffer overflow has lasted for 50 ms. The DTC is set to inactive when the CAN-messages are sent properly again and the buffer no longer is overflowing for the last 1050 ms. The DTC is not validated (stored) if: • the ignition is turned off • first 2 seconds after ignition on • the supply voltage is below 22 volt • the supply voltage is above 32 volt • short circuit on CAN-bus (separate DTC), except from short circuit between CAN-high and supply voltage
• Defect connectors on DAS for CAN-bus 2 (pin B2 or B11). • Defect wiring for CAN-bus, open circuit on CAN-high (pin B2) or CAN-low (pin B11). • Ignition signal (pin A1) on DAS is short circuit to supply. • Short circuit between CAN-high and supply voltage. • High busload • Defect ECU unit(s) on the CAN-bus.