"Too many communiction errors to continue!"

gottacar · Jun 19, 2014

Hi everyone, just received my lead, and tried a few scans, but getting [too many communication errors to continue!] on instrument cluster and immobiliser, other elements communicating fine.
Here's the autoscan

Code:

Wednesday,18,June,2014,20:50:04:24290
VCDS -- Windows Based VAG/VAS Emulator
VCDS Version: 12.12.2.0
Data version: 20140212


VIN: WAUZZZ8Dxxxxxxxxx

--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: 8D - Audi A4/S4/RS4 B5 (1995 > 2001)
Scan: 01 02 03 08 15 16 17 25 35 37 45 55 56 57 67 75 76 77
 
-------------------------------------------------------------------------------
Address 01: Engine        Labels: Redir Fail!
   Part No: 038 906 018 S
   Component:  1,9l R4 EDC   00SG  1630  
   Coding: 00002
   Shop #: WSC 00355  
   VCID: 2643E2BFC2B9EF2EC1B-4B00

1 Fault Found:
17978 - Engine Start Blocked by Immobilizer 
            P1570 - 35-00 - 
Readiness: N/A

-------------------------------------------------------------------------------
Address 03: ABS Brakes        Labels: 8E0-614-111-ABS.lbl
   Part No: 8E0 614 111 AB
   Component: ABS 5.3 FRONT       D00  
   Shop #: BB 24548  
   VCID: 5EB38A5FDA6977EEC9B-5140

1 Fault Found:
00283 - ABS Wheel Speed Sensor; Front Left  (G47) 
            30-00 - Open or Short to Plus

-------------------------------------------------------------------------------
Address 08: Auto HVAC        Labels: 8L0-820-043-2D.lbl
   Part No: 8L0 820 043 D
   Component: A4 KLIMAVOLLAUTOMAT_D75  
   Coding: 04144
   Shop #: WSC 06325  
   VCID: 2959E983D3A7C056EC9-25A0

5 Faults Found:
00779 - Outside Air Temp Sensor (G17) 
            30-00 - Open or Short to Plus
00603 - Footwell/defroster Flap Positioning Motor (V85) 
            41-10 - Blocked or No Voltage - Intermittent
01273 - Fresh Air Blower (V2) 
            17-10 - Control Difference - Intermittent
01206 - Signal for Duration of Ignition Off Time 
            27-10 - Implausible Signal - Intermittent
01582 - Signal for Coolant Temperature 
            30-10 - Open or Short to Plus - Intermittent

-------------------------------------------------------------------------------
Address 15: Airbags        Labels: 8D0-959-655-AI7.lbl
   Part No: 8D0 959 655 L
   Component: Airbag 7 Audi      0503  
   Coding: 00106
   Shop #: WSC 06325  
   VCID: 3F8D57DB3D235EE6A2D-5140

2 Faults Found:
01218 - Side Airbag Igniter; Passenger Side (N200) 
            32-10 - Resistance Too High - Intermittent
01217 - Side Airbag Igniter; Driver Side (N199) 
            32-10 - Resistance Too High - Intermittent

-------------------------------------------------------------------------------
Address 17: Instruments        Labels: 
   VCID: 55A19573AC5FB4B6981-5140
   Note: Excessive Comm Errors


-------------------------------------------------------------------------------
Address 25: Immobilizer        Labels: 
   VCID: 55A19573AC5FB4B6981-5140
   Note: Excessive Comm Errors


-------------------------------------------------------------------------------
Address 35: Centr. Locks        Labels: 8D0-862-257.lbl
   Part No: 8L0 862 257 G
   Component: ZV-Pumpe, DWA, Funk D08  
   Coding: 13130
   Shop #: WSC 06325  
   VCID: 397939C3230770D69C9-4ECE

1 Fault Found:
01372 - Alarm triggered by Door Contact Switch; Rear Passenger Side 
            35-00 - -

-------------------------------------------------------------------------------
Address 45: Inter. Monitor        Labels: 4B0-951-173.lbl
   Part No: 4B0 951 173 
   Component: Innenraumueberw.    D03  
   Coding: 00102
   Shop #: WSC 06325  
   VCID: E0CF34A7601DC11E7B7-4B4C

No fault code found.

End   ---------------------------------------------------------------------

Any ideas of how to get them clearly communicating with each other?

Uwe · Jun 19, 2014

