Audi TT Forum banner

OBDeleven Caused a Headlight Error 01539

7.3K views 48 replies 3 participants last post by  steve-x  
#1 ·
So after fitting my new exhaust solenoid and bypass I went for a spin.

I’ve had a feeling recently my headlights are a but high (xenons).

So I decided to do a factory reset - I really shouldn’t play unless I know what I am doing lol.

In OBD11, module 55, adaptation channel 00, it days ‘perform factory reset’.

So I did this and it was immediately followed by an error:

View attachment 512817

Hmm, I thought, headlights didn’t move when doing the adaptation. I clear the error, the module resets, headlights go to the floor and come back up.

Wait 10 seconds, same error comes back up.

I am now stuck in a continuous cycle of this error /facepalm.

I went into basic settings,

View attachment 512818

I do this and it says learning - nothing happens.

Bit lost, I’ve reset the lights by running the adaptation, drove it round the block, key on and off, and now I have a lovely orange headlight warning and beep on my dash everytime I get in the car /joy.

Had a poke around and found this

View attachment 512820

Weirdly I’m sure I found a menu somewhere that said ‘g78 - not installed’. Maybe it only has a rear sensor?

Anyway, now I am screwed.

Any help please? :)
Image

Image

Image

Image

Image

Image
 
#4 ·
I have found the reset procedure, but OBD11 is different, I can’t be sure it’s doing the same as VCDS at the moment 🤔

Image


Also, in notes it shows rear sensor range should be minimum 50% maximum 85% 🤔 Mine is Zero, but not sure if this is a result of factory resetting.

Image


I found on another forum that in order to perform the factory reset the voltage at the rear sensor must be under 3v 🤔

“After spending some time over at the VAG-COM forum I was able to get a hint that one of my sensors may be reading 'out-of-range' when the car was level. Using VAG-COM I could see that the rear sensor was reading 3.63V on level ground. This turned out to be too high for the Basic-Settings to execute the "Adjust Headlights" function. I could confirm this by jacking up the rear of the car a little bit, which dropped the voltage below 3 (from the rear sensor) and then confirmed the "Adjust Headlights" function could be carried out (no error message). A better permanent fix was to slightly bend the clip that held the sensor arm to the rear control arm, to get the voltage around 3.3V with car on level ground. With this done I was able to complete the Basic Settings process without any issue and the Xenon fault code reset and stayed reset. No more annoying warning symbol on the dash. Total cost = $0”

I think there are a few possibilites:

1 - OBDeleven is not capable of performing the reset inline with instruction above.
2 - There are other conditions such as the car being perfectly level (but how would it know?) and parameters such as voltage in a certain range etc must be met for it to be successful.
3 - The rear sensor (if there indeed is no front one) is faulty, and it just so happens the factory reset has highlighted a problem (it is unable to reset due to faulty reading sensor). If this were the case, I would hope that a sensor error would show though?

Confused and need to sleep on it, pissed I’ve caused a problem by playing around though. I should have just adjusted them down a touch manually under the bonnet!
 
#5 ·
Thanks adding info here. I’m not convinced I can perform headlight adjustment / learning on obd11 or I am looking in the wrong place.

Level sensor reading out of range 🤔 Could be the voltage thing so the car is not level? Not sure why it is ready 0% also when notes (if correct) say should be 50-85%.

Image
 
#6 ·
One of the limitations of the OBDeleven, is it can't to all the Basic Settings, Initializations or Adaptations. i discovered this problem with my Convertible top when I had problems with the Roof Flap Servos. The OBDeleven could read the faults, but it required the VCDS to actually run the Initialization and clear the faults.
 
#7 ·
I shouldn’t have played with it really as now I’m stuck, I don’t know anyone this way with VCDS, and a dealer will rinse me to check it over (plus not convinced they will know what they are doing either!).

I’m not really sure which way to go first, check sensor, troubleshoot in ondeleven or try to find someone with vcds willing to help or 🤷🏻
 
#9 ·
More information dug up, this is for 8P but ‘could’ be similar…


Control unit adjustment

Select STG 55 (headlight range adjustment).
STG adjustment

ATTENTION: Channels 1-5 are fixed values set by the manufacturer and should NOT be changed.

-> Channel 00 (learning values)
The learning values (channels 1-9) are reset to the values specified by the manufacturer.

-> Channel 01 (dynamic control strategy)
Default value: 4

