T6 OEM LED-headlight retrofit

Flyingspanner said:
I bought my lights from TPS with motors (they don’t come with the LED driver modules 2 req for each headlight as you know if you have read through the thread with 14x fixing screws), for around that price.
Avoid buying the driver modules from eBay UNLESS you can easily send them back as they have had issues with them (even new units failing) so you want some sort of protection to allow exchanging them if they fail.
Replace the front suspension nut and bolt which needs to be removed to fit the sensor bracket as it is torque to yield. Think it was 1st stage 110Nm, second stage 120 degree torque angle but I would need to check ELSA (workshop manual).
I made my own looms on the van, but Pauly’s one will save lots of time.
I did the sensors first and ran the two 3 core 0,5mm looms to the drivers footwell.
The 0.5mm 6 core loom from MX1 left headlight was run down the side of the battery using the existing body clips and into the cabin from a small grommet accessed by easing the carpet and sound deadening out the way. Make a SMALL round hole in the removed grommet (rather than slicing with a blade) and pass the core through, this keeps the grommet tight to the core without splitting.
Use a rod from the cabin to the engine bay (I have a super rod kit, but an open coat hanger would do) tape the 6 core to the rod and ease into the cabin then pass the core to the drivers side footwell keeping it above the pedal box housing (follow large loom right at the top and down behind J519 bracket so it does not get caught in the pedal mechanisms.
MX2 right headlight loom and the front sensor loom follows the original loom around the air filter housing and in through the large rubber gland which needs to be pulled forward to allow cutting two nipples to run the 6 core through one and 3 core sensor loom through the other. Make the cut at 90 degrees to avoid splitting and allowing smells and noise into the cabin. Take time to refit the block correctly into the bulkhead, be patient it will go in. Once you have done a few it is much easier, the first time will be a PITA and you will get frustrated. Use brake cleaner to make it slippy (but dries tight) to ease the process. Same when running cores through grommets.
If you use Pauly’s loom I’m not sure what route he suggests, but I made up mine to look original for the rear and ran the 3 core into the right rear quarter and used an inspection camera to find it as the van I did last weekend was fitted with a conversion with insulation so difficult to get to it in comparison to a panel van. Then ran it up to the factory loom in the roof and along to the drivers A pillar and down to meet the other cores.
You should also remove the range rheostat and fit just the dash one to keep it original.
Look at the images to help picture some of the above.

View attachment 120316

View attachment 120317

View attachment 120318

View attachment 120319

View attachment 120320

View attachment 120321

View attachment 120322

View attachment 120323

View attachment 120324

View attachment 120325



View attachment 120327

View attachment 120328

View attachment 120329

View attachment 120330

View attachment 120331
Click to expand...

Cracking addition there @Flyingspanner ! :thumbsup:

Out of interest, where do you buy your boots/bend restrictors for the level senors. I could use a few of those!

053CEB28-6215-45CA-AC42-B73136B29877.jpg
 
I get them from TPS they are listed in the electrical part of ETKA.
I also use butyl cord to seal the rubber to the cable to prevent water ingress. You can just see it at the top.

27A2A46A-9D81-441A-8321-50EC2DE2DE28.jpeg

237A8AD9-E6BE-44A8-A0F1-2C14C19E0DEF.jpeg

Some more photos of the clips:

6149F5A9-DAAD-4949-9B69-ABB9BE6CC43A.png

26F7C756-85FB-48E3-B40A-685A412C1EB9.png

4C639685-E99B-43E2-98B0-2D27E7018289.png

D9EB43F9-AE04-44EA-B2D6-0E26D7506111.png

7E1EB904-340C-4658-8CAA-EE5AC9BDA0DD.jpeg

5672D2F0-F002-4794-A80D-617682FEEF44.jpeg

I see they have changed the part number for the brown original T6 rear sensor plug which is the same black one used on the front sensor now for whatever reason.
 
Hi all,
I'm in the process of collating all the parts necessary for the retrofit – however, my local parts centre has come back to me on some of the components that seem to have multiple variations...

The parts in question are 'Power module for high/low beam' (7PP941571AE) and the 'Headlight range control' (6R0907357C).
They're basically saying that the power module has 6 different part numbers and the range control apparently has 13!

When they say 'different part numbers', they are obviously talking about the 'Zxx' suffix at the end of the main part number (see attached image).
So, with this in mind, does anybody know which 'version' I should be looking for? Or, does it even matter?

@Robert , @Pauly, @Flyingspanner are you guys familiar with these variants/different 'Zxx' suffixes?

Any help is much appreciated!

Thanks

Screen Shot 2021-07-20 at 12.55.08.png
 
ched said:
Hi all,
I'm in the process of collating all the parts necessary for the retrofit – however, my local parts centre has come back to me on some of the components that seem to have multiple variations...

The parts in question are 'Power module for high/low beam' (7PP941571AE) and the 'Headlight range control' (6R0907357C).
They're basically saying that the power module has 6 different part numbers and the range control apparently has 13!

When they say 'different part numbers', they are obviously talking about the 'Zxx' suffix at the end of the main part number (see attached image).
So, with this in mind, does anybody know which 'version' I should be looking for? Or, does it even matter?

@Robert , @Pauly, @Flyingspanner are you guys familiar with these variants/different 'Zxx' suffixes?

Any help is much appreciated!

Thanks
Click to expand...
Looks like hes doing a part number search with the digits im guessing you supplied him ?
If you search by model transporters from 2016-2019 come back as 7PP941571 AC Z06
 
Pauly said:
Looks like hes doing a part number search with the digits im guessing you supplied him ?
If you search by model transporters from 2016-2019 come back as 7PP941571 AC Z06
Click to expand...

Thanks Pauly – yes, I sent the number Robert listed earlier in this thread 7PP941571 AE so not sure what the difference (if any) 7PP941571 AC has?
 
Need a little help with The coding of the range control module.
It’s a secondhand one and i’m putting in the code given by Robert but I’m being given error codes on selecting’yes’ or ‘no’.
Any ideas?

image.jpg

image.jpg

image.jpg
 
  • Wow
Reactions: mmi
Is this a dead unit or do I need the workshop codes etc?

Fault codes from RCM

Address 55: Headlight Range Labels: 6R0-907-357.clb
Control Module Part Number: 6R0 907 357 C HW: 6R0 907 357 B
Component and/or Version: AFS-ECU 005 0050
Software Coding: 0000000000000000
Work Shop Code: WSC 00000 000 00000
ASAM Dataset: EV_HeadlRegulVWLWRCC 002006 (VN75)
ROD: EV_HeadlRegulVWLWRCC.rod
VCID: 3A7B87EFBD5F905BCD-806E
3 Faults Found:

5275220 - Headlight
C107E 54 [137] - Missing Calibration / Basic Setting
MIL ON - Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 1
Fault Frequency: 1
Reset counter: 149
Mileage: 57204 km
Date: 2048.14.16
Time: 18:14:20

13636352 - Control module not coded
U1013 00 [137] - -
[New feature! Extended UDS fault detail is only supported by current gen. interfaces]
MIL ON - Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 1
Fault Frequency: 1
Reset counter: 149
Mileage: 57204 km
Date: 2048.14.16
Time: 18:14:20

10490624 - No End-of-Line Programming
B2013 00 [137] - -
[New feature! Extended UDS fault detail is only supported by current gen. interfaces]
MIL ON - Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 1
Fault Frequency: 1
Reset counter: 149
Mileage: 57204 km
Date: 2048.14.16
Time: 18:14:20
 
Last edited:
mmi said:
Hmmm... why then the coding is zeroed. Any history?
Could you please post Advanced ID data from the controller?
View attachment 126432
Click to expand...
Code: 
Friday,06,August,2021,19:46:24:00009
VCDS Version: Release 21.3.0 (x64)
                Address 55: Headlight Range
Control Module Part Number: 6R0 907 357 C
  Component and/or Version: AFS-ECU       005 0050
           Software Coding: 0000000000000000
            Work Shop Code: WSC 00000
                      VCID: 3A7B87EFBD5F905BCD-806E

Advanced Identification/FAZIT
     Serial number: --------------
     Identification: AGD-071
     Revision: --------
     Date: 22.12.14
     Manufacturer number: 0006
     Test stand number: 5285
Flash Status
     Programming Attempts(application): 0/0
     Successful Attempts(application): 0/0
     Programming Attempts(data): 0
     Successful Attempts(data): 0
     Programming Status: 00000000
     Flash Date: 00.00.00
     Flash Tool Code(data): 00000 000 00000
Misc.
     Hardware number: 6R0 907 357 B
     Workshop System Name: J431
     Equipment/PR Code: FFFFFFFFFFFFFFFF2D2D2D2D
     Dataset Number: -----------
     Dataset Version: ----
     End of Line Equipment Level: ------------------
     ASAM Dataset: EV_HeadlRegulVWLWRCC
     ASAM Dataset Revision: 002006
Car Info
     Chassis Number: -----------------
     Engine code: ----
VCDS Info:
       VCID: 3A7B87EFBD5F905BCD-806E
       Labels: 6R0-907-357.clb
       ROD: EV_HeadlRegulVWLWRCC.rod
 
  • Like
Reactions: mmi
If it is second hand then it would already have coding in it and not read 0000000
Do the headlights dive and return to level when you start the van ?
Basic settings will require the security access code
 
  • Like
Reactions: mmi
LambethBoy said:
Dataset Number: -----------
Dataset Version: ----
Click to expand...

I believe the culprit is the above - the unit is missing so called parameterization file (dataset). That's the root cause for unit showing "not coded" etc. also preventing you to code it.
Probably the unit has been either reflashed (half-way) or is "blank". See below the same from mine:

Dataset Number: V03600097E0
Dataset Version: 0001

Code: 
                Address 55: Headlight Range
Control Module Part Number: 6R0 907 357 C
  Component and/or Version: AFS-ECU       005 0050
           Software Coding: 0FCA020001000000
            Work Shop Code: WSC 02748
                      VCID: 3A2E38592CD6E7379DB-806E

Advanced Identification/FAZIT
     Serial number: --------------
     Identification: AGD-071
     Revision: --------
     Date: 15.02.18
     Manufacturer number: 0004
     Test stand number: 0672
Flash Status
     Programming Attempts(application): 0/0
     Successful Attempts(application): 0/0
     Programming Attempts(data): 3
     Successful Attempts(data): 3
     Programming Status: 00000000
     Flash Date: 00.00.00
     Flash Tool Code(data): 50316 790 02748
Misc.
     Hardware number: 6R0 907 357 B
     Workshop System Name: J431
     Equipment/PR Code: 0000000000019980
     Dataset Number: V03600097E0
     Dataset Version: 0001
     End of Line Equipment Level: ------------------
     ASAM Dataset: EV_HeadlRegulVWLWRCC
     ASAM Dataset Revision: 002006
Car Info
     Chassis Number: -----------------
     Engine code: ----
VCDS Info:
       VCID: 3A2E38592CD6E7379DB-806E
       Labels: 6R0-907-357.clb
       ROD: EV_HeadlRegulVWLWRCC.rod
Unfortunately VCDS is not capable of loading the parameterization file into the unit. VCP or ODIS is needed + the correct parameterization file.

55 - Headlight range - 10490624 - No End-of-Line Programming problem

I ended up flashing my 55 - headlight range module with an updated software downloaded from ErWin. Flash went just fine but after the flash there's an error in the module. Autoscan BEFORE the module was flashed : Wednesday,31,May,2017,19:56:23:18632 VCDS -- Windows Based VAG/VAS Emulator...
forums.ross-tech.com forums.ross-tech.com
 
Pauly said:
If it is second hand then it would already have coding in it and not read 0000000
Do the headlights dive and return to level when you start the van ?
Basic settings will require the security access code
Click to expand...
Headlights come on with ignition do not move and turn off when started.
I have security access code from @Robert earlier post On page 16, that worked.
Pauly said:
If it is second hand then it would already have coding in it and not read 0000000
Do the headlights dive and return to level when you start the van ?
Basic settings will require the security access code
Click to expand...

mmi said:
I believe the culprit is the above - the unit is missing so called parameterization file (dataset). That's the root cause for unit showing "not coded" etc. also preventing you to code it.
Probably the unit has been either reflashed (half-way) or is "blank". See below the same from mine:

Dataset Number: V03600097E0
Dataset Version: 0001

Code: 
                Address 55: Headlight Range
Control Module Part Number: 6R0 907 357 C
  Component and/or Version: AFS-ECU       005 0050
           Software Coding: 0FCA020001000000
            Work Shop Code: WSC 02748
                      VCID: 3A2E38592CD6E7379DB-806E

Advanced Identification/FAZIT
     Serial number: --------------
     Identification: AGD-071
     Revision: --------
     Date: 15.02.18
     Manufacturer number: 0004
     Test stand number: 0672
Flash Status
     Programming Attempts(application): 0/0
     Successful Attempts(application): 0/0
     Programming Attempts(data): 3
     Successful Attempts(data): 3
     Programming Status: 00000000
     Flash Date: 00.00.00
     Flash Tool Code(data): 50316 790 02748
Misc.
     Hardware number: 6R0 907 357 B
     Workshop System Name: J431
     Equipment/PR Code: 0000000000019980
     Dataset Number: V03600097E0
     Dataset Version: 0001
     End of Line Equipment Level: ------------------
     ASAM Dataset: EV_HeadlRegulVWLWRCC
     ASAM Dataset Revision: 002006
Car Info
     Chassis Number: -----------------
     Engine code: ----
VCDS Info:
       VCID: 3A2E38592CD6E7379DB-806E
       Labels: 6R0-907-357.clb
       ROD: EV_HeadlRegulVWLWRCC.rod
Unfortunately VCDS is not capable of loading the parameterization file into the unit. VCP or ODIS is needed + the correct parameterization file.

55 - Headlight range - 10490624 - No End-of-Line Programming problem

I ended up flashing my 55 - headlight range module with an updated software downloaded from ErWin. Flash went just fine but after the flash there's an error in the module. Autoscan BEFORE the module was flashed : Wednesday,31,May,2017,19:56:23:18632 VCDS -- Windows Based VAG/VAS Emulator...
forums.ross-tech.com forums.ross-tech.com
Click to expand...
So I’m looking at a new module then?
 
LambethBoy said:
So I’m looking at a new module then?
Click to expand...
That's certainly an option. VW dealer should have tools to rectify this, however not all of them necessarily have the expertise.
@Pauly - I found in my notes that VCP probably has a proper dataset file "t6_lwr_6R0907357c.zdc" ;)
 
You must log in or register to reply here.

Similar threads

T
  • Locked
Sold T6 OEM LED Headlights (2015-2018)
Replies
5
Views
2K
theorangebaron
T
Back
Top