Most often that's due to something else running on your PC preventing VCDS from answering modules in the real-time manner that they insist upon. What kind of PC are you running this on (CPU, RAM, version of Windows)? What else is running on it (particularly nannyware like virus scanners and such)? Have you looked at our FAQ Entry 2.5?

Of course it could also be a dodgy instrument cluster (the Immo being a virtual controller that's part of the cluster).

-Uwe-

gottacar · Jun 20, 2014

Hi Uwe,
yes, I have done most of what's on faq2.5, running MSCONFIG shows only the cornucopia of microsoft services running.
In answer to your question [Dell, intel P9400@2.4GHz, 2gRam, 32bitWin7] + no virus scanner running. Fresh windows install less than a year ago, and all os updates applied since.

If you like to recommend which microsoft services i should turn off.

Cluster key symbol behaves normally (disappears after approx 1second) and can be made to flash if reader coil is disconnected and rest of cluster behaves normally otherwise.

When selecting 'instruments' can hear small relay methodically clicking in cluster. (selecting 'immobiliser' identical behaviour)

Start
(short pause)
energised (approx 2second pause) relaxed (longer pause)
energised (approx 2second pause) relaxed (longer pause)
energised (approx 2second pause) relaxed (longer pause)
energised (approx 2second pause) relaxed (longer pause)
energised (approx 2second pause) relaxed
End

is there a way to debug? still saying "too many communication errors to continue!"

Uwe · Jun 20, 2014

OK, there's nothing obvious wrong with your computer or how it's configured. That doesn't mean it's not the source of the problem, so if you can beg, borrow, or steal another one to try temporarily, that would help trouble-shoot by process of elimination. I don't recall any instance where any MS service had to be turned off to allow VCDS to function properly.

This being an 8D car, it's in its teens in terms of age. Have you pulled the cluster and inspected the connectors for corrosion? It sure couldn't hurt to do that, and it would doing so would also reboot the cluster, which normally always has some unswitched power going to it.

-Uwe-

gottacar · Jun 23, 2014

Uwe, thanks for suggestions, and thanks for persisting with this one.
I have tried another pc, but unfortunately the same problem.
Then i pulled the cluster.
The cluster connections look okay, a little oxidation evident on very close inspection, but nothing excessive. Even so, i spent a good while cleaning both the male and female sides. Alas, after all that same problem.

Uwe · Jun 23, 2014

Then I think by process of elimination, the cluster being flaky is now the most likely explanation.

-Uwe-

gottacar · Oct 3, 2014

sorry to drag this up again, but having difficulty letting this car go.
too many communication errors implies some communication, but not enough.
i have been very persistent trying at different environment conditions multiple times.
can i try changing the 'Port and Protocol Options' on the about screen to up the chances?
is the security shutting down effective communication?
Is flaky a euphemism ?

Uwe · Oct 3, 2014

gottacar said:
sorry to drag this up again, but having difficulty letting this car go.
too many communication errors implies some communication, but not enough.
i have been very persistent trying at different environment conditions multiple times.

Just for laughs, have you tried a different PC?

gottacar said:
can i try changing the 'Port and Protocol Options' on the about screen to up the chances?
is the security shutting down effective communication?

Assuming those settings are all at their default values, I can't think of anything there that's likely to help.

gottacar said:
is the security shutting down effective communication?

I don't think so.

gottacar said:
Is flaky a euphemism ?

Since you're from the UK, "flaky" is American for "dodgy". Since it's an 8D chassis, this car is at least 13-14 years old. Stuff sometimes goes bad.

-Uwe-

Dana · Oct 3, 2014

The Instrument cluster could be faulty but .... the factory 56-Radio isn't communicating. If this is a 1997/1998 (or newer) I believe you should have a diagnostic capable radio in that vehicle on the same K-line. Please let us know what year this is (the 10th digit of the VIN is edited so I can't tell) and if it has a factory or aftermarket radio installed.

gottacar · Oct 6, 2014

Hi Dana, 10th digit is 'X', arrived in UK near the end of January 1999.
'Concert' radio factory fitted.
Autoscan will prompt radio to display 'diag' at the appropriate stage of scanning. CD changer in the trunk/boot area has previously physically been removed and coding reflects this absence, module is reporting no fault codes. I have no idea why 56-radio is not in the autoscan, but have been reading about unpredictability of all installed module appearing in the 'final report'

gottacar · Oct 6, 2014

Uwe, thanks for translating, 'dodgy' here in English means intermitantly working/not working. This situation is most definately in a not working state, no intermitant at all.