-> Channel 02 (front adjustment limit low value)
Default value: 1

-> Channel 03 (front adjustment limit high value)
Default value: 7

-> Channel 04 (rear adjustment limit, low value)
Default value: 7

-> Channel 05 (rear adjustment limit, high value)
Default value: 13

-> Channel 06 (warning lamp)
Control of the warning lamp.

0 - disabled
1 - activated

-> Channel 07 (terminal 61)

0 - deactivated (reference run to Kl.15 on)
1 - activated

-> Channel 08 (plausibility of the sensors)

0 - disabled
1 - activated

-> Channel 09 (error lamp)
In the actuator test.

0 - disabled
1 - activated

-> Channel 60 (learning values channel 1)
The learning values of channel 01 are reset separately to the values specified by the manufacturer.

-> Channel 61 (learning values channel 2)
The learning values of channel 02 are reset separately to the values specified by the manufacturer.

-> Channel 62 (learning values channel 3)
The learning values of channel 03 are reset separately to the values specified by the manufacturer.

-> Channel 63 (learning values channel 4)
The learning values of channel 04 are reset separately to the values specified by the manufacturer.

-> Channel 64 (learning values channel 5)
The learning values of channel 05 are reset separately to the values specified by the manufacturer.

-> Channel 65 (learning values channel 6)
The learning values of channel 06 are reset separately to the values specified by the manufacturer.

-> Channel 66 (learning values channel 7)
The learning values of channel 07 are reset separately to the values specified by the manufacturer.

-> Channel 67 (learning values channel 8)
The learning values of channel 08 are reset separately to the values specified by the manufacturer.

-> Channel 68 (learning values channel 9)
The learning values of channel 09 are reset separately to the values specified by the manufacturer.
 
#10 ·
Headlight range adjustment

Control unit basic setting

Select STG 55 (headlight range adjustment).
STG basic setting

Select measured value group 001

Now adjust the headlights manually using the adjustment wheel.

Select measured value group 001

The control unit now “learns” the control position of the headlights.



Control unit coding

Select STG 55 (headlight range adjustment).
STG coding

00001 - Front wheel drive (PR-1X0)
00002 - Four-wheel drive (PR-1X1)
 
#11 ·
I followed the procedure above Ignition on, lights off, parking brake off > Adaptation 000, ‘perform factory reset’.

Then basic setting channel 001, it states ‘wait’ and glitches every now and then with more details but it flashes up so fast I cannot catch it. If I start 001, then scroll to 002, headlight error goes out.

Next time I cycle the ignition the error comes back.

I think I need to try an android device maybe? Have had this problem before though, I do not know anyone with one! Actually my headunit is android, maybe I can try that…

I still cannot see any % on rear sensor where it says it should be 50-85%, currently sat at zero…
 
#12 ·
Before you selected "perform factory reset", did you happen to save the original coding values for all your Channels? Hopefully that answer is "Yes".

If the codes in Channel 55 have changed, you might be able to just enter your original values.

Looking under Control Unit 55 coding, this is what I have:

0000011 - Audi TT with magnetic ride

Image
 
#24 ·
One thing about obdeleven, I am not sure if it is an ios bug, but coding does not always show up - I’ve not actually see. It on module 55 yet, but had this issue before with cruise. I think if I accessed the module without first going to coding then back out, coding vanished, I will plug in and go to the module without doing anything else and see if coding is there.
 
#16 ·
Thanks will do.

I was hoping the procedure would work, I mean, it seems common enough on other audi models of a similar age including A3 8P.

Before factory reset my lights seemed to be pointing high (hence doing it). I assume if the rear sensor is working the values should change, but of course, the factory reset could have also messed that up :/
 
#19 ·
Well....now we're both screwed.... :mad:

I first ran a complete auto scan to make sure there were no faults. And as expected, there were none.

I then tried the Adaptation "Perform factory reset" and Basic Setting and sure enough, got the same results you did!

Threw a error icon on the DIS and I now can't clear the 01539 fault that didn't exist before the Adaptation. Tried the Adaptation again and the Basic setting with no luck.

I'm going to break out the VCDS and see if I can resolve this issue.

I also sent and email to the Voltas team at OBDeleven describing this problem in hopes they have a fix since it was their device that caused this problem.

Image
 
#21 ·
Not sure what's going on, but this is what my live data came back with. What doesn't make any sense is I have never had a fault with the headlights, and it looks like OBDeleven has somehow caused a problem by performing the Adaptation.

