Interesting problem with my 2000 a6

   #1  

Mushimoto

New Member
Joined
Sep 1, 2020
Messages
6
Reaction score
0
Location
AZ, USA
Hello thank you for the verification on my account. I have a bit of an interesting issue with my a6 the car is a 2000 model a6 but it has a 2001 ecu and a 2001 cluster with immo disabled. I bought the car this way but it has recently come to my attention that there is something off with it. I recently got a cel *as the story goes with these lovely machines* and I figured I'd hook a generic obd2 reader to it to see what it was. No dice it wouldn't connect to the ecu. Ok so I figured its a fluke as these cars can be a bit difficult as audi uses the k-line and can system to communicate. Well, i got my hands on a vcds and hooked it up to the car, tested the connection and it said k1 was OK and k2 was OK. Now i dont remember what the can line said exactly but that shouldn't be an issue as the car uses k line for things. Well as you can see from the log I am going to post below the car connects to every other module except the ecu and comfort control module. Now, the back story to this car is a bit of a mystery to me but after some digging I found that the ccm is brand new as well snd the car was salvage title /fixed and certified/ in the state of Washington in 2005. What I am trying to figure out is why the ccm and ecu do not show up in vcds at all and I get connecter not responding when hooked to vcds but I can get other modules to respond.

Code:
Tuesday,01,September,2020,18:50:47:17925
VCDS -- Windows Based VAG/VAS Emulator Running on Windows 10 x64
VCDS Version: 20.4.2.0 (x64)
Data version: 20200730 DS317.0
www.Ross-Tech.com





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


Chassis Type: 4B - Audi A6/S6/RS6/allroad C5 (1998 > 2005)
Scan: 01 02 03 06 08 15 16 17 18 22 34 35 36 37 45 55 56 57 65 67
          75 76 77
 
-------------------------------------------------------------------------------
Address 03: ABS Brakes        Labels: 8E0-614-111-EDS.lbl
   Part No: 8E0 614 111 A
   Component: ABS/EDS 5.3 QUATTRO D00  
   Shop #: BB 24334  
   VCID: 1C3C422E8CEDC266EF-513C

No fault code found.

-------------------------------------------------------------------------------
Address 08: Auto HVAC        Labels: 4B0-820-043-MY1.lbl
   Part No: 4B0 820 043 K
   Component: A6-Klimavollautomat D62  
   Coding: 00160
   Shop #: WSC 02325  
   VCID: 22407CD6AE89F49625-258C

3 Faults Found:
01274 - Air Flow Flap Positioning Motor (V71) 
            41-10 - Blocked or No Voltage - Intermittent
00792 - A/C Pressure Switch (F129) 
            31-10 - Open or Short to Ground - Intermittent
01582 - Signal for Coolant Temperature 
            30-10 - Open or Short to Plus - Intermittent

-------------------------------------------------------------------------------
Address 16: Steering wheel        Labels: 4B0-907-487.lbl
   Part No: 4B0 907 487 
   Component: E Lenkrad Elektronik D03  
   VCID: 69D22BFA133FE7CEA4-4BCA

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments        Labels: 4B0-920-xxx-17.lbl
   Part No: 4B0 920 980 MX
   Component: C5-KOMBIINSTR. VDO D13   
   Coding: 02262
   Shop #: WSC 23324  
   VCID: 07160D42256B31BE52-513C

5 Faults Found:
01039 - Coolant Temperature Sensor (G2) 
            29-10 - Short to Ground - Intermittent
00779 - Outside Air Temp Sensor (G17) 
            30-10 - Open or Short to Plus - Intermittent
00771 - Fuel Level Sensor (G) 
            30-10 - Open or Short to Plus - Intermittent
00849 - S-contact at Ignition/Starter Switch (D) 
            31-10 - Open or Short to Ground - Intermittent
01314 - Engine Control Module 
            49-10 - No Communications - Intermittent

-------------------------------------------------------------------------------
Address 36: Seat Mem. Drvr        Labels: None
   Part No: 4B0 959 760 B
   Component: Sitzmemory R1 F     0101  
   Coding: 00001
   Shop #: WSC 00000  
   VCID: 2C5C92EEDC4D32E69F-4B00

No fault code found.

-------------------------------------------------------------------------------
Address 45: Inter. Monitor        Labels: 4B0-951-178.lbl
   Part No: 4B0 951 178 A
   Component: Innenraumueberw.    D02  
   Coding: 00101
   Shop #: WSC 02325  
   VCID: 264860C6C2A108B649-5284

1 Fault Found:
01349 - Alarm via Theft Warning System; Front 
            35-00 - -

-------------------------------------------------------------------------------
Address 56: Radio        Labels: 8D0-035-1xx-56.lbl
   Part No: 4B0 035 195 A
   Component:  Radio              D00  
   Coding: 00201
   Shop #: WSC 00003  
   VCID: 1E3848269AF1D07601-4A82

