VW Vortex - Volkswagen Forum banner
  • Mwerks and Fourtitude have rejoined VWVortex. For more info, see this thread.

1 - 20 of 71 Posts

·
Registered
Joined
·
113 Posts
Discussion Starter #1
Hello!

Is there any possibility to switch off the tail lights when driving on DRL's. I found the possibility to use separate lights for DRL's but tail light remains on. There is possible to visit the dealer, but after deactivating of the tail DRL's there is completely no change in Auto Scan and Adaptations.

I'm talking about Octavia II 2009 Facelift & 2007

Any ideas?

Regards
Marcin
 

·
Registered
Joined
·
1,281 Posts
Hello!

Is there any possibility to switch off the tail lights when driving on DRL's. I found the possibility to use separate lights for DRL's but tail light remains on. There is possible to visit the dealer, but after deactivating of the tail DRL's there is completely no change in Auto Scan and Adaptations.

I'm talking about Octavia II 2009 Facelift & 2007

Any ideas?

Regards
Marcin

Usually whether or not the tail lights are on with the DRLs depends on the country coding (different countries have different laws about lights). When you post your auto-scan, Dana should be able to tell you how to change your country coding so that the tail lights do not come on with the DRLS.

Good Luck

Don
 

·
Registered
Joined
·
113 Posts
Discussion Starter #4
OK. Here is it.
Let me explain the situation. This AutoScan comes from Octavia 2 Facelift 2009 Classic + A/C. This version has no power rear windows, no fog lamps, no DRL's on separate bulb etc. It's cheapest possible option. :)

This saturday I installed the front fog lights, with DRL's included. I make wiring accordingly to the Skoda's electrical diagrams and replace Central Electrical module from 1K0 937 085 to 1K0 937 087H and everything is OK.

In Poland, where I come from, the law allows to switch off the tail lights when using front DRL's
That was the initial question. I assume we can disable the tail light by founding the correct coding of the light configuration at byte 18 of long coding at 09 controller. Yesterday we make an small investigation (just trying :)) of the values of this byte. We have good results for Octavia, for the following coding:

0B - LHD
0A - RHD
0D - both tail fog lams works together.... :confused:

Question is what coding is correct to switch off the tail light in configuration 0B & 0D
Quaestion 2, is there any possibility to use a LED bulbs on DRL's (separate bulbs in front fog lamp chassis)


Saturday,14,August,2010,01:05:13:24735
VCDS Version: Release 10.6.0
Data version: 20100630



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: 1K0
Scan: 01 03 08 09 10 15 16 17 19 25 42 44 46 52 56

VIN: TMBDA21Z19C006327

01-Engine -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
04-Steering Angle -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
10-Park/Steer Assist -- Status: OK 0000
15-Airbags -- Status: OK 0000
16-Steering wheel -- Status: Malfunction 0010
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
25-Immobilizer -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
46-Central Conv. -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
56-Radio -- Status: OK 0000

-------------------------------------------------------------------------------
Address 01: Engine Labels: Redir Fail!
Part No: 06A 906 033 KB
Component: BSE S71 1.6 2VG 2228
Revision: --H04--- Serial number:
Coding: 0004071
Shop #: WSC 31414 790 00001
VCID: 69F772AF3911

No fault code found.
Readiness: 0000 0000

-------------------------------------------------------------------------------
Address 03: ABS Brakes (-----) Labels: 1K0-907-379-60EC1F.clb
Part No SW: 1K0 907 379 AD HW: 1K0 907 379 AD
Component: ESP MK60EC1 H35 0106
Revision: 00H35001
Coding: 113B201C09220000880E04E6902000402800
Shop #: WSC 31414 790 00001
VCID: 74C913DB6ED3

No fault code found.

-------------------------------------------------------------------------------
Address 08: Auto HVAC (J301) Labels: 3C8-907-336.clb
Part No SW: 3T0 820 047 H HW: 3T0 820 047 H
Component: Climatic 130 0203
Revision: 00004001
Coding: 0000000000
Shop #: WSC 31414 790 00001
ASAM Dataset: EV_Climatic A01001
ROD: EV_Climatic_SK35.rod
VCID: 3449D3DB2E53

No fault code found.