Notice the number (55) is green, as this was recorded BEFORE the Adaptation.

I'm going to let the car sit for about half an hour and make sure the car goes into 'sleep' mode (emergency flasher switch is no longer illuminated) and then see if the DIS warning is still present and then run another scan and see what the Live Data looks like.

I will run a VCDS later this afternoon and see if I can sort it out.

Image
 
#22 · (Edited)
I guess at least (hopefully) you still have sensors and they are showing values.

I wonder if mine really does only have one rear one installed from factory 🤔 I hope the ‘factory reset’ hasn’t screwed a ton of settings on mine 🤦

If yours says zero too and reads like mine then for sure obdeleven has screwed us.
 
#23 ·
For me, if I follow the reset procedure, ignition on, parking break off, lights off, module 55, channel 000, I only get option to slide for factory reset. I do this and cannot hear the lights move.

I go to basic settings, channel 001, it just says ‘wait’ if I wait it never seems to do anything (just spinny circle).

Image


If I slide to activate it then shows the following:

Image


If I scroll to 002 it just shows ‘on’ and headlught warning clears. I can go back to read errors in module 55 and it is gone. But cycling ignition or lights on and off the error re-appears.

I still have the weird issue of no front sensor installed 🤷🏻 Plus no values showing from rear sensor, but also no sensor fault 🤷🏻🤦😩
 
#25 ·
So based on my findings, the problem has nothing to do with the codes or changes to the codes, but simply with how OBDeleven works (or doesn't).

Using VCDS, I started by running a fault scan which reported the fault. Then I ran a Basic Setting which cleared the fault and the DIS warning.

After I did that, I again ran OBDeleven, attempted the Basic setting and triggered the fault. But was not able to run the OBDeleven Basic setting to clear it.

But I think I understand why...

With VCDS, go to Address 55, and select Basic Setting - 04
Image

From the Drop down menu, select Adjustment Position and Adjustment Learning -
Image

Click the ON/OFF/Next button and the Adjustment Status will show "Wait".
Let it run for about 30 seconds or so.
Image

Then click ON/OFF/Next again and the Adjustment Status changes to "Adjust" and "Headlights" -
Image

Then click ON/OFF/Next again and you'll see "Reg. Position" and "Learned".
Click Done. Go back.
Image

The DIS fault warning will clear and there will be no fault codes reported.
Image


With OBDeleven, (shown below) I managed to get these screens by pressing on the green dot at the bottom, but it simply didn't work. If you get into this again, notice the blue line that runs from left to right below the word On under Status. This may be trying to emulate the VCDS ON/OFF/Next button, but is just really, really slow.

Image


I have noticed OBDeleven is significantly slower when running a fault scan. With VCDS I can run a full fault scan of all Addresses (Control Units) in less than 45 seconds. Where OBDeleven can take several minutes.

You might want to go back into the Adaptation and see if you can just let it run for a few minutes. Unfortunately I didn't have any luck, but fortunately I was able to sort everything with VCDS.

Notice the green button did go grey on the last attempt, so I guess this is where it couldn't perform the Adaptation and shut off the ability to run it any more.

Image
 
#26 ·
Image


Nice! Thanks for this. Shame I didn’t get to see if the obdeleven screwed with your sensor values before you fixed it 😂

I’m using IOS, my OBD eleven doesn’t get as far as yours. I can only Slide at the bottom to start basic settings, or slide to stop it, there is no way of going ‘next’. At least yours seems to have the dot to press to go next.

Sadly my android headunit will not detect the obdeleven module, so I am stuck at the moment - seems my app won’t even do what its supposed to, let alone there possibly being a bug with it anyway :/

edit this is all I can do, slide and it goes to headlight, then can only slide to stop, so it seems unable to complete the procedure
 
#27 ·
" Shame I didn’t get to see if the obdeleven screwed with your sensor values before you fixed it 😂 "

No, I don't think so. I think it just wasn't able to run the Adaption properly. I suspect it's a bug with OBDeleven for both iOS and Android. It might be that VCDS made that ON/OFF/Next button intentionally in such a way that it can't be easily copied.

IMHO...and this is pure speculation on my part...its probably where OBDeleven got their coding to start with since you can reverse engineer most of the VCDS data files, or at least any that end with LBL. And why many of the Basic Setting and Adaptations in OBDeleven don't work like they should.