ABS Alarm

S

smilesbernard

Active Member
Hi there
I am trying to understand what is wrong wit the car
I bought a scanner cable recoomended on this group and have vdslite
the connection is poor when tested but i do get some results back
It seems inconclsive though ... I was hoping it would tell me that a specific wheel sensor was the issue but all i get is below
If i go into the ABS module and run the tests i dont get anything back. this is just from the autoscan
The later errora re misfires i think i have fixed.... I think buit not certain it was a battery tyhat wasnt performing well enough . Since i recharged and repaired that it seems to have finally stopped misfiring ... i need to drive it more to know for sure but the ABS alarm and then limp mode is preventing that !

Any help much appreciated!

The car is very close to the scrap heap now ;) shame as its been great but i'm short on time and funds to fix....

Many thanks




-------------------------------------------------------------------------------
Address 03: ABS Brakes Labels: None
Controller: 8Z0 907 379 B
Component: ESP 20 CAN V015
Coding: 10758
Shop #: WSC 00000
VCID: 47E1D81F76B5
1 Fault Found:
01314 - Engine Control Module
79-10 - Please Check Fault Codes - Intermittent




VCDS-Lite Version: Release 1.2
Friday, 15 November 2024, 17:14:33.
Control Module Part Number: 036 906 034 Q
Component and/or Version: MARELLI 4LV 3720
Software Coding: 00051
Work Shop Code: WSC 00340
VCID: 20336383B3DB
Additional Info: WAUZZZ8ZZ1N019538 AUZ7Z0Y1572240
9 Faults Found:
16684 - Random/Multiple Cylinder Misfire Detected
P0300 - 35-10 - - - Intermittent
16685 - Shareware Version. To Decode all DTCs
P0301 - 35-10 - Please Register/Activate - Intermittent
16686 - Shareware Version. To Decode all DTCs
P0302 - 35-10 - Please Register/Activate - Intermittent
16687 - Cylinder 3: Misfire Detected
P0303 - 35-10 - - - Intermittent
16684 - Shareware Version. To Decode all DTCs
P0300 - 35-10 - Please Register/Activate - Intermittent
16685 - Shareware Version. To Decode all DTCs
P0301 - 35-10 - Please Register/Activate - Intermittent
16687 - Cylinder 3: Misfire Detected
P0303 - 35-10 - - - Intermittent
17961 - Shareware Version. To Decode all DTCs
P1553 - 35-10 - Please Register/Activate - Intermittent
17912 - Shareware Version. To Decode all DTCs
P1504 - 35-10 - Please Register/Activate - Intermittent








01314 intermittrent

VCDS-Lite Version: Release 1.2
Friday, 15 November 2024, 17:07:18.
Control Module Part Number: 8Z0 907 379 B
Component and/or Version: ESP 20 CAN V015
Software Coding: 10758
Work Shop Code: WSC 00000
VCID: 47E1D81F76B5
1 Fault Found:
01314 - Engine Control Module
79-10 - Please Check Fault Codes - Intermittent





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


VCDS-Lite Version: Release 1.2
Friday, 15 November 2024, 17:08:45.


Chassis Type: 8Z - Audi A2
Scan: 01,02,03,08,15,16,17,18,37,45,46,56,57,75,76,77

-------------------------------------------------------------------------------
Address 01: Engine Labels:
Controller:
Note: Can't Synch Baud Rate
 
The first thing to do is to clear the existing faults, in each controller, as many of them are, probably historical, and no longer present. This will, (almost certainly), reduce the list of faults.
When you installed VCDS Lite, did you also download, and install the device drivers from Ross-Tech?
The cable uses an old version of a chip, and the up to date drivers, which Windows will automatically use, are not a good match.
Mac
 
Thanks Mac I'll take her up the hill and see what codes emerge !
I got confused with the driver info on the Ross tech site but I'll have another look and see if I can figure it out. It seemed to be suggesting that I'd only need the driver if I had an old pc.
I'll re read and try again
Many thanks !
 