-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519) Labels: 1K0-937-08x-09.clb
Part No SW: 1K0 937 087 H HW: 1K0 937 087 H
Component: BCM PQ35 H+ 103 0573
Revision: 00103 AC
Coding: 4E180AB890250CB040100081050081E405010DAE42498960500440000000
Shop #: WSC 07021 666 43302
VCID: 364DE9D3382F

Part No: 1Z1 955 119 C
Component: Wischer 18020 22 0601
Coding: 00DFB7

No fault code found.

-------------------------------------------------------------------------------
Address 10: Park/Steer Assist (J446) Labels: 3C8-919-475.clb
Part No SW: 1Z0 919 475 HW: 1Z0 919 475
Component: PARKHILFE 4K H06 0004
Revision: -------- Serial number: 66640902711765
Coding: 000001
Shop #: WSC 31414 790 00001
VCID: FEDDB1F3D09F

No fault code found.

-------------------------------------------------------------------------------
Address 15: Airbags Labels: 1K0-909-605.lbl
Part No SW: 1K0 909 605 T HW: 1K0 909 605 T
Component: Q2 AIRBAG VW8 020 2300
Revision: 05020000 Serial number: 0038PD2B3D3
Coding: 0020786
Shop #: WSC 31414 790 00001
VCID: 3D5FF6FF1D19

No fault code found.

-------------------------------------------------------------------------------
Address 16: Steering wheel Labels: 1K0-953-549-MY9.lbl
Part No SW: 1K0 953 549 CH HW: 1K0 953 549 CH
Component: J0527 056 0111
Coding: 0000534
Shop #: WSC 12345 123 12345
VCID: 7AD53DE34CB7

Part No: 3T0 959 537
Component: E221__MFL-URO H07 0011
Coding: 00000128
Shop #: WSC 00000

1 Fault Found:
01426 - Controls in Steering Wheel (E221)
004 - No Signal/Communication - Intermittent

-------------------------------------------------------------------------------
Address 17: Instruments (J285) Labels: 5K0-920-xxx-17.clb
Part No SW: 1Z0 920 803 B HW: 1Z0 920 803 B
Component: KOMBI H20 0107
Serial number: 00000000000000
Coding: 110900
Shop #: WSC 31414 790 00001
ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04040
ROD: EV_Kombi_UDS_VDD_RM09_SK35.rod
VCID: 334BD0C72B5D

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway Labels: 1K0-907-530.lbl
Part No SW: 1K0 907 530 S HW: 1K0 907 951
Component: J533__Gateway H16 0210
Revision: H16 Serial number: 3400K091300546
Coding: E9A01F06000202001302
Shop #: WSC 20770 456 11512
VCID: 3753E4D73F25

No fault code found.

-------------------------------------------------------------------------------
Address 25: Immobilizer (J334) Labels: 5K0-920-xxx-25.clb
Part No SW: 1Z0 920 803 B HW: 1Z0 920 803 B
Component: IMMO H20 0107
Serial number: 00000000000000
ASAM Dataset: EV_Immo_UDS_VDD_RM09 A03004
ROD: EV_Immo_UDS_VDD_RM09_SK35.rod
VCID: 334BD0C72B5D

No fault code found.

-------------------------------------------------------------------------------
Address 42: Door Elect, Driver Labels: 1K0-959-701-MIN3.lbl
Part No SW: 1T0 959 701 M HW: 1T0 959 701 M
Component: Tuer-SG 008 2011
Coding: 0000052
Shop #: WSC 31414 790 00001
VCID: 41A78A0F61E1

No fault code found.

-------------------------------------------------------------------------------
Address 44: Steering Assist Labels: 1Kx-909-14x.lbl
Part No: 1K1 909 144 M
Component: EPS_ZFLS Kl.067 H08 1901
Shop #: WSC 00000 347 116111
VCID: 354FEEDF2529

No fault code found.

-------------------------------------------------------------------------------
Address 52: Door Elect, Pass. Labels: 1K0-959-702-MIN3.lbl
Part No SW: 1T0 959 702 M HW: 1T0 959 702 M
Component: Tuer-SG 008 2003
Coding: 0000052
Shop #: WSC 31414 790 00001
VCID: 42A5850364E7

No fault code found.

