[SwissJetPilot]

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.

 

[steve-x]

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.

 

[steve-x]

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).

If I slide to activate it then shows the following:

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 🤷🏻🤦😩

 

[steve-x]

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

View attachment 512845

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.

 

[SwissJetPilot]

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

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

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

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

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

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

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.

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.

 

[steve-x]

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

 

[SwissJetPilot]

" 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.

 

[steve-x]

Ahh right. In which case any adaptation in obdeleven should be approached with extreme caution. Thankfully you had vcds to fix, unfortunately I do not :/

 

[SwissJetPilot]

Well, you can't go wrong with VCDS that's for sure. Certainly not as convenient to set up and use, but it works like its supposed to!

I will be curious to see what Voltas has to say about this. Hopefully they can look into it and explain why it causes a fault that wasn't there in the first place, and why the Basic setting doesn't work.

 

[steve-x]

If they respond

Problem is its not just VCDS, I also need to buy a laptop etc, so its a chunky outlay. i’ve managed to do everything I need so far with OBDeleven, so it has been good. Seems excessive to spend £600 plus to fix my headlight fault :/

 

[SwissJetPilot]

True... Figure £200 for VCDS and about that much for an old laptop.

This is what I have, the HEX-V2. I bought mine from German VCDS vendor for about that same price nearly 10-years ago.

As you know, it does require laptop with Windows but the VCDS software updates are free and you get way more help from Ross Tech since you can access their Forum. Something OBDeleven doesn't offer.

You can get a halfway decent laptop from Amazon for around £100-150. Or just ask around and see if anyone you know has an old "beater" they'd be willing to sell cheap.

https://vcdsdiagnostics.co.uk/

 

