Brozee

I've had a level control sensor fault on my A8 for over four years and over 100k miles. Still on original struts and original compressor at 157k. Knock on wood.

I wouldn't worry about the fault unless it changes or your suspension is drooping.

jeffkruse

Thanks for all your help guys, I am a novice at this stuff. FYI after I excuted the tests again and ran another auto scan the code is now gone. Thanks again. I will be posting something again soon for another DTC's

Panelhead

I clear twice and use the third scan. Sometimes one clear DTC's does not clear them all.

jeffkruse

I ran a scan and for 34 Level Control

The top of the scan shows
"34-Level Control -- Status: OK 0000"

but the body of the scan

Address 34: Level Control Labels: 4E0-910-553.lbl
Part No SW: 4E0 910 553 E HW: 4E0 907 553 E
Component: LUFTFDR.-CDC H05 4290
Coding: 0015510
Shop #: WSC 02503 444 01098
VCID: 2541171FEC14DD36C75-8070

1 Fault Found:
01772 - Signal from Level Control Pressure Sensor (G291)
008 - Implausible Signal - Intermittent
Freeze Frame:
Fault Status: 00101000
Fault Priority: 3
Fault Frequency: 3
Reset counter: 120
Mileage: 193458 km
Time Indication: 0
Date: 2015.03.23
Time: 19:02:39

Brozee

That's exactly what mine says. No worries.

jeffkruse

I was looking at the coding on my level control module and it was this:

Address 34: Level Control Labels: 4E0-910-553.lbl
Part No SW: 4E0 910 553 E HW: 4E0 907 553 E
Component: LUFTFDR.-CDC H05 4290
Coding: 0015510
Shop #: WSC 02503 444 01098
VCID: 2541171FEC14DD36C75-8070

In the VAGCOM a ballon window pop-up these procedures for coding the level control module. The only difference was the last digit is 0 and I have NAR which is 1. I changed it to 1, is that an issue? So my coding now reads 0015511. You might have to copy the url into your browser to see the VAGCOM coding procedures

Brozee

For what it's worth, yesterday when changing the oil in my 05 I did the level control process and went through step by step. The process won't necessarily say pass or fail for the record. Everything worked as it normally does, and yes, the error still persists.