-------------------------------------------------------------------------------
Address 56: Radio (J503) Labels: 5M0-035-1xx-56.clb
Part No SW: 1Z0 035 161 F HW: 1Z0 035 161 F
Component: SWING 006 0039
Revision: 0H001001 Serial number: SKZ1Z2I8214206
Coding: 080002000001
Shop #: WSC 73430 790 00999
VCID: 3147DACFD141

No fault code found.

End ---------------------------------------------------------------------
 

·
Registered
Joined
·
113 Posts
Discussion Starter #5
Any ideas?

In the coming weekend we intend to check out all of the 256 possible combination coding on Octavia Facelift 2009. We have an spare Central Electric module to do it. We are looking for 2 following setups:

1. Daily Running Lights mode - tail lights shut down
2. Front, separate DRL's (assembled in the same chassis as the front fog lights, but 2 bulbs in each lamp - H1 for fog and cornering, 21W for DRL). We intend to change the classic 21W bulb into 12V LED bulb.

Does anybody know if there is possible to find out the coding of byte18 to have the cobfiguration as above, without checking out the LED DRL's damage?
 

·
Vendor
Joined
·
2,906 Posts
Hi,

Sorry I missed the scan the other day. We have another customer (Octavia II) with a similar Byte 18 issue. I don't have this sorted yet, but feedback would be really helpful. Was your coding "00" from the factory, or did it have the real coding shown?

We were experimenting in the 30's since the original coding is unknown.

32, 34, and 36 resulted in no DRL's

38 and 39 did have DRL's but I do not think he had an operational Left rear fog light. I'm sorry but I don't know if this was all lights as DRL's or only front. The car was from France if that matters.

If you get all of the lights off with 32, 34, or 36 we can try to enable the fronts in some other Bytes. Possibly Byte 11, 15 or 24. My only other note about DRL's as separate lights and the use of LED's is to make sure we configure a 12.6V coding. As per the current coding it looks like 80% in Byte 24.
 

·
Registered
Joined
·
113 Posts
Discussion Starter #7
Thanks Dana.

I have the spare 09 module for experimenting. We can try everything without a risk of damaging antything in normallu used module. Just give me some tips what is the best way to document our results. I was thinking, we will do a photo of each code at back and front, but I'm not sure if it helps.

Brgrds
Marcin
 

·
Registered
Joined
·
113 Posts
Discussion Starter #8
Hi,
. Was your coding "00" from the factory, or did it have the real coding shown?

.
Yes original quote was "00". I bbserve if we chnage the value of the byte 18 to e.g. 0D then behaviour of the lights changes, but if we come back to 00, there is no change. This mechanism works for each coding. So, some of my colleagues went to the dealers with request ti change the way of behaviour of tail DRL's and their coding has no difference before and after. I assume the dealers comes back to 00 to hide the coding.

Btw, feedback to the module 1K0 937 087

in Byte 14 Bit 1 - if You change it to 1 = DRL via fog lights.
in Byte 11 Bit 0 - if You change it to 1 = american lighting mode - light deactivation by hand brake

:)
 

·
Registered
Joined
·
7 Posts
It works like this, because they use, what I call, STORED PROCEDURES. Their VAS software has an option, for example "TURN REAR LIGHTS WHILE DRL". In this case, their sw makes:
1. Change byte 18 to appropriate value,
2. Change byte 18 to 00.

That's why, when I went to change the behaviour of rear light I noticed no change in coding.

In VCDS there is an option we can turn ON or OFF, and we can also see which byte and bit it is going to change - in dealer's service they don't see where the change is made. It's like instead of coding we have now in VCDS, there was a list of what you want to do: to turn on the cornering light I have to turn on one bit in 14'th byte, one in 17'th byte and one bit in byte 26. Of course I can decide which of them I want ON, but for this case assume it has to be like I just said.
Now, in VCDS I need to change every bit (and we know which one), but if there is only a list of the functions there will be "TURN CORNERING ON", and the software sends (changes) those bit's to 1.

The same is with bit 18. In Octavia2FL there could be at least 4 configurations:
1. Left hand drive*
2. Right hand drive*
3. "Universal" left and right drive - with both rear fog light on
4. Right hand drive with rear lights OFF while DRL
5. Rear lights with LED.
etc. etc.

The points 1 and 2 makes a difference for rear fog light (works left OR right fog light) but also for climatronic setting - while RIGHT hand drive, left temperature switch is a 'master' (while changing "left" side temperature, also right changes). While LEFT hand drive it works opposite - the right switch is a 'master'.

