|
Post by paaudiman on Jul 20, 2024 14:20:26 GMT
Good Day, I am a new OBDEleven user and I apologize in advance if my questions are basic. I have searched the forums for an answer to my topic but it seems I might be the only one 'dumb' enough to go this route.
I purchased a 2015 Audi A3 Cabriolet Prestige S-Line 2.0T Gasser from an insurance auction. The vehicle had minor front end damage which included both headlights. The original headlights were led headlights. I decided to go with BI-Xenon to replace both headlights. After installation and setting Low Beams to Bi Xenon I am left with two issues. The first is that neither left or right turn signals are working. I received the errors below for each turn signal. Not sure how to proceed with fixing these errors. I assumed a change needs to be made in Central Electronics, but did not want to make things worse by guessing.
The second issue is that the HighBeams are no working at all. I do not have any error codes present for this and nothing on dash. I am completely lost on this one.
Thank you for any help.
OBDeleven vehicle history log
Date: 2024-07-20 09:46:52
VIN: WAUWFLFF8F1114608
Car: Audi
Year: 2015
Body type: UNKNOWN
Engine: CNTC kW ( hp) l
Mileage: 141898 km
---------------------------------------------------------------
09 Central Electrics
System description: BCM MQBAB MNA
Software number: 5Q0937085AB
Software version: 0137
Hardware number: 5Q0937085AB
Hardware version: H18
Faults:
B11EA15 - Right front turn signal bulb
Open circuit/short circuit to B+
static
Priority - 2
Malfunction frequency counter - 1
Unlearning counter - 174
km-Mileage - 141898 km
Terminal 15 status - On
Terminal 50 status - Off
Voltage - 11.8 V
Outside air temperature - 25.0 °C
Status Bremslichtschalter (HW) - Off
Status Bremslichtschalter (CAN) - Off
Off - operated
Parking light - not activated
Automatic high beam assist - not activated
Low beam - not activated
Parking light left - not activated
Parking light right - not activated
Letzte Weckursache/ Werte [00;2E] - keine Störschutzursache
CAN-Bus aktiv - On
date - 2024-07-11 20:16:30
B11E815 - Left front turn signal bulb
Open circuit/short circuit to B+
static
Priority - 2
Malfunction frequency counter - 1
Unlearning counter - 174
km-Mileage - 141898 km
Terminal 15 status - On
Terminal 50 status - Off
Voltage - 12.1 V
Outside air temperature - 26.0 °C
Status Bremslichtschalter (HW) - Off
Status Bremslichtschalter (CAN) - Off
Off - operated
Parking light - not activated
Automatic high beam assist - not activated
Low beam - not activated
Parking light left - not activated
Parking light right - not activated
Letzte Weckursache/ Werte [00;2E] - keine Störschutzursache
CAN-Bus aktiv - On
date - 2024-07-11 18:30:35
|
|
|
Post by dv52 (Australia) on Jul 20, 2024 21:40:18 GMT
hmm.........posting a part SCAN is a common failing on forums - I have never understood why folk believe that this is preferable!
It's a bit like assuming that everyone reads a novel in the same way - which of course is nonsense because whilst the general theme in a book is commonly understood by all readers, individual readers comprehend the words in a book differently! The same is true about a SCAN - every piece of data in the report adds value to the imperfect medium of remote diagnostics via a forum.
Editing a SCAN by removing information (presumably because OP wants to keep the post "simple") has large down-side consequence - it cloaks the ability of others to understand the basics about the car like how it is built and what equipment-options are installed in the vehicles. And it destroys the readers' understanding of the context of the faults/errors on other modules on the car's CAN network. This latter consequence is particularly relevant in the case of errors related to retrofitted headlight fittings because HID/LED lamps are managed by multiple modules (i.e. modules other than the central electrics module)
So, lets start again - please post-up an UNEDITED copy of the SCAN for this car - as an attachment. I guess that you can delete the VIN if you want albeit I have also never understood why folk want to keep the VIN secret - it's available for all to see on the front windshield!
Also, we need to know a whole lot more about the change process and the related equipment. Unfortunately "the original headlights were led headlights. I decided to go with BI-Xenon to replace both headlights" doesn't tell us much (no offense intended)!
Please provide more words about how this change happened - what specific modules were changed on the car. The unedited SCAN will tell us the software/part numbers of the existing modules - but what are the specifics of the deleted modules? Where were the new modules sourced (include URL details) - it matters! Also, what country is this - again, it matters? Finally, what coding changes were made after the physical fitment of the equipment?
Don
|
|
|
Post by paaudiman on Jul 21, 2024 13:07:35 GMT
Thank you for your reply Don....I apologize for the 'edited' scan. I merely dumped the data from the Central Electronics module and not the entire car. Point taken. I have attached the entire scan as txt file. As for your point about the 'change process'. As stated vehicle was in front end collision. Original Headlights were models 8V0.941.034.B and 8V0.941.033.B (I provided and image of passenger side for reference). New Headlights are models 8V0.941.044.B and 8V0.941.043.B (Image provided of Passenger side for reference). The replacement headlights are both new. I installed them directly with no modifications. This was as directed from my Audi dealer whom I purchased the lights from. Maybe this is part of the problem. The country is United States. The lights were sourced directly from the Audi Dealer (links below) parts.audiusa.com/p/Audi_2015_A3-20L-AT-Quattro--Prestige-Convertible/Headlight-Assembly/52385492/8V0941043B.htmlparts.audiusa.com/p/Audi_2015_A3-20L-AT-Quattro--Prestige-Convertible/Headlight-Assembly/52385515/8V0941044B.htmlI have not made any coding changes at all. Currently the Low Beams and Parking lights illuminate as expected. No high beams (no dashboard errors) No Front Turn Signals (Dashboard Error for both sides) Please let me know what additional information I can provide. I am very good at following directions...usually. Thank you again. Attachments:OBDeleven_Log.txt (136.96 KB)
![](//storage.proboards.com/6321844/thumbnailer/qNDRyJDcjbkhjfgPQzHB.png)
![](//storage.proboards.com/6321844/thumbnailer/PpGSfGgqSjhVSHyHlWxO.png)
|
|
|
Post by dv52 (Australia) on Jul 22, 2024 0:24:24 GMT
paaudiman : Arrhh................ that's much better -thanks for posting-up the additional data!! I hope that you didn't read my last reply as personal criticism because it wasn't meant so - I intended the content of my response as a general comment for a colleague that was new to this place. OK - this is a "Yankee" car! For reasons that are obvious because I live on an island in the very, very "deep South", I don't get to see many (any) MQB platform cars that are North America Region (NAR) models. This is an important caveat for ALL my comments below because NAR models are significantly different to Rest-of-World (RoW) models.
When you said in your first post " I am a new OBDEleven user", are you also new to coding modules using a diagnostic device in general? If so, maybe read THIS as a primer to my words below (clearly my link won't make you a fluent OBD11 user - but hopefully the material will acquaint you with the terms that I use) I start the arcane techno-babble part of my response with a pet-peeve: I hate the way that some OBD11 SCANs omit reporting the module long-code string. I have never understood why this happens, but it occurs on your SCAN. As I've said many times in this place, VCDS produces a far more informative SCAN (the layout is more logical, the module information is more nuanced and the file format is more usable) - IMO, of course!!
First some background words: - After you read the information in my link, you will understand that the prime purpose of a module long-code string is that it tells the module what equipment options were installed into the car on the vehicle assembly line. You can think about the Byte/Bits in the long-code string as being software driven switches that turn ON/OFF subroutines inside the module depending on the buyer's chosen options for the car. And, to further complicate already complex matters, the values in the module long-code string use hexadecimal arithmetic (look it up) - not more familiar decimal numbers!!
As support to long-code, the values in the adaptation channels in the module then direct the module how to operate those subroutines that are activated. - The "convenience" functions in this car (like the headlights) are principally managed by the central electrics module which lives at address 09 on the CAN network and the Headlight Regulation module which has an address 55 - see your SCAN report. The 09 module has in excess of 1,000 adaptation channels!
Even though I don't know the value of the long-code string on the central electrics module on this car - logic dictates that currently the module believes that it should control the original factory fitted LED fittings. Of course the module's understanding is wrong because you retrofitted HID headlights. I suspect that this inconsistency is at base of the high-beam problem. So we need to change the software switches on the long-code string to align with the new headlight techology (I think) and to do this - alas, I need more information. Please provide a Backup of the central electrics module as an attachment - read HERE. For the turn-signal problem, my hunch (guess really) is that we need to modify the "other" module coding variables - meaning the adaptation channels, again in the central electrics module.
But, to understand this change, I first need to introduce you to a concept that I call a "Leuchte-set". Each of the 35 x exterior lights on MQB platform vehicles like this car is controlled by a separate "Leuchte-set" - which is a group of 19 x adaptation channels that all start with the name "Leucthe" (German for "light"). Each individual Leuchte-set controls a specific pin on the central electrics module and the Leuchte-set can be programmed to suit the type of lamp that is connected to that pin. There are a total of 665 x Leuchte channels in the module (i.e. 35 x 19)
On the original LED headlight fittings, the front turn signals were controlled by an additional "slave" module that lived inside each of the left/right headlight housings. However, on the new HID headlight fittings, each of the turn-signal lamps are driven directly by a pin on the central electrics module. So, my hunch is that we need to change the way that the central electrics module drives the turn-signal pins by modifying a Leuchte channel in the respective Leuchte-sets However, I need your help in pursuing my hunch above! It's not clear to me how the new headlight fittings manage turn-signals lamps - in fact, I'm not entirely certain that 8V0941043B headlights have embedded turn-signals? Please confirm how the turn-signals work on your new headlights and if indeed the blinkers are integrated into the the headlight housings, are they LED, or incandescent bulbs? Don
|
|
|
Post by paaudiman on Jul 22, 2024 14:30:09 GMT
Once again thank you for your response Don. I took absolutely no offense or exception to anything you wrote. You are trying to help me and I am more than grateful. I am technologically savvy and conceptually understand the long coding in various modules. I was aware the likely fix would end up being in Central Electronics and that it would be a matter of finding the right pin coding. Hope that help in describing my aptitude. The New Headlights do have an integrated turn signal. It is a small bi-xenon amber / orange colored bulb with a part number of N10776302. I have attached the exploded parts diagram and a listing for the bulb. Also here is the link to the exploded view if that helps at all. parts.audiusa.com/a/Audi__/52385492__6700547/FRONT-LAMPS-HEADLAMP-COMPONENTS/1312025.htmlI have also attached the Central Electrics - 09 Backup Attachments:![](//storage.proboards.com/6321844/thumbnailer/SHJSjIuIyvRXOojyfOGP.png)
![](//storage.proboards.com/6321844/thumbnailer/jhOI0uFlPdrykauZzlgz.png)
CentralElecBackup.txt (72.34 KB)
|
|
|
Post by dv52 (Australia) on Jul 22, 2024 22:02:01 GMT
OK - again, thanks for the new information! I don't believe that the turn-signal lamp is "a small bi-xenon amber / orange colored bulb". Purely from eyeballing your picture of the bulb, I can see the tell-tail filament of an incandescent lamp inside the glass bulb. And from a technical perspective, there is no need for a turn-signal lamp to have bi-xenon technology since it's only a blinker!!
So, again I'm flying blind because this is a "Yankee" car and I don't have access to the module Backup data - but I suggest that you try the following (I assume that you are using the iOS version of OBD11): - Ignition-ON, engine-OFF (IOEF)
- Fire-up OBD11 software and connect to the dongle
- On the Home screen, press the icon highlighted with a star as indicated on the screen below
![](https://i.imgur.com/XlaA6GS.png?1)
- On the Control Units screen, select the Central Electrics module
![](https://i.imgur.com/HWnw17n.png?2)
- Scroll down the Central Electrics module screen and select Adaptations
- Enter "B36" into the search box and select Leuchte 0 BLK VL B36 (this is the Leuchte-set for the left-side front turn-signal lamp)
- change the values as follows:
- Lasttyp >12 - Blinkleuchten
- Dimmwert AB > 100
- Implement the changes above using the "slide" and follow the prompts. When/If a security code is requested, select 31347
- Back on the Adaptations screen (step 6. above), enter "VRB20" into the search box and select Leuchte1BLK VRB20 (this is the Leuchte-set for the right-side front turn-signal)
- Repeat Step 7. and Step 8. above
- Exit OBD11 software and don't forget to unplug the dongle
Don
|
|
|
Post by paaudiman on Jul 23, 2024 0:00:04 GMT
Thanks Don. Unfortunately those settings did not work. No change.
|
|
|
Post by dv52 (Australia) on Jul 23, 2024 0:43:16 GMT
paaudiman: Bummer!! OK - it's time to stop guessing and to bring-out the heavy-guns (I chose the analogy because I understand that ALL Americans like guns - I don't)!. Restore my suggested changes back to their original values and post-up a copy of the Backup for the central electrics module - please Don
|
|
|
Post by paaudiman on Jul 23, 2024 4:01:28 GMT
It's true...allot of Americans like their guns. I am not one of them. Posted backup Attachments:CentralElecBackup.txt (72.34 KB)
|
|
|
Post by dv52 (Australia) on Jul 24, 2024 22:10:10 GMT
paaudiman : Interesting information in your backup file!! First, the front turn signals: Your back-up file confirms the assumptions that I embedded into my suggested changes in my previous post. On this car, the 2 x Leuchte-sets that drive the front turn-signals are Leuchte 0 BLK VL B36 and Leuchte1BLK VRB20. So, all else being correct - I would have thought that my suggested changes would have worked. But your observation is that my tweak didn't work! I'm convinced that the tweak is correct - which means that there are additional steps needed to address the disabled turn-signal problem For the High-beam problem, it appears from your back-up file that the central electrics module on this car does NOT control the high-beam lights via a pin on one of its 3 x sockets. For reference, I've included a picture at the end of this reply showing these sockets (BCM = central electric module).
Normally on MQB platform cars, the Leuchte-sets that control non-incandescent high-beam lamps are: - Leuchte10SHUTTER LB23
- Leuchte11SHUTTER RB22
As you can see from the back-up data, the 2 x Leuchte-sets above have been factory disabled (notice that ALL "Lichtfunktion" channels and the "Lastyp" channel are coded with the value not active) As I said in a previous reply, the connections that these Leuchte-sets control are as I have highlighted in the Leuchte-set name above. The fact that these Leuchte-sets are factory disabled means that almost certainly there will be NO wires connected to pin #23 and pin #22, Socket B in the factory loom that eventually terminates on the left/right 14 x pin headlight connectors. Your new HID headlights need these missing wires to operate the high-beam shutters inside the fittings!
My hunch is that on this car, the original LED high-beam lamps were controlled either by the 55 Headlight Regulation module, or more likely, by the CAN network directly!
I assume that you simply plugged the new headlights into the 14 x pin factory headlight connector on the car without altering the pin positions, or without adding a cross wiring harness
So, if my deductions are correct (and again, remember my previous caveat about this being a NAR model), my hunch is that additional wiring changes will be required to fix both the turn-signal and the high-beam problems.
I suggest that you eyeball the 14 x pin headlight connectors and look particularly at those pins on the female part of the connector that have terminated wires - does the mating pin on the male part of the connector also have a terminated wire? And, if so, is the physical size of both wires the same? The physical wire size tells you whether the wire is a CAN signal (small wire diameter), or a power-supply for the lamp (large wire diameter).
Note the pin numbers and the socket gender where a mismatch occurs.
Don
|
|
|
Post by paaudiman on Jul 26, 2024 19:27:45 GMT
Don, Thank for the reply. Your assumption is correct. I did simply plug the lights in with existing plug and no adapters or modifications. I will take a look at the pin connectors tomorrow and reply with findings. Thank you again!
|
|
|
Post by paaudiman on Jul 28, 2024 20:08:07 GMT
Don...wanted to close this one out. I had a long conversation with an Audi specialist. I wont recap but the absolute nightmare this turned out to be is just to much. I ended up buying a set of the LED lights. Unreal how Audi make this so difficult.
Wanted to thank you for your assistance and wish you the best.
|
|