smilesbernard said:
Thanks Mac I'll take her up the hill and see what codes emerge !
I got confused with the driver info on the Ross tech site but I'll have another look and see if I can figure it out. It seemed to be suggesting that I'd only need the driver if I had an old pc.
I'll re read and try again
Many thanks !
Click to expand...
I use two laptops, one old XP, and one on Windows 10. I use the Ross-Tech drivers, successfully, in both, having had problems on the Windows 10 machine,following a Windows update, which included a new version of the FTDI driver.
Mac.
 
thanks for the support with this
just back from a drive and the car is driving really well
but then every few mins the esp/abs lights along with the red central brake display. If i ignore it - the car goes into limp mode. turn on and off engine and it clears and i get another few mins of driving in before it repeats
So i'l trying to get the windows 10 setup for better comms with VCDS lite and my Gendan connector
I downloaded the drivers from the above link on rosstech
Ive unzipped but even when i attempt to update the usb driver windows automatically using the 'have diak' option.. it doesnt allow me to go to 'Next'... any help much appreciated
for now i'll try and scan with the default driver and see what codes are showing up !
ALl the very best
 
@smilesbernard,
What does the ABS alarm look like on the dash board please?


This one happened when my brake fluid reservoir was empty.

If yours looks the same and there's no abs wheel speed sensor DTC's please stop driving the car and check the brake fluid reservoir. 🙂👍
 
Last edited:
smilesbernard said:
thanks for the support with this
just back from a drive and the car is driving really well
but then every few mins the esp/abs lights along with the red central brake display. If i ignore it - the car goes into limp mode. turn on and off engine and it clears and i get another few mins of driving in before it repeats
So i'l trying to get the windows 10 setup for better comms with VCDS lite and my Gendan connector
I downloaded the drivers from the above link on rosstech
Ive unzipped but even when i attempt to update the usb driver windows automatically using the 'have diak' option.. it doesnt allow me to go to 'Next'... any help much appreciated
for now i'll try and scan with the default driver and see what codes are showing up !
ALl the very best
Click to expand...
With cable plugged in.
Have Disk > Browse > to the folder you downloaded, and unzipped the drivers.
There are two .inf files, try one, and if it not accepted, try the other.
Mac.
Edit: Did you manage to clear the DTCs, especially the ECU, Engine Controller?
 
Last edited:
PlasticMac said:
With cable plugged in.
Have Disk > Browse > to the folder you downloaded, and unzipped the drivers.
There are two .inf files, try one, and if it not accepted, try the other.
Mac.
Edit: Did you manage to clear the DTCs, especially the ECU, Engine Controller?
Click to expand...
Basically, I think it's an engine fault that is triggering the ABS not an ABS fault.
Mac.
 
When the "crisis" happens and all the lights come on - do you also get ABS / EPC / stability control fault lights coming up as well as the limp mode / loss of throttle body control etc.? Are there any other notable factors (weather conditions, temperature, applying brake pedal etc.)?

This is either the second or third parallel thread on a very similar collection of faults we have running here in the very recent past (and others previously).

Various hypotheses re brake light switch, alternator performance, battery levels, manifold air pressure sensor errors, various other air leaks solved by replacing lids with aged o-rings (petrol cap, oil cap).

Although I suspect @smilesbernard you've told us this before - which engine do you have and any other pertinent information as today's thread has started out of the blue again.
 
Hi there
Yes I've seen a few other threads with similarish abs woes
The engine is 1.4 petrol 2001 with single coil pack. Perhaps MARELLI means something as it cones up on vcdslite but not sure if that's related to engine type
So I took it for a spin again after clearing down all the errors and I got exactly the same as above in my 1st post on the thread.
01314 - Engine Control Module
Also engine misfires intermittent and specifically cylinder 3

