MK7.5 OEM LED Headlights Retrofit

[vw019283]

Hello everybody i am working in this retrofit on my golf 7 gte and i am installing the 8IU lights but i am currently running into some problems with the coding of the lights and the 4B module. I have tried flashing al the modules but since there are so many different flash version i don't know which ones work together and which ones i need? hopefully one of you can help me with this. Also i don't know the difference between flashing the modules and uploading datasets to them, do you need to do both or is it the same thing? I do have acces to the vcp flash files and to the odis datasets. I will include the fault codes i am getting down below and pictures of everything. So far i don't have the DRL's working and also have no blinker lights and the high beam only works if the knob is on auto mode. I only want the lights to work normal and don't care about the adaptive function since i have no camera in the windscreen. I followed the guide but i couldn't find some adaptation settings in my 09 like the:
Leuchtweitenregulierung:
sensor_headlight_range_control_installed:
rear
sLWR_verbaut:
not installed
1_Sensor_LWR:
1-Sensor_LWR
Fahrwerk_Variante:
Variante_1
sLWR_bei_Abblendlicht:
active
Quelle_Hoehenwerte:
BCM

Aussenlicht_uebergreifend:
Light_Control_Module:
installed
LCM_blinker:
FALSE

Can anybody tell me where to find them?

Here are the faults codes i am getting on each module:
29 + 39: C119F00 / U112100
D6 + D7: B200500 / NO_DATA (maybe i need to upload the odis datasets?)
4B: U112100 / U112300 / B201200 / U12EB00 (additional installations) / Basic setting
09: B149C01 B149B01 (left + right led headlamp power outage) / U101400 Control module coded incorrecty
AFS: warning light on the dash
And the check left and right headlight warning light on dash

To sum it up can anybody tell me whats to do? If i need to know what the flash and which files to use, and to know if thats enough or if i also have to upload a dataset or something? And then i need to know where to find the 09 adaptations? If anyone could help me out i would be very thankful and sorry if my english is bad