[TT'sRevenge]

If they respond

Problem is its not just VCDS, I also need to buy a laptop etc, so its a chunky outlay. i’ve managed to do everything I need so far with OBDeleven, so it has been good. Seems excessive to spend £600 plus to fix my headlight fault :/

Hopefully someone on here that's local to you and has VCDS will be willing to help out

There used to be a "VCDS locator" website where ppl with it that were willing to help others would sign up and put their location on there and ppl could message them. But I'm not sure it even still exists or if anyone uses the site if it does.

Better idea is just someone here is local with you and willing to help out?

 

[SwissJetPilot]

It's in the Stickies...

 

[SwissJetPilot]

For your own interest, here's the data file for Address 55 -

; Copyright © 2006+ Ross-Tech, LLC
; Audi A3 (8P) / Audi A4 (8EC/8ED) / Audi A6 (4F) / Audi A8 (4E)
; Audi Q7 (4L) / Audi TT (8J) / VW Scirocco (13)
; Component: J431 - Headlight Range (#55)
; P/N: 8P0-907-357-??? / 8P3-907-357-???
;
; This file is part of a label file package, make sure you have all of the following files.
;
; 8P-55.LBL
; 8P0-907-357.LBL
;
; includes measuring blocks, basic setting, adaptation, coding and selective output tests created on 30/May/2006 by Sebastian Stange (Sebastian@Ross-Tech.com)
;
; last modification on 18/Apr/2012, requires VCDS 805.0 or newer
;---------------------------------------------------
;
; measuring blocks & basic setting
;
;---------------------------------------------------
001,1,Voltage,(Terminal 15),Specification: min. 10.5 V
001,2,Light,(Terminal 56b),Specification: ON/OFF
001,3,Vehicle Speed
001,4,Acceleration
;
B001,0,Adjustment Position && Adjustment Learning
B001,1,Adjustment,Status,
B001,2, , ,
B001,3, , ,
B001,4, , ,
;
002,1,Front Sensor (G78),(actual),Specification: 12.5...50.0 %
002,2,Rear Sensor (G76),(actual),Specification: 50.0...87.5 %
002,3,Actuator Motor,Activation
002,4,Time Constant
;
003,0,Brake && Engine Status
003,1,Brake
003,2,Brake Status,,Range: ON/OFF
003,3,Engine
003,4,Engine Status,,Range: ON/OFF
;
004,1,Voltage at,Light Input
004,2,Sensor,Voltage Supply
004,3,Basic Frequency,Sensor Front (G78)
004,4,Basic Frequency,Sensor Rear (G76)
;
005,1,Front Sensor (G78),(learned)
005,2,Rear Sensor (G76),(learned)
005,3,Movement,Front Suspension,Range: -127.0...+128.0 mm
005,4,Movement,Rear Suspension,Range: -127.0...+128.0 mm
;
125,0,CAN-Databus Communication (Powertrain)
125,1,Brake Electronics,(J104),Range: ABS 1/ABS 0\nSpecification: ABS 1
125,2,CAN-Gateway,(J533),Range: Gateway 1/Gateway 0\nSpecification: Gateway 1
125,3,Power Steering,(J500),Range: Steer. ang. 1/Steer. ang. 0\nSpecification: Steer. ang. 1
125,4,Engine,Electronics,Range: Engine 1/Engine 0\nSpecification: Engine 1
;
126,0,CAN-Databus Communication (Powertrain)
126,1,Instrument Cluster,(J285),Range: Instruments 1/Instruments 0\nSpecification: Instruments 1
126,2,Level Control,(J197),Range: Level 1/Level 0\nSpecification: Level 1
;
225,0,Electro Magnetic Compatibility (EMC) Counter
225,1,Brake Electronics,(J104)
225,2,CAN-Gateway,(J533)
225,3,Power Steering,(J500)
225,4,Engine,Electronics
;
226,0,Electro Magnetic Compatibility (EMC) Counter
226,1,Instrument Cluster,(J285)
226,2,Level Control,(J197)
;---------------------------------------------------
;
; adaptation
;
;---------------------------------------------------
A001,0,Dynamic Control Strategy
A001,5,Dynamic Control Strategy
A001,6,4 = Standard
;
A002,0,Adjustment Range Front (Low Value)
A002,5,Adjustment Range Front (Low Value)
A002,6,1 = Standard
;
A003,0,Adjustment Range Front (High Value)
A003,5,Adjustment Range Front (High Value)
A003,6,7 = Audi A3 (8P)
A003,7,13 = Audi A4 (8E) / Audi A6 (4F)
;
A004,0,Adjustment Range Rear (Low Value)
A004,5,Adjustment Range Rear (Low Value)
A004,6,1 = Audi A4 (8E) / Audi A6 (4F)
A004,7,7 = Audi A3 (8P)
;
A005,0,Adjustment Range Rear (High Value)
A005,5,Adjustment Range Rear (High Value)
A005,6,13 = Standard
;
A006,0,Warning Lamp Enabling
A006,5,Warning Lamp Enabling
A006,6,0 = Warning Lamp Activation suppressed
A006,7,1 = Warning Lamp Activation enabled
;
A007,0,Terminal 61 Function Enabling
A007,5,Terminal 61 Function Enabling
A007,6,0 = Terminal 61 Function locked (Reference Run after Terminal 15 ON)
A007,7,1 = Terminal 61 Function enabled (Reference Run after Engine Start)
;
A008,0,Sensor Plausibility Enabling
A008,5,Sensor Plausibility Enabling
A008,6,0 = Sensor Malfunction Plausibility locked
A008,7,1 = Sensor Malfunction Plausibility enabled
;
A009,0,MIL Enabling
A009,5,MIL Enabling
A009,6,0 = MIL locked (in Output Test)
A009,7,1 = MIL enabled (in Output Test)
;
A010,0,Tourist Solution
A010,5,Tourist Solution
A010,6,When driving in countries where driving is performed on the
A010,7,opposite side as in the native country the headlights must
A010,8,be changed over to avoid blinding the oncoming traffic.
A010,9,
A010,10,0 = Disabled
A010,11,1 = Enabled
A010,12,
A010,13,Note: Only supported for 8P0-907-357-C @ 0020 or newer!
;---------------------------------------------------
;
; coding
;
;---------------------------------------------------
C00,Headlight Range Control (J431) Coding
C01,0000001 = Audi A3 (8P) Front-Wheel-Drive (FWD)
C02,0000002 = Audi A3 (8P) All-Wheel-Drive (AWD)
C03,0000003 = Audi A6 (4F) with Steel Suspension
C04,0000004 = Audi A6 (4F) with Air Suspension
C05,0000005 = Audi A4 (8E) & Audi A4 Cabriolet (8H)
C06,0000006 = Audi A8 (4E)
C07,0000007 = Audi Q7 (4L) with Steel Suspension
C08,0000008 = Audi Q7 (4L) with Air Suspension
C09,0000009 = Audi TT (8J) with Steel Suspension and Front-Wheel-Drive (FWD)
C10,0000010 = Audi TT (8J) with Steel Suspension and All-Wheel-Drive (AWD)
C11,0000011 = Audi TT (8J) with Magnetic Ride
C12,0000012 = Audi A3 (8P) with Single Frame Grill (SFG)
C13,0000013 = Audi A3 (8P) Cabriolet
C14,0000015 = VW Scirocco (13) with Standard Suspension
C15,0000016 = VW Scirocco (13) with Dynamic Chassis Control (DCC)
;---------------------------------------------------
;
; selective output test
;
;---------------------------------------------------
T1540,Headlight Range Control: Adjusting to Lowered Position
T1541,Headlight Range Control: Adjusting to Raised Position
T2232,Headlight Range Control: Adjusting to Delivery Position

 

[TT'sRevenge]

It's in the Stickies...

LOL I hadn't even noticed we had our own one here! Haha yeah I guess that works much better then!

 

[SwissJetPilot]

Just spent some time in the OBDeleven forum and many people are reporting problems with multiple Adaptations in various control units. So be very cautious about using them.

I actually posted a warning about this issue for other TT owners since OBDeleven/Voltas is obviously unaware of the problem.

 

[steve-x]

I fixed it using an android tablet.

Igniton on
Parking brake off
Parked on level ground (I hope time will tell)
Adaptation 00 > Perform factory reset
Basic Settings 01
Press and hold green dot it changes to learning
Wait a few seconds, then press and continue to hold green dot it changes to control position
Press and keep holding and it says adapted

Now at this point I was still pressing and holding for like a minute and the dongle disconnected. But I noticed the error on my cluster had gone.

I reconnected and there were no errors 🤷🏻

I can now see sensor is at zero, but if I bounce on the suspension it changes.

Can also see values on suspension and sensor now too, and again changed when I bounce on suspension.

Cycled ignition and lights and it ‘appears to be fixed’ 🤷🏻🤷🏻

 

[steve-x]

I must also say, I had no idea up until now rhat the android app differs, it also is able to add vehicle data (in profile), and code the module without it bugging and sometimes vanishing.

The biggest difference is the green tick that you can press and hold, the it would seem press and hold again to move on. On IOS you just have the slide bar to start, slide again back to stop. So this must be a limitation of trying to integrate the functionality and software into IOS.

I borrowed this tablet, but will be on the hunt for a cheap used android 6+ tablet for coding and other features of obd11. I think although I have coded with ios and it has done me the past year well, I will reserve coding only for android and just use ios for reading codes and live data.

 

[TT'sRevenge]

I'm not going to say what I'd usually say about Crapple here and not using any of their "stuff" for anything technical or serious, because I understand you're just trying to get out of the mess you're now in and that kind of thing is not helpful LOL

But even with Android, isn't SJP using Android? And didn't he have the exact same thing happen and still had to fix it with VCDS (in the other thread)? Or did I misunderstand that thread? If that's true then I don't think it matters whether you're using iPhone/iPad or a real device, it's just going to do the same thing, isn't it? Or did using the Android version fix your issue now?

 

[SwissJetPilot]

It might be I didn't wait long enough when I was trying to get it to work, so maybe Steve-x found the solution. Patience.

As I commented, OBDeleven takes nearly four times longer than VCDS to run an identical fault scan, so for whatever reason their software is just s...l.....o.......w.

I will try it again tomorrow and see if I can duplicate his results since it's not an issue to fix it with VCDS if I can't. TBO I am not sold 100% with OBDeleven's Applications which is why default to VCDS when I have to make any serious changes.

This seems to be echoed in the OBDeleven Forum too by other people who are finding out OBDeleven pretty much sucks when it comes to Adaptations and Basic settings.