Those settings of byte 18 are of course individual for each car. There are few cars I can search the right settings :) So the list in byte 18 can be longer.

Hope it helps :)
 

·
Vendor
Joined
·
2,906 Posts
Thanks Dana.

I have the spare 09 module for experimenting. We can try everything without a risk of damaging antything in normallu used module. Just give me some tips what is the best way to document our results. I was thinking, we will do a photo of each code at back and front, but I'm not sure if it helps.

Brgrds
Marcin
A photo is very helpful at times. I personally have created logs on the PC and typed the description of the lighting and saved fault codes if any were stored. Cycling the key and operating all exterior lights so the faults, if any, are stored prior to saving the data is critical. It is time consuming and I bet I've done 125 (or so) Byte 18 mods. on my 2010 Gti.

At one point I had several multimeters back-probing various lighting sockets so I could monitor voltage as well.

Yes original quote was "00". I bbserve if we chnage the value of the byte 18 to e.g. 0D then behaviour of the lights changes, but if we come back to 00, there is no change. This mechanism works for each coding. So, some of my colleagues went to the dealers with request ti change the way of behaviour of tail DRL's and their coding has no difference before and after. I assume the dealers comes back to 00 to hide the coding.

Btw, feedback to the module 1K0 937 087

in Byte 14 Bit 1 - if You change it to 1 = DRL via fog lights.
in Byte 11 Bit 0 - if You change it to 1 = american lighting mode - light deactivation by hand brake

:)
Nice, I have the DRL via fog lights thing noted here: VCDS MKVI / MK6 Platform, Handy Coding tweaks And several people have reported variable results based on Byte 18 coding.

"Notes:
- Depending on the Byte 18 coding, this may result in all of the parking lights illuminating."

In my case, I coded the Gti to a Seat Altea and duplicated this. I had a ton of faults, but all of the lights were on as DRL's

http://forums.vwvortex.com/showthre...ing-tweaks&p=65746832&viewfull=1#post65746832

http://forums.vwvortex.com/showthre...ing-tweaks&p=65776401&viewfull=1#post65776401

Just keep that in mind, so your Byte 18 coding testing isn't jeopardized.

I agree with the Byte 18 "00" coding, it only hides the real coding and Zeroing after doesn't change the lighting ;-)
 

·
Registered
Joined
·
113 Posts
Discussion Starter #11
Hello.

We did the exercise. We had Ambiente model with the module 1K0 937 087 for testing. Finally in this car, the module is not working correctly, because it's always reporting the bulbs broken. The nearest best value is 33 (HEX).

I also tried this coding in a basic model and it fits perfectly. I just followed this link:

http://www.motor-talk.de/forum/led-rueckleuchten-fuer-golf-vi-t2374173.html?page=269

The tail lights with DRL's with coding 33(HEX) remain OFF, so this coding is OK>

There is also new question of coding the DRL's with Xenon lights. Do You think, there is any difference in byte 18, when Xenon lights are factory mounted and DRL are retrofitted by authorised workshop? They failed with this. I'm affraid to change anything in a brand new car.
 

·
Registered
Joined
·
126 Posts
I tried this on my Seat Leon Facelift, and came up with a cool result.
Standard Byte 18 value was 9D and i changed is to 9C. No fault codes found.
Before the change all lights were illuminated when Daytime running lights were enabled.

So my normal front lights and my taillights.

But now only my front lights are active.

But here comes the cool thing. I enabled DRL's on my foglights, and normally also the citylight would illuminate, but they don't anymore...:D So during the day i drive with only my foglights, and during the night my normal front lights + tail lights.
 

·
Registered
Joined
·
35 Posts
I tried this on my Seat Leon Facelift, and came up with a cool result.
Standard Byte 18 value was 9D and i changed is to 9C. No fault codes found.
Before the change all lights were illuminated when Daytime running lights were enabled.

So my normal front lights and my taillights.

But now only my front lights are active.

But here comes the cool thing. I enabled DRL's on my foglights, and normally also the citylight would illuminate, but they don't anymore...:D So during the day i drive with only my foglights, and during the night my normal front lights + tail lights.
Hello Adjego,

I followed your example and did the same thing today in my 2010 Altea.