It ran well in that I didn't notice any misfiring up the big hills in 2nd gear and putting foot down etc.
But the engine is saying misfires - intermittent with special note on cylinder 3
Not sure which is 3 but I could try switching the plugs around and seeing if that alters the cylinder misfire but they all look clean and spacings are OK.
As normal after 5 mins of driving the and alarm 3 beep alone with the epc and abs triangle lights
It drives for a few mins in this alarm state then goes into limp
If I turn it off and on its ok for a short period but then it alarms again

So far - this all started with a breakdown - with abs errors and limp mode. Took it to garage who diagnosed a manifold pressure sensor our of range. Did a smoke test and found there was a leak on the vacuum pipes in that area (I didn't actually know or ask for more details but they fixed the pressure leak and the manifold pressure code stopped
But the abs alarm symptoms including obvious misfiring continued along with misfiring codes
I swapped the coil pack with a new Bosch one. No different
I changed and recharged battery - that was a problem potentially as it felt like the misfiring went away at that point but I'm still getting misfire codes !

I see others link this to manifold pressure switched but I've not had any more codes about that. Is that a hard or costly fix?
At the point of giving up but such a shame as feels like something minor and otherwise its been a brilliant car

Any thoughts most welcome and gratefully recieved
 
As in this thread:
Thread 'Mysterious Engine Light: Load Calculation Cross Check - Lower Limit Exceeded' https://www.a2oc.net/community/inde...ation-cross-check-lower-limit-exceeded.54449/
It would be great if someone could create a log, in a car without the symptoms so we can compare the same data from a car with the symptoms.
Mac.
Edit: To make progress on this common symptom, requires a "Team Effort"
Isolated investigation isn't going to be productive
 
  • Like
Reactions: Ami
Hi,
The engine is AUA. Marelli is the ECU manufacturer.

01314 in the ABS module is saying that there is some problem with the communication to the engine ECU or that there is a fault stored in the engine ECU memory.

In your case, I would be inclined to say that there is a communication fault, a misfire should not cause ABS warnings like this.

If you can log group 3 in the ECU (there a lots of guides on how to do this, just search VCDS logging guide) and then drive the car until the fault happens, that will be a good start.
 
Last edited:
To add more clarity, you most likely don’t have a ABS fault, but the ABS is going into a error state because it loses communication with the ECU.

That could be because the ECU is faulty, the power to the ECU is being interrupted, there is a wiring fault, or the ABS module has some internal error (unlikely).

By logging this group you can check the battery voltage to see if it falls when ABS light comes on. If VCDS disconnects, that may also indicate that the ECU is getting reset.
 
For now, I'll assume this is an ABS/EPC problem, as there's nothing, currently to suggest @smilesbernard 's problem is anything else.
The ABS Controller is the MK20.
The earlier scan shows that the ABS/EPC problem, that's triggering the ABS/EPC lights, is caused the loss of communication with the ECU.
As far as I can see, Comms is via the CANBUS. I suspect the link between the two controllers supports traction control.
The ECU has not been scanned, with "Can't Synch Baud Rate"
The ECU must be scanned, and any DTCs cleared first, as it's quite possible, (imo), that the ECU has a logged DTC that is causing a problem, and will continue to, until it's cleared.

Just seen @a-zwo 's post, with much the same conclusion.
Mac.
 
thanks @PlasticMac and @a-zwo this is really helpful
Ok so i need to figure out how to scan the ECU.....
I guess trying to adjust the baud rate on the com port would be worth a try? Are there any other things to try here
Since installing the sopecific drivers as per Mac's advice the connection has gone from poor to good... so perhaps if i play with the baud rate i'll get some joy
The other option i assume if to drive it (in 2 min stop starts to avoid limp mode) to a VAG specialist and pay for use of the full licenced scanner ?

So the best option here might be that i clear the codes from the EDU and all the woes clear also
Or at least i get to see what might be underneath the issues

I'm unclear if from the descriptions if there is a fundamental issue with the cars internal comms ... but sterpwise i guess!

Many thanks for all the support
 
smilesbernard said:
thanks @PlasticMac and @a-zwo this is really helpful
Ok so i need to figure out how to scan the ECU.....
I guess trying to adjust the baud rate on the com port would be worth a try? Are there any other things to try here
Since installing the sopecific drivers as per Mac's advice the connection has gone from poor to good... so perhaps if i play with the baud rate i'll get some joy
The other option i assume if to drive it (in 2 min stop starts to avoid limp mode) to a VAG specialist and pay for use of the full licenced scanner ?

So the best option here might be that i clear the codes from the EDU and all the woes clear also
Or at least i get to see what might be underneath the issues

I'm unclear if from the descriptions if there is a fundamental issue with the cars internal comms ... but sterpwise i guess!

Many thanks for all the support
Click to expand...
If you can get the alternative driver installed, the default baud rate is preset.
Mac
 
Hi, the connection issue with the ECU is a known problem with this car. It isn’t a problem with full VCDS or another scanner, but VCDS lite can be very unreliable.

To make it work, you can follow Mac‘s guidance here to reduce the latency: https://www.ttforum.co.uk/threads/vcds-pc-setup.1924695/

If that doesn’t help, you need to open VCDS, go to options and set Start Baud to 10200, Apply and save.
Now try and connect. If that doesn’t work, repeat with 10400 and 4800.
 
I was unable to communicate with the Magnetti-Marelli ECU with VCDS-Lite version - all of my AUA work was done with my Xtools VAG401 as a consequence until I eventually got a full-fat infinite VIN number VCDS cable. Your experience is not unique!

There was a related thread I read the other day where someone with a similar problem (I think) found that the voltage regulator in the alternator was the key to the problem - which would tally with my running hypothesis about it being an ECU crisis due to voltage levels in very specific conditions (cold weather, dark, battery not tip top, alternator is the smallest 90A one and maybe not in best condition, heavy electrical demand because everything is turned on and it's not long after starting the engine), but I am now completely drawing a blank on finding the post again, even in my browsing history.

I like the look of @a-zwo's suggestions about logging the voltage-related data above - will have a look at how to go about this, although I don't really have availability of my other half's car at the moment owing to my and her work patterns.
 
Another very helpful group to log is 125. That group reports the CAN bus status, but it is again not available in VCDS lite. That’s something to try later.
 
thanks @PlasticMac and @a-zwo
The plot thickens
Now with the proper driver and some checking of the com port settings i seem to be able to connect to the 01 controller for the engine :)
I cleared all fault codes (some showing intermittent cyliner misfires and also misfired in cyl 3
Also clear all in the abd control module
Then a short drive up a hill
I had the vdcs plugges in and monitoring a few blocks for sensors
The abs alarm went off as normal
Interestingly i was able to drive home without limp mode kicking in - perhaps just randon luck
On checking the engine001 controller is reporting


1 Fault Found:

17961 - Barometric / Manifold Pressure Signals: Implausible Correlation

P1553 - 35-10 - - - Intermittent

No errors logged for cylinder misfires at this time

I took a log of the engine sensors readings as a .csv file (attached) and it looks like the inlet manifold went up to about 900+ mbar from a start pressure of 3 to 400

The manifold pressure when the alarm went off was i think it was in the higher range ...
the abs 003 controller has just the one same error :

1 Fault Found:

01314 - Engine Control Module

79-10 - Please Check Fault Codes - Intermittent



SO it looks like the original fix the garage did was on the engine manifold pressure - they i think said a smole test showed a leak - i think on a pipe to the break vacuum (would that make any sense?) and they fixed that .........

Quite enjoying the VCDS now :) thanks for getting me up and running with it

Any thoughts on ways to move this on / next steps very much appreciated ... i remember being pretty unclear on researching the 17961 code before .....

All the best
 

Attachments

You must log in or register to reply here.
Back
Top