1 Fault Found:
00856 - Radio Antenna 
            36-00 - Open Circuit

End-------------------------(Elapsed Time: 05:24)--------------------------
Edit: I am sure some of these are ghost codes, as I've fixed some of these things but maybe you guys can give me some insight as to why its just not communicating with the ccm and ecu. I should add the car runs and drives and my key fob works so I know the ecu and ccm work in communication with one another, its just for some reason not working with the obd 2 port or my cluster.
 
Last edited:
   #2  

PetrolDave

Verified VCDS User
Verified
Joined
Dec 16, 2014
Messages
3,764
Reaction score
3,764
Location
South Molton, UK
VCDS Serial number
C?ID=1423
Sounds like you need to get a WD and trace the K & K2 wiring to see why those ECUs don't scan.
 
   #3  

Mushimoto

New Member
Joined
Sep 1, 2020
Messages
6
Reaction score
0
Location
AZ, USA
But the k1 and k2 test ok in vcds. Wouldnt that mean the wire that runs through all the modules is good?
 
   #4  

PetrolDave

Verified VCDS User
Verified
Joined
Dec 16, 2014
Messages
3,764
Reaction score
3,764
Location
South Molton, UK
VCDS Serial number
C?ID=1423
But the k1 and k2 test ok in vcds. Wouldnt that mean the wire that runs through all the modules is good?
But that doesn't mean that it connects to ALL the modules it should - just that it connects to at least one module ;)
 
   #5  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,896
Reaction score
21,338
Location
USA
VCDS Serial number
HC100001
But that doesn't mean that it connects to ALL the modules it should - just that it connects to at least one module ;)
No, it doesn't even mean that. It just means it can swing the output both high and low, i.e. that neither K-line is "stuck" (shorted to GND or +12).

FWIW, a 2000 A6 should only have one K-line. The second K-line didn't arrive until 2002 or thereabouts.

Note that the K-line goes directly to all diagnostic-capable modules except the ECU. For the ECU, it goes to the cluster and comes back and goes to the ECU as a line labelled "W". This allows the instrument cluster to disconnect the K-line from the ECU during immo negotiations so that those negotiations can't be sniffed or spoofed at the diagnostic socket.

There is also no CCM at address 46 in these cars, but there should definitely be a Central Locking module at address 35.

If it were mine, the first thing I would do is check continuity between pin 7 (K1) of the diagnostic socket and whatever pin the K-line goes to on the Central Locking module and/or pull the cluster and put a jumper between K and W on the cluster's harness connector(s) to see if the ECU then responds.

-Uwe-
 
   #6  

Mushimoto

New Member
Joined
Sep 1, 2020
Messages
6
Reaction score
0
Location
AZ, USA
So what you are saying is to jumper the lines and see if there is an internal issue. Are there wiring diagrams on here I can use to figure out the w and k wires on the cluster? And if the k to w doesn't trigger the ecu what could the likely problem be.
 
   #7  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,896
Reaction score
21,338
Location
USA
VCDS Serial number
HC100001
Yes, I would jumper K to W at the cluster connector(s) to see if the cluster is failing to connect them as it should.

Wiring diagrams can be found in a repair manual. I doubt erWin has them for a car that old, so this may be something of a challenge now. An old-school paper manual is available here.

-Uwe-
 
   #8  

Mushimoto

New Member
Joined
Sep 1, 2020
Messages
6
Reaction score
0
Location
AZ, USA
If rhats the issue how would I go about fixing that, because I tried the cluster in a different car and it works
 
   #9  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
29,896
Reaction score
21,338
Location
USA
VCDS Serial number
HC100001
If you put the cluster in a different car and were able to talk to the ECU in that other car, then I would check continuity on the W line between the cluster and the ECU in the car in which you can't talk to the ECU. And if you have a whole 'nother car to try things in, why not try moving the ECU as well to see if it works in the other car too?

-Uwe-
 
   #10  

Jetta 97

Professional User
Joined
Apr 22, 2014
Messages
807
Reaction score
761
Location
Dallas (McKinney) ,TX ,USA
VCDS Serial number
C?ID=81680
It is possible that you have bad ECu or broken wire form Cluster W-Line to ECU K-Line.

Here is this pin out of cluster K-Line and W-line:

K-Line is pin 28 Green connector
W-Line is Pin 5 Green connector .
 
  • Like
Reactions: Uwe
   #11  

Mushimoto

New Member
Joined
Sep 1, 2020
Messages
6
Reaction score
0
Location
AZ, USA
If it was a bad ecu the car wouldn't run. Atleast I'm pretty sure so i don't think its a bad ecu now the possibility of a broke wire seems a bit more likely.
 
   #12  

Mushimoto

New Member
Joined
Sep 1, 2020
Messages
6
Reaction score
0
Location
AZ, USA
I was at a buddies in a different state at the time, so I dont ha e that option right now. But it seems likely somewhere is not getting the proper connection
 
Top