Parking brake again

[Stuarta]

Hello all - I've been fighting with the dreaded parking brake or quite some time now.

The warning on the controller has been there since I bought the car (from the main dealer) 2 years ago.

Around a year or so ago, I replaced the rear pads (with VCDS / correct procedure) and all was well - for about 2 weeks, the the warning lamp was back. Switch still worked, brake held and released as per normal but warning stayed.

This morning, having driven 150kms yesterday without a problem, the whole thing gave up completely. (DTC readout at bottom of post). I first checked fuses (for the controller and both motors) which were ok. Then charged battery and finally replaced the battery with the spare that I bought a while ago when the car died on me 2 hrs away from home (has never repeated) - still no joy. Don't have time to pull the wheels off and check connectors today due to work - that will be the next thing. Any other suggestions?

Wednesday,16,October,2013,13:09:37:40931
VCDS Version: Release 12.12.0 (x64)

Address 53: Parking Brake Labels: 4E0-910-801.clb
Control Module Part Number: 4E0 910 801 HW: 4E0 907 801
Component and/or Version: EPB A01H019 H01 0190
Software Coding: 0000631
Work Shop Code: WSC 76700 819 177785
VCID: DCBD054B1FB4E4FE28B-8089
Fault Codes have been Erased

5 Faults Found:
16347 - Control Module - EEPROM Error
014 - Defective - MIL ON
Freeze Frame:
Fault Status: 11100000
Fault Priority: 4
Fault Frequency: 183
Reset counter: 255
Time Indication: 0
Date: 2064.00.00
Time: 00:00:00

Freeze Frame:
Voltage: 9.42 V
Count: 187

02596 - Rear Brake Pads Worn
008 - Implausible Signal
Freeze Frame:
Fault Status: 01110000
Fault Priority: 6
Fault Frequency: 1
Reset counter: 163
Mileage: 84088 km
Time Indication: 0
Date: 2013.04.28
Time: 12:24:56

Freeze Frame:
Voltage: 12.42 V
Count: 61

02433 - Supply Voltage for Right Parking Brake Motor (V283)
012 - Electrical Fault in Circuit - MIL ON
Freeze Frame:
Fault Status: 11110000
Fault Priority: 1
Fault Frequency: 2
Reset counter: 29
Mileage: 92264 km
Time Indication: 0
Date: 2013.10.16
Time: 11:04:03

Freeze Frame:
Voltage: 11.18 V
Count: 87

02432 - Supply Voltage for Left Parking Brake Motor (V282)
012 - Electrical Fault in Circuit - MIL ON
Freeze Frame:
Fault Status: 11110000
Fault Priority: 1
Fault Frequency: 2
Reset counter: 29
Mileage: 92264 km
Time Indication: 0
Date: 2013.10.16
Time: 11:04:02

Freeze Frame:
Voltage: 11.39 V
Count: 86

00446 - Function Limitation due to Under-Voltage
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 6
Fault Frequency: 4
Reset counter: 29
Time Indication: 0
Date: 2064.00.00
Time: 00:00:00

Freeze Frame:
Voltage: 0.00 V
Count: 188

[Delboy]

First of all, I would be checking wiring between the ecu and parking brake motor to rule out obvious stuff like corroded connectors / damaged wiring.

If that all checks out see if you can get a replacement ecu as thats where most of your faults are registered.

[Stuarta]

Thanks,

Will remove wheels and have a look after my night shifts the next couple of days. Unlikely to be corroded / moisture here - more likely dust.

BTW - yes, I did code the new battery and it was accepted.

In the meantime, is there any way of manually disengaging the epb? google has failed me on this.

Planning to get a new controller once I can get the damned thing mobile to collect it!

[Stuarta]

Sorry all - should be in the D3 forum - mods, can you move it or do I need to repost?

[Architex_mA8tey]

moved
Im sure there is a wind back tool for manually winding the parking brake on a D3 to back it off - DarrenJoe90 had to do it recently - check your user manual I think its like a z shaped allen key?

[Stuarta]

Thanks

Had a look in both the manual and the toolkit - manual has nothing to say at all about a procedure and the contents list for the toolkit has no mention - only possible suspects are the torx allen key and a plastic rod that's threaded at one end and has a couple of holes at the other but I suspect that's the "wheel mounting pin"

[snapdragon]

I suspect all but the first one are due to low battery and starting the car.

Clear all trouble codes, then do the Function Test:
Prerequisites:
Connect a battery charger as per repair manual.
Cycle the Parking Brake ON, then OFF first.
[Select]
[53 - Parking Brake]
[Basic Settings - 04]
Group 010
[Go!]
Activate the Basic Setting.
[ON/OFF/Next]
The brake pads are now opening and closing 3 times.
Wait 30 seconds after the the brakes stop making noise.
[Done, Go Back]
[Close Controller, Go Back - 06]
Clear all codes again.
Do you still get EPROM error?

[47p2]

There is no way to manually disable the EPB, it has to be done electronically

Saying that it might be possible to remove the motor and manually wind the plunger back, but then that would throw up more errors and could cause the ECU to do a wobbly

[Stuarta]

Snapdragon,

all trouble codes, then do the Function Test:
Prerequisites:
Connect a battery charger as per repair manual.
Cycle the Parking Brake ON, then OFF first.
[Select]
[53 - Parking Brake]
[Basic Settings - 04]
Group 010
[Go!]
Activate the Basic Setting.
[ON/OFF/Next]
The brake pads are now opening and closing 3 times.
Wait 30 seconds after the the brakes stop making noise.
[Done, Go Back]
[Close Controller, Go Back - 06]
Clear all codes again.
Do you still get EPROM error?

Tried that today - after leaving the charger connected for several hours on a brand new battery - switch is ineffective (disabled) and so impossible to cycle EPB. All other functions requiring the motors also disabled.

EEPROM error is consistent and has been since I bought the car - didn't do anything about it as the EPB always worked regardless!

[snapdragon]

Oh dear, some fault codes and error messages don't clear until you do that adaptation, that's why I recommended it. It is weird you had the code already and it worked. When you have time, pull the connectors, it's a simple enough job.
One of mine was full of water and corroded because Audi did a warranty replacement of the connector for the previous owner and it wasn't even sealed with a boot. This caused different error codes though, but maybe you have this combined with the original one?