My original Byte 18 coding was 19 (Hex) = 25 (Dec). I found the same description from the Byte 18 list but for Xenon instead of Halogen and changed the coding to 17 (Hex) = 23 (Dec).

And voila !! My DRLs (via Low Beam) light only, without the citylights or any of the rear lights !!

I tested for fault codes and there aren't any. I also tested all the other light functions and they work like a charm.

Thanks for idea my friend :D

This is what I wanted from the very beginning.

Rgrds
Dimitris
 

·
Registered
Joined
·
126 Posts
Hello Adjego,

I followed your example and did the same thing today in my 2010 Altea.

My original Byte 18 coding was 19 (Hex) = 25 (Dec). I found the same description from the Byte 18 list but for Xenon instead of Halogen and changed the coding to 17 (Hex) = 23 (Dec).

And voila !! My DRLs (via Low Beam) light only, without the citylights or any of the rear lights !!

I tested for fault codes and there aren't any. I also tested all the other light functions and they work like a charm.

Thanks for idea my friend :D

This is what I wanted from the very beginning.

Rgrds
Dimitris
Hi Dimitris,

Thanks...;)

Your initial setting was this: SE351/9 Halogen Halogen SE351/9 RdW TFL_S ROM 25
You changed it to this: SE351/9 Xenon XENON SE351/9 RdW TFL_0 XE ROM 23

It has to do with the TFL type. TFL_S is the scandinavian version which is all lights eluminated.
TFL_0 stands for no rear lights eluminated...:D

I used this website: Motor-Talk
 

·
Registered
Joined
·
6 Posts
Hi
I was reading this threat and i was wondering if someone could help me ..
I messed up with byte 18 in a European golf6 highline with halogen lights , fog lights and i have no taillights now..:banghead:
I cant find the correct value of the byte since 00 is what is shows and i couldn undersand the link in German with all these types and codes since i dont know what it refers to..
Can someone help me recode it??
 

·
Vendor
Joined
·
2,906 Posts
There is also new question of coding the DRL's with Xenon lights. Do You think, there is any difference in byte 18, when Xenon lights are factory mounted and DRL are retrofitted by authorised workshop? They failed with this. I'm affraid to change anything in a brand new car.
If the 09 module doesn't support Xenon lamps, the lighting output may actually be using different DRL wires/pins.

For example my car (2010 NAR, Gti) is factory equipped with Xenons and the PLR (Permanent Running Lights) coding. If I enable DRL's as separate lights, I get fault codes. This leads me to believe that I could install additional DLR's and I think the Byte 18 coding would change how they behave.


Hi
I was reading this threat and i was wondering if someone could help me ..
I messed up with byte 18 in a European golf6 highline with halogen lights , fog lights and i have no taillights now..:banghead:
I cant find the correct value of the byte since 00 is what is shows and i couldn undersand the link in German with all these types and codes since i dont know what it refers to..
Can someone help me recode it??
Try 02 or 03 on that car. If it fixes it, post the results here with some data from that module: For those with Byte 18 issues... (MK6)
 

·
Registered
Joined
·
6 Posts
Thanks Dana :)
The 02 worked for me great..
But now i have another strange issue.. When i drive in speed above 80km/h the rear wiper drops tears!
Ofcourse i cheked twice that the bit of teardrops in rear wiper is not enabled and its not..
Is there any chance this could be affected from the byte 18? What else could be going on here?:what:
 

·
Registered
Joined
·
113 Posts
Discussion Starter #18
If the 09 module doesn't support Xenon lamps, the lighting output may actually be using different DRL wires/pins.

For example my car (2010 NAR, Gti) is factory equipped with Xenons and the PLR (Permanent Running Lights) coding. If I enable DRL's as separate lights, I get fault codes. This leads me to believe that I could install additional DLR's and I think the Byte 18 coding would change how they behave.
[/url]

Of course You can do it.
If You connet the front daylights to the following pins:

Wehicles with powered rear windows:
48 (+ left bulb) and 49 (+right bulb) in the C-Relay

Wehicles without powered rear windows or simply 3 doors chassis:
7 (+ left bulb) and 8 (+right bulb) in the A-Relay

You will have it done. To avoid fault codes, the bulbs should be P21W.
 
1 - 20 of 71 Posts
Top