T6 OEM LED-headlight retrofit
Ah sorry - my bad… I can see where you said ‘parametrization’ in your original reply now…
It was the genuine ‘rogue’ post yesterday that made me think it was another one!
I’m impressed too - it’s a fine word, although I agree with Gavinda, it should probably be an ‘s’ on these shores.
What a terrible time to be a ‘z’ eh?
It’s a 2019 unit, looks like it has never been coded as no workshop code listed for it either, prob just needs to go online to factory to release it.
Where are you based?
That is prob why sensors and motors are showing open circuit as it is not set up to accept inputs.
Have you tried setting up a workshop code on your VCDS? Could it just be that preventing it being coded?
Where are you based?
That is prob why sensors and motors are showing open circuit as it is not set up to accept inputs.
Have you tried setting up a workshop code on your VCDS? Could it just be that preventing it being coded?
Thanks for your input @Flyingspanner.
Re workshop code: Yes, coincidentally this is something I read about last night on the Rosstech forums, where other users were having trouble coding ‘virgin’ modules.
One response on the forum recommended adding a valid workshop code as you have suggested - so this is something I will try next (when I finish work today).
In terms of which workshop code to add - Rosstech forum users suggested opening another control module in VCDS and copying/mirroring the workshop code from there.
By all accounts, the workshop codes don’t behave like a normal security password, they are more a ‘digital marker’ to record who has worked on/made changes to modules during repairs, servicing etc.
In theory, the given module will accept coding changes, once any valid workshop is added, it just won’t work if you try and proceed with the VCDS 123, 12345, 123456 default code the dialog box recommends in the app.
I will report back this evening, when I get chance to try this.
Thanks
Last edited:
Can’t give you my info, but the importer info for the uk ( the middle box) is 210
Great - I’ll try 210 in the middle box. Rosstech forum users all suggested 444 which is the code for North America.
Do you think it’s better to add the workshop code in settings/options for the whole VCDS app or when prompted when viewing the 55 Range Control module?
Apparently, If the workshop code is added in the general settings, It will be this code that is shown/recorded for ALL module changes going forward, and will no longer display ‘000000’ which Rosstech refer to as ‘stealth mode’.
Set VCDS up as you want to use it for all jobs, that way you won’t have to worry about these irritating holdups along the way.
Hope you get it sorted.
Hope you get it sorted.
**Update**
So - apologies for the mammoth post that's about to ensue, but my issues appear deeper than first thought...
Worryingly, this evening I discovered that my headlights turn off when I start the engine!? I've only discovered this now, as most of my testing/coding etc. has been done with the ignition on, with a charger hooked up to maintain the battery.
Everything is working fine, high/dipped beam, indicators, DRLs, but shortly after starting the engine, everything except the DRLs turn off? The headlight control dial also becomes unresponsive, with no effect in any position?
This is baffling because the lights appear to work perfectly when the key is in the ignition on position - but die as soon as I start the engine.
VCDS autoscan throws up some errors for hi and low beam (short or open circuit), but again, if there was a short/wiring issue, why would they work fine with ignition on?
The other issues I cant seem to shift are a bulb out indicator on the dash, and an alert stating 'no cornering light (AFS) function' - again, these are strange because I can't find a bulb out and my front fogs work too?
@KT6B - I notice you mention an AFS cornering light issue earlier in this thread.... did you ever manage sort this?
I've attached my VCDS scan results if anybody has any pointers? Is it worth trying a BCM reset for instance?
Any help on this would be much appreciated... Thanks!
So - apologies for the mammoth post that's about to ensue, but my issues appear deeper than first thought...
Worryingly, this evening I discovered that my headlights turn off when I start the engine!? I've only discovered this now, as most of my testing/coding etc. has been done with the ignition on, with a charger hooked up to maintain the battery.
Everything is working fine, high/dipped beam, indicators, DRLs, but shortly after starting the engine, everything except the DRLs turn off? The headlight control dial also becomes unresponsive, with no effect in any position?
This is baffling because the lights appear to work perfectly when the key is in the ignition on position - but die as soon as I start the engine.
VCDS autoscan throws up some errors for hi and low beam (short or open circuit), but again, if there was a short/wiring issue, why would they work fine with ignition on?
The other issues I cant seem to shift are a bulb out indicator on the dash, and an alert stating 'no cornering light (AFS) function' - again, these are strange because I can't find a bulb out and my front fogs work too?
@KT6B - I notice you mention an AFS cornering light issue earlier in this thread.... did you ever manage sort this?
I've attached my VCDS scan results if anybody has any pointers? Is it worth trying a BCM reset for instance?
Any help on this would be much appreciated... Thanks!
Last edited:
No problem mate - whenever you get chance to view the log, please report back if you see any glaring errors.
I forgot to add, that I’ve still got halogen rear lights, so not sure if I need to tweak the coding to suit.
I think @mmi posted something earlier in the thread about front LEDs/halogen rear coding tweaks so will study that too.
I had the same issue with the module which threw up some of those errors codes, this is the part no for a new module from Vw that will fix the module related errors.
Once that is replaced you’ll be able to see which errors are left to sort in the wiring assuming all the other parts are in working order.
Thanks @KT6B. I’ve got a brand new RCM on the way to my local parts centre as we speak.
I had no idea how much this part would effect the rest of the set-up in terms of faults - I just presumed the lights wouldn’t level correctly if it was not coded/installed.
Reassuring to know it cleared a lot of your issues when you eventually got your new RCM installed.
Cheers
Do they not adjust levels whilst in transit too? For example - if the vehicle is travelling up-hill, would they not lower slightly as to not dazzle oncoming traffic?
Ok understood. My lights switching off with engine on is obviously my biggest issue, so was hoping the uncoded RCM was influencing that fault, but given what you have said, it’s probably the fact my coding is out somewhere…
I’m off to pick up my replacement RCM this afternoon, so I guess I’ll have a better idea what’s going on when it’s fitted - or at least eliminate the faults associated with it.
Thanks
I'm pleased to report that my lights appear to be working... I've fitted and successfully coded the new range control module (although now £209 lighter in my wallet!).
The lights now seem to work with the engine running.
I tweaked my 09 Central Electrics (BCM) coding to include the recommended settings that @mmi posted early on in this thread re: van with LED headlights with halogen rears. I also used 'D0' in Byte 16 as recommended by a few posts in the thread too.
This is now my coding:
In terms of remaining fault codes, I still have the following:
Code:
09 Central Electrics (BCM)
-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519) Labels:. 7E0-937-BCM-V1.clb
Part No SW: 7E0 937 090 D HW: 7E0 937 090 D
Component: BCM PQ25 Max4 H82 0762
Revision: B9082001 Serial number: 8601 297180548
Coding: A0AC391A0A61341193284F347CEB8E70FF84730F60CD7D40330400230840
Shop #: WSC 01369 210 40505
VCID: 2C010D942608804B432-8078
Subsystem 1 - Part No: 5K7 955 559 C Labels: 5K7-955-559.CLB
Component: RLS 171018 05 50 0106
Coding: 0228EE
Subsystem 2 - Part No SW: 7E0 959 801 P HW: 7E0 959 801 P Labels: 7E0-959-80X-V2.CLB
Component: J386__TSG_FT 004 0653
Serial number: KU0KU001101882740141
Coding: 1400B0
Subsystem 3 - Part No SW: 7E0 959 802 P HW: 7E0 959 802 P
Component: J387__TSG_BT 004 0653
Serial number: KU0KU019101882921610
Coding: 0400A0
Subsystem 4 - Part No: 7E1 951 172
Component: DWA-Sensor 00 001 0104
Coding: 000000
Subsystem 5 - Part No: 1K0 951 605 F
Component: LIN BACKUP HO H01 0009
Coding: 000000
Subsystem 6 - Part No: 7E1 951 172
Component: DWA-Sensor 00 001 0104
Coding: 000000
Subsystem 7 - Part No SW: 7E0 959 442 HW: 7E0 959 442 Labels: 3C8-959-537.CLB
Component: E221__MFL-DC1 H02 0103
Serial number: 39180001895190098383
Coding: B0FFFF
4 Faults Found:
00978 - Lamp for Low Beam; Left (M29)
010 - Open or Short to Plus
Freeze Frame:
Fault Status: 01101010
Fault Priority: 3
Fault Frequency: 5
Reset counter: 168
Mileage: 26565 km
Time Indication: 0
Date: 2022.04.05
Time: 20:12:00
00979 - Lamp for Low Beam; Right (M31)
010 - Open or Short to Plus
Freeze Frame:
Fault Status: 01101010
Fault Priority: 3
Fault Frequency: 24
Reset counter: 168
Mileage: 26565 km
Time Indication: 0
Date: 2022.04.05
Time: 20:11:25
01495 - Bulb for High-Beams; Left (M30)
010 - Open or Short to Plus
Freeze Frame:
Fault Status: 01101010
Fault Priority: 3
Fault Frequency: 9
Reset counter: 167
Mileage: 26565 km
Time Indication: 0
Date: 2022.04.05
Time: 20:05:06
01499 - Bulb for High-Beams; Right (M32)
010 - Open or Short to Plus
Freeze Frame:
Fault Status: 01101010
Fault Priority: 3
Fault Frequency: 4
Reset counter: 167
Mileage: 26565 km
Time Indication: 0
Date: 2022.04.05
Time: 20:05:06
-------------------------------------------------------------------------------
19 CAN Gateway
-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533) Labels:. 7E0-909-901.clb
Part No SW: 7E0 909 901 HW: 7E0 937 090 D
Component: GW-K-CAN TP20 H82 0762
Revision: B9082001
Coding: 042305
Shop #: WSC 01369 210 40505
VCID: 6889B184F2706C6B67A-803C
1 Fault Found:
01044 - Control Module Incorrectly Coded
000 - -
Freeze Frame:
Fault Status: 01100000
Fault Priority: 2
Fault Frequency: 1
Reset counter: 255
Mileage: 26565 km
Time Indication: 0
Date: 2022.04.05
Time: 16:47:44
Is this something to do with having the correct chassis type? There is a drop down menu when viewing the module where you can select different vehicle types... there's no Transporter option, so selected the closest which stated 'City Van/Pickup' I still get the fault though.
55 Range Control Module
-------------------------------------------------------------------------------
Address 55: Headlight Range (J431) Labels:. 6R0-907-357.clb
Part No SW: 6R0 907 357 C HW: 6R0 907 357 B
Component: AFS-ECU 005 0050
Revision: -------- Serial number: --------------
Coding: 0FCE020001000000
Shop #: WSC 12345 123 12345
ASAM Dataset: EV_HeadlRegulVWLWRCC 002006
ROD: EV_HeadlRegulVWLWRCC.rod
VCID: 3A2D3BCCDCDC2EFBC1E-806E
1 Fault 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: 168
Mileage: 26565 km
Date: 2022.04.08
Time: 16:08:51I'm guessing this will clear once I've done some driving? Or, is there something else I need to do?
The only other thing I have noticed is the DRLs seem really bright when the headlight selection dial is set in the '0' but they seem to dim slightly when you turn to Auto, Side Lights, Dipped beam etc. Is this normal behaviour?
As ever, any pointers would be much appreciated - thanks!
Last edited: