You can take it from old illumination/manual range control plug.
Black/violet wire ( Pin 4) is the same supply as factory OEM LED setup and obviously GND could be connected to any earthing point or ( Pin 1) of the same plug.
T6 OEM LED-headlight retrofit
Black/violet wire ( Pin 4) is the same supply as factory OEM LED setup and obviously GND could be connected to any earthing point or ( Pin 1) of the same plug.
Show us the photo of your purchased item.
What is its part number?
6Q0941334 is the correct part number.
See more below
What is its part number?
6Q0941334 is the correct part number.
See more below
So i need to change this part right? For the 6Q0941334 which controls the dash luminosity.
Just so im clear - on the wiring side of things how would i then wire this up? im assuming the plugs will be different? or not? And then for the RCM?
sorry for the numerous questions..
Reading description it is wrong item.
Yes you need to change your manual lights range adjuster only to illumination adjuster only.
Plug is the same as well as the wiring.
Got mine from TPS
Yes i got mine from TPS also.
Here are the two part numbers new one on the top, old dual H4 at the bottom
To clarify what Andy and I did to cure the issue we had (LED lights worked, but not as expected, pulling back on the stalk to flash Main beam would light both dipped and high beam lights on both sides, so we knew they would/should work but neither lamp would light if dipped or high beam were selected)
Andy's Byte 16 was originally 8F (10001111) but as you can see in the screenshot above, bits 0-3 are not an option to change via the tick boxes, so I did a cut & paste and changed Byte 16 to D0 to match Montecha's coding. This cured the problem. I can't remember if we tried DF but I think we did, thus disabling low and high beam lamp monitoring.
I don't know what the change from F to 0 means but it had the desired effect. If anyone else has the same issue I suggest trying this change.
For comparison, My own van (2017 T28 150 with H4 headlights), also has an F in the first part of Byte 16.
Found the meanings for all the bits in Byte 16
0.
I assume bits 0-3 need to be active (unticked or binary 0) for LED lights to work. However if standard filament bulbs are fitted in the rear foglights would bit 1 still need to be a 1? Is bit 1 referring to rear foglights like bit 5 is?
( @Andy_dea or @Montecha , do you have LED rear fog lights? are they working correctly?)
0.
Byte 16 Bit 0 Activation low beam via pulse width modulation (PWM) active (Ansteuerung Abblendlicht über Pulsweitenmodulation (PWM) aktiv)
- Byte 16 Bit 1 Activation of fog light via pulse width modulation (PWM) active (Ansteuerung Nebelschlusslicht über Pulsweitenmodulation (PWM) aktiv)
- Byte 16 Bit 2 Activation of Daytime running lights via pulse width modulation (PWM) active (Ansteuerung Tagfahrlicht über Pulsweitenmodulation (PWM) aktiv)
- Byte 16 Bit 3 Activation of High Beam via pulse width modulation (PWM) active (Ansteuerung Fernlicht über Pulsweitenmodulation (PWM) aktiv)
- Byte 16 Bit 4 Lamp Diagnostics for Low Beam active
- Byte 16 Bit 5 Lamp Diagnostics for Rear Fog Light(s) active
- Byte 16 Bit 6 Lamp Diagnostics for (Separate) Daytime Running Lights (DRL) active
- Byte 16 Bit 7 Lamp Diagnostics for High Beam active
I assume bits 0-3 need to be active (unticked or binary 0) for LED lights to work. However if standard filament bulbs are fitted in the rear foglights would bit 1 still need to be a 1? Is bit 1 referring to rear foglights like bit 5 is?
( @Andy_dea or @Montecha , do you have LED rear fog lights? are they working correctly?)
I retrofitted the rear LEDs light clusters, but I think that the fogs (and reversing bulbs) are still halogen?
I have the T6 Led rears - what I call the 'E3' lights and I didn't change any coding for the rear lights.