Bosch 5.7 ABS Module coding issues

[koreandude81]

Hey guys,

So my current repair project is getting my repaired Bosch 5.7 ABS Module re-coded. It's the original and ended up having bad components relating to the wheel speed sensors and brake pressure. It never had any VAGCOM connection issues with it. The car is a 2002 Audi A6 3.0 Avant Quattro with 1LF brake package and an Auto trans (not CVT).

I've studied and reviewed the procedure and have used the provided Ross-Tech wiki to build my login and coding #'s but the short of the long is this: I can login but the module won't accept the code. In VCDS, after inputing the appropriate code#, I end up getting a "login lost due to dropped session" in the upper right corner. I also have a Foxwell NT510 scantool with VAGCOM on it. It will report a successful login, however the code portion reports "code rejected".

I've been informed that the Ross-Tech wiki info is not 100% accurate and I might not have the correct code. If this is the case, IDK what the hell to do because I was never able to get my original code off the module before I sent it off.

According to the wiki my login should be: 07397 with a code of 06497 for a 2002 A6 (non-armored), 1LF brakes, V6 3.0 gas, Auto (non cvt).
I feel like i'm so close to getting this crap fixed. Between time and money, I'm pulling my hair out. The only conclusion i've found online was another forum member, with the exact issue i'm having, had to purchase a new module and then the coding worked. I hope this is not my fate as most new Bosch 5.7's I've seen online cost anywhere from $700-$1000+ which is insane. I'm already about $300 in, toward this repair.

I deeply appreciate any usable insight.


If useful, here is the portion of the VCDS autoscan:

VIN: WAUVT64BX2N089073 License Plate:
Mileage: 137314 Repair Order:



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


Chassis Type: 4B (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

VIN: WAUVT64BX2N089073
-------------------------------------------------------------------------------
Address 01: Engine Labels: 06C-909-559-ASN.lbl
Part No SW: 8E0 909 559 D HW: 8E0 909 059
Component: 3.0L V6/5V G 0003
Coding: 0016752
Shop #: WSC 02325 785 00200
VCID: 3664FD9A42DC3DF103-5072

2 Faults Found:
18057 - Powertrain Data Bus
P1649 - 008 - Missing Message from ABS Controller - Intermittent
16805 - Warm Up Catalyst; Bank 1
P0421 - 001 - Efficiency Below Threshold - Intermittent
Readiness: 0000 0000

-------------------------------------------------------------------------------
Address 02: Auto Trans Labels: 01V-927-156.lbl
Part No: 4B0 927 156 FF
Component: AG5 01V 3.0l5V USA 1213
Coding: 0001002
Shop #: WSC 04940 001 00001
VCID: 70E80B82603853C119-5000

1 Fault Found:
18158 - Supply Voltage
P1750 - 003 - too Low

-------------------------------------------------------------------------------
Address 03: ABS Brakes Labels: 4B0-614-517.lbl
Part No: 4B0 614 517 H
Component: ABS/ESP allrad 1728
Coding: 00000
Shop #: WSC 00000
VCID: 26442DDAC27C4D71B3-5072

2 Faults Found:
01044 - Control Module Incorrectly Coded
35-00 - -
00778 - Steering Angle Sensor (G85)
66-10 - Not Matched - Intermittent

[bpark1210]

From what I recall you have to clear your steering angle sensor fault first then the ABS module will take the code, someone may correct me if I'm wrong it's been a few years since I last had to login to the ABS module.

When I re-did my brakes I was able to recode the ABS module but it would never communicate to do the ABS bleed. I just ended up doing multiple pedal bleeds and all seems fine now.

[koreandude81]

I don't believe there is a way to "clear" the G85 Steering angle sensor fault. It's a default code that comes up when the module has the incorrect code fault present. Basically, if your module needs recoding, you will have those two codes present always. I can log in with the 40168 basic setting code and carry out the G85 calibration procedure but it's only calibrated for that session and won't save it because my module won't accept the code using the ross-tech wiki info. And obviously that's the wrong order in the procedure. lol.

I honestly believe the wiki info just may not be correct for my vin. I've been informed by an ABS repair tech that it's not all 100% accurate. I have a spare module that I believe is 100% functional that is the exact same part # and came from the same model A6 with the same options from a Vin that's only 805 cars apart. I get the same coding error on it as my repaired one.
Also between a VAGCOM scantool as well as the highly regarded VCDS. So yeah, pretty sure I'm just not using the right code. It's a shot in the dark but maybe an Audi dealership can provide me the codes?

This job has seriously been one of the biggest headaches ever and only because it doesn't appear to have a 100% clear answer.

[julex]

I was never able to change the coding on my allroad either. There was a thread a while ago on this very forum about it and there were some "gotchas" for coding to take that didn't make any sense to me but reportedely they work. Search the forum and good luck!

[koreandude81]

Ok, I did initially dig around last week but I'll try again now that I know what to look for. Thanks Julex!

UPDATE:
So only 38 search results came back for "ABS coding allroad" and this was the closest in relevance:
https://www.audizine.com/forum/showt...coding+allroad

But the thing is, it's more about the OP just being confused that the login and coding used different parameters. He ended up using 07497/06397 for login/coding and it worked. My brake package is different so mine are supposed to be 07397/06497.

[chris86vw]

I had some issues with mine..stuck fault for the yaw sensor, coding blanked and it wouldn't take new coding. My buddy that works for Roos-tech and I finally got it but I can't remember what I Was goofing on (possibly from weird info on wiki)

If you are in fact a licensed user of VCDS post on their forum (free) and someone should be able to help you. Or call them..but not free help.

[koreandude81]

I had some issues with mine..stuck fault for the yaw sensor, coding blanked and it wouldn't take new coding. My buddy that works for Roos-tech and I finally got it but I can't remember what I Was goofing on (possibly from weird info on wiki)

If you are in fact a licensed user of VCDS post on their forum (free) and someone should be able to help you. Or call them..but not free help.

Sooooo, yeah not a licensed VCDS user. I have an outdated HEX-CAN cable and VCDS 17.1 I bought from an Australian auto repair site, attempting to keep repair costs low. I also have a Foxwell NT510 scantool that does everything VCDS does, just without the pretty GUI. Neither can get past the soft coding as previously mentioned.

My A6 seems to be a pretty vanilla, extremely popular/common model as I keep seeing the 07397/06497 login/coding #'s all over the place (forums, youtube videos, etc.). I'm beginning to think the codes are right. I just don't have any confirmation of what is wrong or broken. I keep chasing dead end leads and coming up empty handed, despite my efforts.

[chris86vw]

so sounds like you could have just bought the real thing for less than you spent and had the help from RT :)

But what you have in theory still should work. Have you tried clearing faults, even if they won't clear prior to trying to login or change coding the system sometimes likes to see this attempt. I looked at the wiki and my logs and nothing popped out at me as to what I was doing wrong before it finally worked.

do you have any faults for an attempt to align a sensor but it failed?I recall I was having an issue with that but not sure if it was related to my final fix and being able to recode. I think part of my issue might have been I Was using the manual login.. not the auto that it was before, but not sure if that was my final issue or just an early mistake and still had issues.

Not that I want to condone clone use, I would use that over the foxwell for this.

[koreandude81]

Ha, yeah at this point perhaps, but I've been at this since December '17 for this one problem and that's been my running total. I've had the Foxwell for about a year and it's been great for diagnosing/troubleshooting everything else. I went with it over VCDS for portability. It stays in the car, something I won't do with a laptop.

Anyways, after replacing two wheelspeed sensors and a yaw rate sensor last fall, intermittent ABS issues persisted, indicating a bad module. I found a used one on eBay for $50, allegedly "good", then ran into this code problem. I assumed it was a bad module so, I sent my original out for repair. It was confirmed bad, returned it repaired and again, ran into the same coding problem. So, maybe the junkyard module is in fact, "good".

So I thought maybe the NT510 scantool was the issue and looked into VCDS. But their steep costs, locked to one PC turned me off. And the free VCDS Lite couldn't carry out my needs either. So, I looked into cost effective alternatives and found VCDS 17.1 with a Hex-Can cable. Yet again, I'm having no success, getting the "dropped session" errors after soft coding.

So, at this point, it must be one of the following:

-Both modules are still bad
-Coding info is incorrect
-NT510 and VCDS are unable to code

Seems people's experiences coding are all over the place: some code w/o issues, some can't code, only to finally successfully code yet have no idea why, and finally some can't code 'cause they just don't know what they're doing at the time and/or are using bad tools.

I've cleared the ABS faults before attempting to code and I haven't had any other faults for sensors. I've used all zeros as well as 12345 for the WSC shop code. I've even tried different #'s for Logins, with 07397 (which is the correct one) only working. Still, 06497 doesn't won't accept as soft code. Interestingly enough, if I change the soft-code to 07497, which is for a "light-armored A6", it doesn't reject or drop the session and takes me back to the main screen that shows all the info, although soft code still displays all zeros. I can then carry out a G85 calibration and all ABS faults will disappear. But they return if I restart the car. This happens with both VCDS and the NT510. I know logging in with 07397 and soft coding with 07497 is an incorrect combo, but that's one combo I found that doesn't spit out a "code rejected" message on the NT510 or cause a "dropped session" on VCDS after experimenting. I use a 12345 WSC code for this.

My personal hunch tells me my NT510 can do the coding job, as VCDS hasn't done anything more, and my "repaired" and junkyard ABS Modules are likely not useable and a new, $700-800 Bosch 5.7 module would work.

But I'm still flying blind here and don't want to drop $700-800 to test a theory. But I don't see any other option.

[koreandude81]

Hmm, maybe the WSC# is what's holding me back? Ross-Tech says to either use 00000 or 12345 but I've come across VCDS auto-scans of other peoples ABS readouts (that work, lol) and their Shop #'s are definitely neither. Found one with: "Shop #: WSC 02334" from this:

-------------------------------------------------------------------------------
Address 03: ABS Brakes Labels: 4B0-614-517.LBL
Controller: 4B0 614 517 H
Component: ABS/ESP allrad 3428
Coding: 06397
Shop #: WSC 02334
VCID: 263F41FED1FF

It's the same module p/n, although from a 2004 2.7T A6. I'll give it a shot.

Maybe I should make a new thread asking willing members to post their abs auto-scan specs that have the "4B0 614 517 H" module?

[koreandude81]

Just an update:

Trying the 02334 WSC Shop # didn't work either. Back to the drawing board I guess.

[koreandude81]

Well, so I was giving it my usual go again at the ABS Module yesterday, going through my usual process: connect to Engine, scan and clear faults (usually none), connect to Trans, clear the "low voltage" fault, then connect to ABS clear faults (which there are only the typical two, code mismatch and G85 steering angle sensor cal).

Something changed as I was trying to access the ABS Module: After accessing it, I noticed the comm status section was busier than usual. After a few seconds a window popped up with, "Too Many Communication Errors to Continue". So I closed out VCDS, cycled the ignition, and tried again. I was able to access everything else (engine, transmission) but would get this error with the ABS module.

Soooo, I guess this means my "repaired" ABS module crapped out completely? Maybe this damned thing was never really capable of being coded to begin with? At this point I guess I have no choice but to order a new module.

Anyone else have experience with the "Too Many Communication Errors to Continue" message?