Uwe said:
Stuff sometimes goes bad.
-Uwe-

hence leading to the adjective "Stuffed"

Dana · Oct 6, 2014

gottacar said:
Hi Dana, 10th digit is 'X', arrived in UK near the end of January 1999.
'Concert' radio factory fitted.
Autoscan will prompt radio to display 'diag' at the appropriate stage of scanning. CD changer in the trunk/boot area has previously physically been removed and coding reflects this absence, module is reporting no fault codes. I have no idea why 56-radio is not in the autoscan, but have been reading about unpredictability of all installed module appearing in the 'final report'

OK a factory 56-Radio that isn't communicating could be the end result of a problem on the K-line, for example a faulty controller such as the 17-Instruments, or it could be the reason that you are experiencing communication issues with this vehicle.

I don't think this vehicle uses internal CAN communication to/from the 17-Instrument cluster and the other installed modules so I would:

1) Unplug the 56-Radio and see if 17 communicates.
2) Unplug 17 with 56 reconnected and see if and all other modules in the vehicle communicate.

If unplugging any one of the installed modules resolves the communication issue you can be reasonably confident that you found the bad one.

gottacar · Oct 6, 2014

Dana said:
OK a factory 56-Radio that isn't communicating

err, umm

Gottacar said:
Autoscan will prompt radio to display 'diag' at the appropriate stage of scanning... ...module is reporting no fault codes

Autoscan will prompt radio to display 'diag' (on the radio screen) at the appropriate stage of scanning

"module is reporting no fault codes" = 56-radio > 'no fault codes found'

i think this constitutes communication between radio and VCDS ?

Dana · Oct 6, 2014

gottacar said:
i think this constitutes communication between radio and VCDS ?

Sure, 56 could be communicating .... but that communication could be intermittent at best. Audi radios from this era were notorious for causing communication problems so that was my only suggestion before condemning 17.

Uwe · Oct 6, 2014

Those radios were notoriously difficult to communicate with, and they will clamp the K-Line to ground if they don't have any power, but when they're working as intended, they don't usually cause problems communicating with other modules. The ABS modules, on the other hand...

Silly question: Have you tried cold-booting the entire car?

-Uwe-

gottacar · Oct 9, 2014

okay, so if I'm reading this right...
"too many communication errors to continue" could mean any component or module on the car (such as radio or ABS) could have an invisible(to VCDS)fault that prevents effective comms with another module on the car.

endogenous versus exogenous
The fault could be intrinsic to the instrument cluster (such as a cracked pcb conductor, corrupted chip data or whatever) or external to the cluster such as ABS controller, radio, etc.

Is it therefore possible to isolate the K-line from all but the cluster, to exclude anything but the cluster ?

Cluster multi-pin connector, 32-pin, blue, [ 25 - K wire ]

Uwe · Oct 9, 2014

gottacar said:
Is it therefore possible to isolate the K-line from all but the cluster, to exclude anything but the cluster ?

IMO, it would be relatively difficult to do that with the cluster installed in the car. If I wanted to test communications with the cluster alone, I'd pull the cluster out and connect only Terminal 30 (unswitched power), Terminal 15 (switched power), GND, and K to the cluster and see if it then communicates reliably.

-Uwe-

ak77 · Oct 3, 2017

Hey everyone , I'm getting constant communication errors from 4 different vw cars all mk5&6 now , I have noticed this since doing a software upgrade 17.8.
Can someone run me with few suggestions. I have had the cable now for 3 years and dedicated laptop with XP Running . Nothing interferes with this as it's the only app running and no internet.

I have noticed that if after first few interruptions x8 or so , I do another pass at scanning it will successfully go through all the modules . But not the first time .
This is the same for all my other vw's and and Audi as well

Any recommendations?

Cheers
Al

ak77 · Oct 3, 2017

Also it's worth noting that communication errors appear with different controll modules at different passes / on same car scan .so it does not interrupt at same sections .

Uwe · Oct 3, 2017

Specs on the "dedicated laptop with XP" please?

-Uwe-

"Too many communiction errors to continue!"

Verified VCDS User

Benevolent Dictator

Verified VCDS User

Benevolent Dictator

Verified VCDS User

Benevolent Dictator

Verified VCDS User

Benevolent Dictator

Administrator

Verified VCDS User

Verified VCDS User

Administrator

Verified VCDS User

Administrator

Benevolent Dictator

Verified VCDS User

Benevolent Dictator

Verified VCDS User

Verified VCDS User

Benevolent Dictator