(BTW I did get the DRL's to work after i flashed the modules the first time but then i turned the car on and off and it was back to how it was)

 

[2018gti]

@vw019283 I have to first say I haven’t done this retrofit, though I’m very interested in helping you because I have the DLA/matrix beam lights as well and just need to find time to install them

someone who knows can correct me on this but I think only the 4B module has parameters loaded separately. the 29, 39, D6, D7 modules are one file (each) that has both the software/flash and the parameters in one. I’ve never used VCP but I’m assuming the parameterizing and flashing are separate areas in the program.

I would try loading the parameters “golfE_fcm_3q0907338.zdc” to your 4B module, then flash the first 4 “.flash” files in your second picture to D6, D7, 29, 39 in order. (if you haven’t already tried this combination) if that doesn’t work then you could try flashing the “_LED_MXB_eGolf_” flash files to see if that helps. then clear all the codes from all the modules.

unless “eGolf” really means only the e-Golf and not the GTE, I’m not sure.

you can also try going to Live Data or whatever it’s called in VCP and you can check what the high beam variant is.

 

[DV52]

@vw019283 and @2018gti : Hi to you both!!

First about "flash files" and "Datasets" and "parameters". My understanding is that these are ALL names used by different folk for the same thing.

The basic concept for these modules is like this: At the highest level of discussion - we are talking about vehicles that have a MQB platform build. So, the VAG group (being the parent company for the monolithic conglomerate that sells these cars) uses this platform across a wide range of car brands like Audi, VW, Seat etc. This means that the same module is often suitable for many car brands notwithstanding that to operate correctly on a particular model, the module software needs to be tailored to the brand, model and build year.

The way that VAG minimizes costs across the various brands/models is with "Dataset/Parameter-files/Flash-files"- meaning that the module will often have the same Part Number and Software Number (think about the module software as being the fundamental module firmware) across different brands/models/build-years - but the Dataset will be different to meet the requirements of a particular make/model/build-year - hope this makes sense.

Of course, my description above is a very general summary and some times the final digits in the Part Number and Software number are also important considerations as to the suitability of a retrofitted module

OK - @vw019283: With no offense intended, not ALL mk7 GTE's were built the same over the many years of production. Importantly for this project, a major change happened to mk7s in about the middle of 2016 - the 09 module was radically re-programmed and the entire module database was changed. One of these important changes resulted in the deletion of the long-code string that existed in the earlier version 09 module. In later model 09 modules, ALL of the long-code software switches (i.e. the Bits in the numerous Bytes) were transferred to the database for the adaptation channels. A consequence of the deletion of long-code from these later modules is that most diagnostic devices either report a zero-string, or no long-code entry at all.

I'm not sure - but my strong suspicion is that the 09 module instructions that you posted refer to the newer module without an active long-code string. Does a SCAN of the existing 09 module in this car report an active long-code? If so, this is likely the reason for your 09 module difficulties and it's also the likely reason for some of the consequential error messages in the other modules (because the AFS settings in the 09 module are not correct)

Again, my words above are predicated on my limited understanding of information provided about these two similar, but very different projects - so I could be wrong!

Don

 

[vw019283]

Thanks for the information guys
@2018gti Ok thank you for the help i will try that order in a moment!

@DV52 So if i understand correctly i need to find the “same” settings but not in the adaptation channels but in the long coding bites?

Or could i go a hole other route and “flash/update” my bcm so it has the newer version? (I think this would need a whole new fl bcm)

 

[2018gti]

I'll just put this here in case it helps.. has a lot of details about the whole process: https://www.drive2.ru/l/626710084033987147/

 

[DV52]

@DV52 So if i understand correctly i need to find the “same” settings but not in the adaptation channels but in the long coding bites?

Or could i go a hole other route and “flash/update” my bcm so it has the newer version? (I think this would need a whole new fl bcm)

NO, I wasn't suggesting anything like a wholesale change to the BCM software. And in any event - it's NOT possible to "flash/update" an older style BCM to the newer type because the hardware on the BCM mother board is different across the 2 x modules!

Maybe answer the question that I asked in my first reply ( which I put in bold type for emphasis). If this car has an older style BCM, post-up a copy of the long-code string- please. We can talk about the way forward after this information is disclosed!

Don

 

[vw019283]

@DV52 Yes thats what i was thinking i will include a picture on this post with the long code string. Hope this helps!

@2018gti That russian guide helped a bit, the only thing is that he uses the 4B 3Q0907338E file on vcp but i can only find the 4B 3Q0907338C file I don’t know if this is different but i mailed vcp about this to see if they still have the file. As you can see in the pictures the normal 3Q0907338 flash files and the 3Q0907338C flash files also have a lot of option to chose from themselves so i don’t know which one he used? Also he has a gti and i have a gte, there are normal files and electric hybrid files so idk if i can get away with just using the normal files? I tried you suggested flash combination but it didn’t change anything. Still waiting on more info….

 

[2018gti]

@vw019283 dang, sorry to hear it isn't working (yet). must just not be the right combination of parameters/flashes. are you still getting "Data record invalid " on the D6 or D7 modules? I wonder if there's a difference between the A and AG (7P5941572).

in the Russian post I think they're using ODIS to flash everything so it's just a plain XML file that gets sent, not a .zdc file with all those options. if I read the post correctly I think 4B was updated to "E" version after everything was finished.

what options do you get when you open "golfE_fcm_3Q0908338.zdc" in VCP? hopefully the VCP people know more since they have all that stuff gathered.

 

[DV52]

@vw019283: The non-zero Bytes in the BCM long-code string are like this

Byte Hex    Binary
00    00    00000000
01    11    00010001
02    1C    00011100
03    42    01000010
04    C3    11000011
05    51    01010001
06    62    01100010
07    F3    11110011
08    6B    01101011
09    EC    11101100
10    50    01010000
11    80    10000000
12    B1    10110001
13    04    00000100
14    03    00000011
15    28    00101000
16    18    00011000

The software switches that tell the BCM what version headlights to manage are in Byte 02, Bit 0-2. As you can see from my list - as currently coded, the value of the headlight-Bits are Binary 100 (remember that Binary numbers are read from right-to-left - so the right-most digit is Bit 0), or hex04.

There are no details of the "8IU" headlights - so I have no idea what the appropriate combination of Bits should be - but I suggest that you try either hex05 (101), or hex06 (110). Clear the BCM errors after each try ! Hopefully one of my suggested changes will remove the BCM "incorrectly coded" error (and some of the errors in the other modules)

Don

 

[vw019283]

@2018gti Umhh i was getting a no OPX error if i remember correctly but i have no idea what this means maybe you guys know?
I read the hole article, the russian guy himself used vcp files and he used the one i couldnt find. But he included the odis files for other users to use (idk why).
The egolf files only has one option and its just called AFS, idk if this is the one i need because i don’t know if i need the afs files or the mxb files like the russian? (idk what mxb stands for if anyone can explain would help)

@DV52 Sorry if this sound really dumb or anything its my first time doing something like this.

So its currently this:
Byte Hex Binary
00 00 00000000
01 11 00010001
02 1C 00011100
03 42 01000010
04 C3 11000011
05 51 01010001

And it needs to go to this:?

Byte Hex Binary
00 00 00000000
01 11 00010001
02 05/06 00011100
03 42 01000010
04 C3 11000011
05 51 01010001

And the binnary changes automatic with the hex change or what does that need to be?
00011101/00011110 for 05 or 06? I have no idea haha.

Do you also know which byte will enable the 4b module to control the lights? And will enable the bcm to read the rear left lvl sensor directly? Or will this both be enabled by changing the above?

 

[DV52]

hmm......... not really!! I'm not sure how familiar you are with hexadecimal arithmetic. If not familiar, maybe forget the VCDS long-code Helper facility and instead, make the changes directly in the VCDS Recode module screen

These are the long-code strings:

Scenario	Long Code Value (hexadecimal)
Existing (Byte 02, Bit 0-2= hex04)	00111C42C35162F36BEC5080B10403281800000000000000000000000000
1st Try (Byte 02, Bit 0-2 = hex05)	00111D42C35162F36BEC5080B10403281800000000000000000000000000
2nd try (Byte 02, Bit 0-2. =hex06)	00111E42C35162F36BEC5080B10403281800000000000000000000000000

So, do this (of course, the values on your car will be different to those shown on the screens below):

1. On the Open Controller Screen for the BCM, select Coding -07
   
   
2. On the Recode Module screen below:
   
   
3. Copy the ENTIRE long-code string from the Current coding box to the PC clipboard
4. Paste the PC clipboard into the New coding box
5. 1st. Try: In the New coding box - change the sixth digit from the left from C to D and click on Do It!
6. Follow the prompts to implement the changed long-code string
7. Clear ALL errors and SCAN the car - does the U101400 Control module coded incorrectly error re-appear on the BCM?
8. If so, repeat steps 3 and step 4 above
9. 2nd. Try: In the New coding box - change the sixth digit from the left from D to E and click on Do It!
10. Follow the prompts to implement the changed long-code string
11. Clear ALL errors and SCAN the car - does the U101400 Control module coded incorrectly error re-appear?

Don

 

[vw019283]

@DV52 Does only VCDS make these changes directly or can i also use vcp to change the long code and will it work the as well?

(edit)
And doesn’t every setting of the 09 have to be perfect for the error to go away? Like the leuchte settings and afs?

 

[DV52]

Does only VCDS make these changes directly or can i also use vcp to change the long code and will it work the as well?

No - VCDS is NOT the only diagnostic device that will change the value of the long-code string on these modules.

The facility to change long-code values is in the module, itself - it's NOT a particular function that is restricted in most diagnostic devices.

So YES, other good diagnostic devices, like OBDeleven and VCP can make these same changes and they will work equally as well.

Of course, the detailed instructions for VCDS in my previous response will NOT apply to other diagnostic devices - which will have their-own unique way of implementing these changes.

Nevrtheless, the long-code values in the table for my 3 x scenarios (in my previous reply) will be the same regardless of which device you use!

And doesn’t every setting of the 09 have to be perfect for the error to go away? Like the leuchte settings and afs?

hmm......... Yes of course you are correct!! But I'm reminded of a saying that I understand has its origins in Africa: "the best way to eat an elephant is one bite at a time!!

This car clearly has multiple problems (not surprising because retrofitting these headlights into a mk7/mk7.5 ain't a simple execise!). If your objective is to fix ALL the errors on this car as ONE task - then I respectfully suggest that you might start by first solving world poverty !! No offense intended - I'm joking, of course!!

The ONLY workable approach for moving forward with this car is to take "one bite at a time" - meaning that diagnostics needs to be piecemeal and the fix needs to be incremental.

However, obviously this is my opinion and as the owner of the car- you are entitled to apply any other meathod that you so choose!!

 

[vw019283]

@DV52 Yes ofcourse i know that, but i was just wondering how will i know which one works and if i got the right one if the error stays?

 

[DV52]

@DV52 Yes ofcourse i know that, but i was just wondering how will i know which one works and if i got the right one if the error stays?

hmm...... not sure that I understand "which one" you mean in your response?

Are you referring to "which one" of my 2 x suggested long-code changes in my previous response?
Or are you referring to "which one " - meaning which of the many fixes that could possibly apply to clear this car of ALL errors?

Don