sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 10, 2024 14:01:10 GMT
I apologize if I did something wrong, I'm new to the forum (and also sorry for my bad english)
in my golf mk7 with halogen headlights I replaced the H15s with an LED model, which act as DRLs and high beams.
When in low beam or high beam mode, no problem as the LEDs dedicated to the DRLs lower their intensity...
Unfortunately, however, if I put it in 0 mode or AUTO mode, the DRLs have a very strong intensity, almost as strong as the high beams.
In order not to disturb people who come towards me, I always keep the lights on manually so that the DRLs remain dim and do not bother me.
Over the years, this operation has caused the low beam halogen bulb to overheat, which has melted the housing of the conductive wires.
I have personally repaired this dissolution, but I would like to prevent it from happening again.
Throughout this premise, the question is:
It is possible to change the light intensity of the DRL LEDs only, when the selector is in "0" mode or in "AUTO" mode (daytime)
It would be enough to replicate the same intensity that is currently set automatically when the low beams are turned on.
Thank you very much to anyone who will be kind enough to answer me
PS. if it can help:
I'm in Italy and my 2014 halogen headlights have code 5G1941005 and 5G1941006
|
|
|
|
Post by dv52 (Australia) on Jun 10, 2024 21:34:39 GMT
sm4rk : Hi. Ain't nothing wrong with your English - I wish my Italian language skills were as good (both my parents were born in Italy)!! As for your question - I understand from your words that you want to reduce the illumination level of the DRL lamps when the rotary light switch is in the 0 position and during daytime in the AUTO position. This should be doable using the following steps (I assume that you have a PRO account):
- Ignition-ON, engine-OFF - plug the OBD11 dongle into the car's OBD port
- Fire-up OBD11 software and connect to the dongle
- Navigate to the Control Units screen and select the central electrics module
- Scroll-down and select Adaptation
- Enter "LB4" into the search-box and select Leuchte4TFL LB4 (this is the Leuchte-set for the left-side DRL lamp)
- Confirm the values of the following 2 x channels:
- Lichtfunktion A>Tagfahrlicht
- Lichtfunktion B >nicht aktiv
- The DRL illumination level for your wants is determined by the value of Dimmwert AB. As default, the factory setting is 100 (i.e. max illumination) and the value that is used to dim the DRL lights with low-beam lights is 31 - but you can select any value from 0-100 (I suspect that the value 31 will be too dim during daylight hours). ONLY IF the channel values in Step 6. are as shown - change the setting of Dimmwert AB to the desired value.
- Follow the OBD11 software prompts to implement the change (use security-code 31347)
- Go-back to Step 4.
- Enter "RB32" into the search-box and select Leuchte5 TFL RB32 (this is the Leuchte-set for the right-side DRL lamp)
- Repeat Step 6. to Step 8.
- Exit OBD11 software - remove dongle from the car's OBD port
Don
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 11, 2024 9:28:26 GMT
Thanks so much... thanks thanks thanks....
You don't know how long I've been looking for this modification... at one point I was almost about to go back to halogen.
It really solved a big problem for me... thank you so much!
It worked straight away for me as the entries were already set:
- Lichtfunktion A > Tagfahrlicht
- Lichtfunktion B > nicht aktiv
If I understood correctly (because I'm not very good at English) if I had had different entries I could only have put the value 31
while with the two correct entries I can put any value.... did I understand correctly?
or did I necessarily have to have the two items set correctly?
(to be safe I put 31, and fortunately it has perfect brightness)
- - - - - - -
I'll then ask you a second question if I don't bother you too much and if I may.
Now that I have correctly lowered the brightness during the OFF and AUTO positions,
is it possible to slightly increase the brightness when used together with the low beams to 50% and use 100% when using with the high beams since it is the same bulb?
|
|
|
|
Post by dv52 (Australia) on Jun 11, 2024 22:53:47 GMT
Thanks so much... thanks thanks thanks.... You don't know how long I've been looking for this modification... at one point I was almost about to go back to halogen. It worked straight away for me as the entries were already set: That's fantastic!! It's always good when a forum member is happy! If I understood correctly (because I'm not very good at English) if I had had different entries I could only have put the value 31 while with the two correct entries I can put any value.... did I understand correctly? or did I necessarily have to have the two items set correctly? ( to be safe I put 31, and fortunately it has perfect brightness) hmm...... not really! Without wanting to make this reply a master-class in Leuchte-programming - a Leuchte-set (like Leuchte4TFL LB4/Leuchte5 TFL RB32) has 8 x Lichtfunktion channels marked as A, B, C.....F. Lichtfunktion = Lighting function = Funzione luce
The basics set-up in a Leuhte-set is that each pair of Lichtfunktion channels has ONE Dimmwert channel that controls the illumination level for the 2 x specified light functions. So it wouldn't matter what values were in Lichtfunktion A and Lichtfunktion B, the Dimmwert AB value would still determine the dimming level!
Dimmwert = Dimming value = valore di attenuazioneNow that I have correctly lowered the brightness during the OFF and AUTO positions, is it possible to slightly increase the brightness when used together with the low beams to 50% and use 100% when using with the high beams since it is the same bulb? OK - now I have to make a huge assumption!! I'm not sure how this car was factory coded - but for the sake of an example, let's assume that Leuchte4TFL LB4 is coded like this: - Lasttyp 4 > 9 - allgemeine Glühlampe 27W; auch H15
- Lampendefektbitposition 4 > 48
- Fehlerort mittleres Byte DTC-DFCC 4 > 43
- Lichtfunktion A 4 > Tagfahrlicht
- Lichtfunktion B 4 > not active
- Dimmwert AB 4 > 100 (31 after your change)
- Lichtansteuerung HD AB 4 > Always
- Lichtfunktion C 4 > Blinken links aktiv (beide Phasen)
- Lichtfunktion D 4 > not active
- Dimmwert CD 4 > 0
- Dimming Direction CD 4 > minimize
- Lichtfunktion E 4 > Standlicht allgemein (Schlusslicht; Positionslicht; Begrenzungslicht)
- Lichtfunktion F 4 > Parklicht links (beidseitiges Parklicht aktiviert li & re)
- Dimmwert EF 4 > 31
- Dimming Direction EF 4 > maximize
- Lichtfunktion G 4 > not active
- Lichtfunktion H 4 > not active
- Dimmwert GH 4 > 0
- Dimming Direction GH 4 > maximize
Notice the channel structure that I described in my response to your earlier question: A Leutche-set has 8 x Lichtfunktion channels and each Lichtfunktion-pair has ONE related Dimmwert channel!
For the low-beam question: The Leuchte-command for switching-ON the DRL lamps with the low-beam lamps is in channel 12 above and as you can see - the Dimmwert EF value on channel 14 is 31. So, if you have understood my explanation to your previous question above (and if this car is coded as per my example), hopefully you can deduce that increasing the Dimmert value in channel 14 to 50 is the solution to the first part of your question (about the low-beam lighting function). If this car is NOT coded as per my example - look through the 8 x Lichtfunktion channels for the Leuchte-command in channel 12 above and change the related Dimmwert channel to 50.
Of course, you need also to make the SAME change to Leuchte5 TFL RB32. For the high-beam question: Try my suggestion below:
I'm not sure if you want the change to also apply to high-beam-flash (i.e. when the dash-stalk is pulled towards the driver)? If not- don't change Lichtfunktion H.
First confirm that the 2 x Leuchte-sets have existing values as shown below:
- Lichtfunktion G > not active
- Lichtfunktion H > not active
- Dimmwert GH > 0
Do NOT proceed if the values above are different!
Leuchte4TFL LB4
Lichtfunktion G 4 > Fernlicht links
Lichtfunktion H 4 > Lichthupe generell (for high-beam flash only)
Dimmwert GH 4 > 100 Leuchte5 TFL RB32
Lichtfunktion G 5 > Fernlicht rechts
Lichtfunktion H 5 > Lichthupe generell (for high-beam flash only)
Dimmwert GH 5 > 100
Don PS: A matter that hasn't been addressed in your posts is the fact that the central electrics module still believes that it should control the DRLs as factory fitted incandescent lamps. Of course this is incorrect because they are now actually LEDs.
For the 2 x DRL Leuchte-sets on this car, the value of the Lasttyp channel has remained the original factory setting 9-allgemeine Glühlampe 27W; auch H15 which translates to 9-general light bulb 27W; also H15, or to 9-lampadina generale 27W; anche H15 in your language. The H15 part is still OK because the lamp-base style has not changed - but the lamp is no longer 27 Watts and more importantly, it is an LED type (not the factory installed incandescent lamp)
I'm not sure if you are aware that the central electrics module is able to control LED lamps differently to incandescent lamps. If you look at the Lasttyp channel, you should notice that the allowable options are separated into two categories: those that refer to LEDs and those that don't! The latter cattery options are for incandescent lamps!
Since there are no errors on this car and the retrofitted LEDs operate correctly, there probably is no need to tell the 09 module that the lamps have been changed to LED type. Just something to consider-maybe?
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 12, 2024 6:36:25 GMT
wooowwww....
really a lot of information, you are really professional and I compliment you on how much you know....
The general concept is quite clear, but since if I mistranslate a single word I risk making a mistake,
if you agree I would proceed step by step... one question at a time.
Surely my configuration is set to read all bulbs in halogen mode since the headlight came from the factory with all filament bulbs.
Now to be sure I would like to scan the current settings.
How can I exclusively scan the entire current light module and bring it back here to you?
|
|
|
|
Post by newty on Jun 12, 2024 17:48:03 GMT
There is a oftenly overlooked adaption
„Standlicht aktiviert Tagfahrlicht“ („Parking Lights also activate DRL“) which overrides the Parking Light with the much brighter DRL setting, regardless of coding.
Worth a look when the parking lights are at DRL brightness
|
|
|
|
Post by dv52 (Australia) on Jun 12, 2024 23:32:00 GMT
really a lot of information, you are really professional and I compliment you on how much you know.... Yes, my replies do tend to be too long! My philosophy is that if a forum colleague has taken the time to write a reasonably detailed post - it's important that the reply is information-rich, But thank you for the generous words if you agree I would proceed step by step... one question at a time. Absolutely "yes" - you are solely in control of this thread!! Surely my configuration is set to read all bulbs in halogen mode since the headlight came from the factory with all filament bulbs. Yes, you are correct! If this car was factory built with halogen headlights and with halogen tail-lights - yes, your "configuration is set to read all bulbs in halogen mode". However, think about how this car is configured today compared to how it was configured when factory built? I don't know the complete answer to this comparison question because I don't know what other changes have been made to this car (if any). But you say in your first post "I replaced the H15s with an LED model, which act as DRLs and high beams". Therefore, I do know that the original DRL/High-beam halogen lamps have been replaced with LEDs.
So at least for the H15 lamps, the halogen configuration on this car at factory build time is different to today's configuration!
As I said in my previous reply - the new LED H15 lamps appear to be working OK and I assume that there are NO error messages appearing on the dashboard because you haven't mentioned it. This is good and it often does NOT happen when retrofitting these non-OEM LED H15 lamps. So, because this car has no error messages, my discussion about changing the Lasttyp channels to LED setting is more of a technical issue than being a necessary thing
Since it appears that this matter has complicated this thread, I suggest that you just ignore the issue for now and continue to allow the central electrics module to believe that it is controlling halogen H15 lamps in the headlights! We can re-visit this matter if errors appear on the dashboard after you have completed ALL of the changes that you want to make to the new LED H15 lamps.
Now to be sure I would like to scan the current settings. How can I exclusively scan the entire current light module and bring it back here to you? hmm........ I assume that you are not aware of what OBD11 calls a module "Backup". A Backup is a complete database copy of every adaptation channel in a module including each channel value and the long-code string (if the module has a long-code facility). Of course the channel values in a Back-up file only apply for the module at the time that the database file is created! A Backup should not be confused with the term "SCAN" as used by OBD11. A SCAN is a different report that identifies each module in the car and its error status - and it includes details of any fault-characteristics in each module - if present at the time when the SCAN is undertaken So, in summary: - Backup -> OBD11 polls a module for a complete data-dump of every adaptation channel and its current value.
- SCAN -> OBD11 polls the entire car for a report of each module's identity and it's error status (as well as details of fault characteristic, if any)
I suspect that for your purpose, a Backup is more useful! Read HERE to create a Backup file of the central electrics module on this car After the Backup procedure has been created, the resulting database file will be stored against your account on OBD11's central-servers. To extract a copy of the Backup file from your account so that you can include it in a post here, do the following (for the iOS version of OBD11 software):
- I assume that you have completed the Backup process and OBD11 software is still connected to the car
- Navigate back-to the Control Units screen
- Select 09-central electrics module (again)
- Scroll-down and select History - you should see the first screenshot below (of course the details on your screen will be different)
- Follow the procedure in my screenshots
- On the second screenshot, remove ALL ticks except Backup (scroll down to ensure that ticks for hidden elements are cleared)
- After you receive the email that you sent to yourself from the last screenshot, include a copy of the Backup file in a new post. Note: the file will be big, so it's better not to paste the file contents into a post - instead, add the Backup file as an attachment
Finally, you can use the same instructions above if you want to include a copy of a SCAN report for this car to a post with the following change: - for Step 6 above, de-select ALL ticks except FULL SCAN
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 13, 2024 6:59:57 GMT
I followed the instructions exactly for backing up from the link provided, and I hope I did the backup correctly. Is it possible that it is a TXT format? I attach it to this answer. If you then have the link to restore the backup performed, I would feel safer before starting any other changes, I wasn't able to find it on my own. Furthermore, as you requested, I am attaching the last full scan done two days ago when I deleted the error of the old halogen bulb that had burned out the housing. [there is only one perpetual error that I can't erase, as 3 years ago the seat resistor burned out and was replaced. maybe in OT there is a solution to eliminate that error too, but not important] |
|
|
|
Post by dv52 (Australia) on Jun 13, 2024 9:30:30 GMT
sm4rk : well done -the 2 x files are perfect!! Yes, OBD11 formats the Backup-file as .TXT - I have no idea why!! I have complained many times that a much better file format for a database file is .CSV (i.e. a flat file format)- but the deities on the OBD11 mother-ship are not listening! OK, because you said "I would proceed step by step... one question at a time" lets ONLY address the following request in this reply
is it possible to slightly increase the brightness when used together with the low beams to 50% Below, I provide a copy of the values for Leuchte4TFL LB4 from your Backup information: - Lasttyp 4 > 9 - allgemeine Glühlampe 27W; auch H15
- Lampendefektbitposition 4 > 48
- Fehlerort mittleres Byte DTC-DFCC 4 > 43
- Lichtfunktion A 4 > Tagfahrlicht
- Lichtfunktion B 4 >nicht aktiv
- Dimmwert AB 4 > 31
- Lichtansteuerung HD AB 4 > Always
- Lichtfunktion C 4 > Blinken links aktiv (beide Phasen)
- Lichtfunktion D 4 > nicht aktiv
- Dimmwert CD 4 > 0
- Dimming Direction CD 4 > minimize
- Lichtfunktion E 4 > Standlicht vorn (Positionslicht; Begrenzungslicht)
- Lichtfunktion F 4 > Parklicht links (beidseitiges Parklicht aktiviert li & re)
- Dimmwert EF 4 > 31
- Dimming Direction EF 4 > maximize
- Lichtfunktion G 4 > nicht aktiv
- Lichtfunktion H 4 > nicht aktiv
- Dimmwert GH 4 > 0
- Dimming Direction GH 4 > maximize
Hopefully you can see that the values above are EXACTLY the same as the Backup information - except that ihey are in a more readable format The adaptation channel in the list above that determines how the DRLs operate after-dark is: - Lichtfunktion E 4 > Standlicht vorn (Positionslicht; Begrenzungslicht)
This is the rotary light switch which I believe is installed in this car: With the Leuchte-command Standlicht vorn (Positionslicht; Begrenzungslicht) and at night-time, the ONLY way that the DRLs will illuminate on this car is if the rotary light switch is in the  position. This is called the Parking Light, or Position Light, or Boundary Light function (not sure what term is used in Italy) Or said another way, if the rotary light switch on this car is in the AUTO position and at night-time, the Low-beam lights will automatically switch-ON- but the DRLs will NOT turn-ON. The same will happen if the rotary light switch is moved to the  position (low-beam ON) - the DRLs will NOT turn-ON. This occurs because Standlicht vorn (Positionslicht; Begrenzungslicht) means Front parking light (position light; boundary light) So, I'm confused by the words in your first post "When in low beam or high beam mode, no problem as the LEDs dedicated to the DRLs lower their intensity...". Low-beam mode should NOT turn-ON the DRLs (with, or without "reduced intensity") with the coding in your Backup. And you include "high beam mode", but again according to the Backup, the DRLs will not work at all in this mode! It's entirely your choice, but I provide two options for your request to increase the after-dark illumination of the DRLs to 50%:
- Either accept the way that the DRLs currently operate after dark as per your Backup - in which case, change
- Leuchte4TFL LB4
- Leuchte5 TFL RB32 -
- Or, alter the current DRL operation after dark to automatically switch-ON with low-beam lights - in which case, change:
- Leuchte4TFL LB4
- Lichtfunktion E 4 >Standlicht allgemein (Schlusslicht; Positionslicht; Begrenzungslicht)
- Dimmwert EF 4 > 50
- Leuchte5 TFL RB32
- Lichtfunktion E 5 >Standlicht allgemein (Schlusslicht; Positionslicht; Begrenzungslicht)
- Dimmwert EF 5 > 50
You can use the same step-by-step instructions that I provided earlier to implement your chosen option - that is:
- Ignition-ON, engine-OFF - plug the OBD11 dongle into the car's OBD port
- Fire-up OBD11 software and connect to the dongle
- Navigate to the Control Units screen and select the central electrics module
- Scroll-down and select Adaptation
- Enter "LB4" into the search-box and select Leuchte4TFL LB4 (this is the Leuchte-set for the left-side DRL lamp)
- For the chosen option, make the changes listed above for Leuchte4TFL LB4 and follow the OBD11 software prompts to implement the change (use security-code 31347)
- Go-back to Step 4.
- Enter "RB32" into the search-box and select Leuchte5 TFL RB32 (this is the Leuchte-set for the right-side DRL lamp)
- For the chosen option, make the changes listed above for Leuchte5 TFL RB32 and follow the OBD11 software prompts to implement the change
- Exit OBD11 software - remove dongle from the car's OBD port
We can deal with your high-beam light question when you have completed these changes
Don
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 13, 2024 10:22:47 GMT
actually, after your explanation I checked better and you're right...
in "OFF" mode only the H15 at intensity 31 (recently modified) are activated
when taking a photo there is a flicker effect due to the weakening
when the low beams are activated the H15 is completely off and only the halogen H7 is on
When the high beams are activated, the H7 halogen low beam remains on and the H15 turns on at 100% intensity (in the photo there is no flicker because it is not weakened)
At this point I apologize if I made you confused and wasted your time trying to understand...
In light of this correct configuration, do you think such a configuration could be possible?:
Selector on "0" = everything off
Selector on "AUTO" = DRL only, 15% intensity in daylight
Selector on "positions"= DRL intensity 15% (same as "AUTO" mode)
Selector on "low beam"= H7+DRL 31%
High beam = H7+DRL 100%
|
|
|
|
Post by dv52 (Australia) on Jun 13, 2024 11:10:54 GMT
My responses to your questions in blue In light of this correct configuration, do you think such a configuration could be possible?:Selector on "0" = everything off Change Daytime running lights -Tagfahrlicht nur in Schalterstellung AUTO to activeSelector on "AUTO" = DRL only, 15% intensity in daylight Change Dimmwert AB to 15 for the 2 x DRL Leuchte-sets (very similar to your previous request).
What happens to the DRL lamps after-dark in the AUTO position?
Selector on "positions"= DRL intensity 15% (same as "AUTO" mode) Change Dimmwert EF to 15 for the 2 x DRL Leuchte-sets (again, very similar to your previous request)Selector on "low beam"= H7+DRL 31% This depends on your answer to my question - what happens to the DRL lamps after-dark in AUTO position
High beam = H7+DRL 100% This will energize both LED elements in the H15 lamps (equivalent to energizing both filaments in your old halogen H15 lamps)- is the thermal power rating of your new DRL lamps sufficient to operate both LED elements at the same time? If not, this change will destroy the H15 lamps!!
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 13, 2024 12:35:41 GMT
1. Selector on "0" = everything off
Change Daytime running lights -Tagfahrlicht nur in Schalterstellung AUTO to active
so just need to change find the parameter Daytime running plights and change in Schalterstellung AUTO
2. Selector on "AUTO" = DRL only, 15% intensity in daylight
Change Dimmwert AB to 15 for the 2 x DRL Leuchte-sets (very similar to your previous request).
yes, it's actually the exact same edit as last, just change from 31 to 15
2B. What happens to the DRL lamps after-dark in the AUTO position?
after dark, the function remains the factory one by default... it practically automatically activates the low beam position**
3. Selector on "positions"= DRL intensity 15% (same as "AUTO" mode)
Change Dimmwert EF to 15 for the 2 x DRL Leuchte-sets (again, very similar to your previous request)
ok, I think I can do it on my own
4. **Selector on "low beam"= H7+DRL 31%
This depends on your answer to my question - what happens to the DRL lamps after-dark in AUTO position
currently in the dark only the low beam H7 halogen lights up and the H15 turns off completely... If possible I would like to have the H15 light up at 31% to give a white effect to the current yellowish halogen...
But if it can't be done, it doesn't matter
5. High beam = H7+DRL 100%
This will energize both LED elements in the H15 lamps (equivalent to energizing both filaments in your old halogen H15 lamps)- is the thermal power rating of your new DRL lamps sufficient to operate both LED elements at the same time? If not, this change will destroy the H15 lamps!!
in theory this is not a modification but a confirmation of current functioning, as currently when I turn on the high beams (either if I move the lever forward or if I pull it towards me) the basic halogen low beam remains on, and the H15 is already activated (I think and hope already 100%)
I hope I have been clarifying, and not confusing things
|
|
|
|
Post by dv52 (Australia) on Jun 13, 2024 22:45:35 GMT
I have added numbers to the multiple requests in your last reply for clarity.
hmm..........stuff is becoming complicated!!! I suggest that you first implement those changes in your last post that are easy. After these are completed successfully, we can then proceed with your remaining requests For example - request 1, 2, 2B (no change needed), 3 can be easily implemented.
Don
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 14, 2024 5:46:21 GMT
you know, I was also thinking about numbering them yesterday...  back to question, OK, today I'll make changes 1-2-3 and then we'll see if we can do the others... in the end, the other modification are not important anyway. Before starting, can I ask you if you have the link to understand how to restore the txt backup in case I make something mistake? I would feel more comfortable editing if I already knew how to restore everything. I would like to inform that I made both backups, of the specific module 09 and full backups of the car too.
|
|
|
|
Post by dv52 (Australia) on Jun 15, 2024 1:11:59 GMT
sm4rk : I entirely understand your need for reassurance before proceeding given your status as a newbie OBD11 user! The way to "restore everything" with OBD11 is via the History facility. Each and every time that you make a coding change with OBD11, details about the modification are recorded in a special database that is stored against your OBD11 account number. I include below an example of the type of information that is stored in a typical History change-record. In my example, the OBD11 user changed: Leuchte4TFL LB4
- Lichtfunktion G 4 > Nebellicht links
- Dimmwert GH 4 > 127
---------------------------------------------------------------
Adaptation
Control unit: 09 Central Electrics
Name: Leuchte4TFL LB4
Values:
Lichtfunktion G 4:
Old value: nicht aktiv
New value: Nebellicht links
Dimmwert GH 4:
Old value: 0
New value: 127
Mileage: 51007 km
Date: 2022-11-01 21:18
---------------------------------------------------------------
As you can see, History records are date/time stamped and they identify both the new and old value for each coding change. So, there is sufficient information in these records to enable an OBD11 user to revert a coding change back to the original value- if needed
Please note that this is a MANUAL process that involves the separate reversion of each individual coding-change in a module. OBD11 does NOT have an automated "un-do" facility for reverting multiple coding-changes in a module (unlike VCDS - which does have this function).
This is how to access data from the History facility using the iOS version OBD11 software: - Fire-up OBD11 software - no need to connect to the dongle
- On the Home screen - select Garage/Vehicle (bottom-left of the screen)
- If you have registered multiple vehicles to your account - select the correct car
- Scroll-down the car-information screen and select History.
It's also possible to access History for a particular module, by scrolling-down the selection-options on the main screen for that module - when OBD11 is connected to the car
Bexause you have already made coding changes with your OBD11 device, you should find similar History records like those above against your account. I suggest that you take a look!
Don
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 15, 2024 8:55:29 GMT
ah... so there is no automatic restore way...
I can only manually go back with the changes.. ok, fine, thanks for the thorough explanation.
I've started making the changes you described in previous posts, and I have good news.
Simply by making the new modification 1 (deactivation to OFF) and changing modification 2 from value 31% to value 10%, I also automatically obtained modification 3!!
This is because the dimmewert EF was already set to 31%.
At this point I can say that I have almost as requested!
as it currently works like this:
1)pos.0=everything off
2)pos.auto=daylight_only_drl10% night_only_lowbeam
3)pos.position=only_drl31%
4)pos.lowbeam =only_halogen_h7_lowbeam
5)manual_highbeam=halogen_h7+drl(i think 100%,but i'm not sure)
at this point, without even doing much, I got almost all the required configuration with the exception of modification 4) where I would have liked to have together with the current halogens even a small percentage of drl...
but if you think it's a difficult modification, it doesn't matter, it's not important...
in the end I'm quite satisfied with this current result!!
|
|
|
|
Post by dv52 (Australia) on Jun 15, 2024 22:59:16 GMT
sm4rk : Well-done!! I'm glad that you are happy!!
Hopefully you are now more comfortable using OBD11 to make manual coding changes. I suggest that you keep practicing your new skills to further your knowledge! And most importantly, I recommend that you try to make a few errors because these events are the best environment for learning! OK - back to request 4 (NO, I don't "think it's a difficult modification").
Make the following changes:
Leuchte4TFL LB4 - Lichtfunktion G 4 > Abblendlicht links
- Dimmwert GH 4 > *
Leuchte5 TFL RB32- Lichtfunktion G 5 > Abblendlicht rechts
- Dimmwert GH 5 > *
* = select the desired illumination level (I'm not sure what value you want)
Note: when choosing the value for Lichtfunktion G above - make sure that you don't confuse Abblendlicht links/rechts with Abbiegelicht links/rechts (the two Leuche-commands look similar - but they are very different)
Don
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 17, 2024 6:04:25 GMT
Thanks, I can't try the change for a couple of days as I don't physically have the car.
I'll update you as soon as I do it, but I'm sure it will be a success like all the modifications you taught.
In the meantime I would like to ask...
Currently I have no bulb errors in the module, although an incandescence is set instead of the H15 led DRL.
If I changed the value from incandescent to LED, what would substantially change?
just to understand
|
|
|
|
Post by dv52 (Australia) on Jun 17, 2024 9:11:12 GMT
Hmm................ your question might sound simple - but it isn't because the answer involves a discussion about the technical basis for how the central electrics module controls lighting!!
At the heart of the answer is an engineering principle called Pulse Width Modulation (PWM) - which is the system that is used to dim lamps to different levels. You might think that a lamp on this car is dimmed by applying a lower voltage to the lamp but this is NOT what happens (well, not directly at least)
What actually happens for lamp dimming is PWM. This is the process whereby electronic circuits inside the module chop-up the battery rail voltage by rapidly switching the 12Volt supply ON/OFF to create a square-wave. The ratio of the ON-time and the OFF-time of the square wave determines the dimming level. This ratio is called the "duty cycle". Here's some examples of PWM with different duty cycles:
Hopefully you can see that feeding a lamp with the 3 x wave forms above will change the dimming level of the lamp. Increasing the ON-time compared to OFF-time in the waveform will make the lamp brighter and vice-a-versa. PWM does change the "effective" supply-voltage to a lamp - but it does this in a far more efficient manner with much lower power/thermal loss!
When you used Leuchte-programming to change the Dimmwert values in my suggested tweaks - you actually changed the duty-cycle of the PWM waveform that supplied power to the lamp.
The central electrics module on this car can use a different form of PWM to separately control LED lamps and halogen lamps. VW designed the module in this manner to increase the efficiency of the power-supply for the many lighting functions that Leuchte-programming can deliver.
I call VW's PWM method for halogen lamps "analogue" control because the Dimmwert value range is 0 ->100, whereas I call PWM for LED lamps "digital" control because the Dimmwert value range is 0 -> 127.
I use the term "digital" for LED control because a total of 128 x different dimming states is the highest quantity for a 7 x Bit binary number (yes, this discussion is a bit geeky).
Halogen lamps can tolerate PWM well without many problems - but LED lamps are not so tolerant and often the semiconductor in the LED lamp requires very strict PWM characteristics to operate properly. The other problem is that there are a huge number of manufacturers of LED lamps - each making non-OEM lamps with different operating characteristics! That's why retrofitting non-OEM LED lamps into a mk7 can sometimes result in error messages!
So, the shorter answer to your question is that because the non-OEM LED lamps that were retrofitted to this car did NOT result in error messages -not much would change if you told the central electrics module to use the LED style PWM system.
Changing the Leuchte-set values to LED type in this case would simply be a technical nicety - so probably not worth doing, IMO
Don
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 18, 2024 5:32:27 GMT
the answer seems difficult to understand, but I actually understood it quite well.
Probably because you have a very simple and schematic way of explaining things...
I have to congratulate you again for this.
I'm happy to have "met" a person like you!.
In light of this explanation, it is true that the h15 LED I used did not generate errors, perhaps because it has a greater tolerance, but from a future perspective, keeping it under inappropriate stress for a long time could not lead to premature exhaustion or a breakup earlier than normal?
Maybe the correct PWM can help increase the life cycle and longevity of the LED lamp?
|
|
|
|
Post by dv52 (Australia) on Jun 18, 2024 6:00:18 GMT
sm4rk : Thank you for the generous words!! I am delighted to be of assistance and likewise to "meet" un connazionale così educato del paese di nascita dei miei genitori As I have said, making coding changes to align the PWM system to LED is normally used to fix error messages!! In all honesty, I cannot confirm that "the correct PWM can help increase the life cycle and longevity of the LED lamp". There is NO evidence that changing the PWM system has any effect on the life-cycle of an LED and I suspect if it does - the impact will be marginal at best. So, NO significant impact on longevity!
Don
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 18, 2024 6:29:26 GMT
ok I understand. I keep the current configuration... if perhaps one day it fails and I go to replace it with another brand, I will later check the presence or absence of errors... in this case I know that I will only have to modify that value to resolve it. In the meantime, while I'm waiting to get the car back to make the last change discussed over the weekend, I wanted to open a very small OT. or if you prefer, we can open a new discussion to leave this one clean to the initial topic. I don't know if you noticed the result of my scan, there is a small error that I haven't been able to eliminate for years. in 2021, following the failure of the heated seat element, it was replaced. From that moment it has always worked correctly, but OBD11 has always detected a permanent error that cannot be eliminated. Do you think there is any way to eliminate that error since the resistance works correctly?
Talking to a guy on an Italian forum, he told me that I probably had the old model resistor coded in the control unit, while the one mounted was the new version which changed slightly from the previous one... He also provided me with the following photos to show me the difference (attachment).. But I don't know if this difference in resistance really exists Do you think there is a possibility of eliminating that error?
  Attachments:
|
|
|
|
Post by dv52 (Australia) on Jun 18, 2024 22:47:26 GMT
Marco: Yes, I did see the seat heater error in your SCAN! First, we need to confirm the veracity of the information that has been provided about this car! Are you sure that you have the correct wiring diagram? Look again at the SCAN that you posted earlier - notice that it reports the build year as 2014. This means that this car was built before the Golf mk7.5 model (i.e. before the Golf Face-Lift). I suspect that the wiring diagrams that you included in your last post are for a Golf mk7.5, not for a Golf mk7 - there is a big difference for seat heating!
This is what I believe is the correct wiring diagram for your car: Notice the difference - the two wiring diagrams are definitely NOT the same -so using the correct information is crucial to diagnosing this problem!!!
OK - let's now deal with the error code on your SCAN report! Almost certainly, this fault is likely caused by a physical break/short in a wire/connector and/or in the heater elements in the seats. I use the term "likely" because there can be NO guarantees in diagnostic analysis!
I'm not sure how familiar you are with VW's wiring diagrams- but this is how they are read: Notice T10a /5 at the left-side of TSVL on the brown (br) wire of my diagram above. T10a /5 means: - T10 = a connector with a Total of 10 x pins
- a = a simple descriptor that identifies this connector from the other 10 x pin connectors on this car
- /5 = pin #5
ALL of the remaining designations in the wiring diagram are read in the same way as above. Also, J519 is what OBD11 calls central electrics module
So, I suspect the first step in fault-finding this problem is to measure the heating element resistances at TSVL which is the coupling station located on the left-side under the driver seat .
Again, I'm not sure of your understanding of electrical circuits, or if you are confident using a multi-meter to make resistance measurements - so I don't know if you want to proceed and if so, how much detail to provide!
Don
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 19, 2024 5:35:21 GMT
yes my golf is from 2014, so it's not a 7.5.
No, I'm not very familiar with wiring diagrams, but I know how to use a multimeter.
The images I sent were sent to me by a guy to make me understand what the problem could be... but they are not the diagrams of my car.
the resistance now works perfectly...but it has always given the error since the first day of the replacement in 2021.
would you prefer if we opened a new thread so as not to go Off Topic here?
|
|
|
|
Post by dv52 (Australia) on Jun 19, 2024 6:19:44 GMT
yes, commence a new thead and start your first post with as much historic data about this problem as you can - please
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 19, 2024 7:20:48 GMT
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 21, 2024 20:44:19 GMT
sm4rk : Well-done!! I'm glad that you are happy!!
Hopefully you are now more comfortable using OBD11 to make manual coding changes. I suggest that you keep practicing your new skills to further your knowledge! And most importantly, I recommend that you try to make a few errors because these events are the best environment for learning! OK - back to request 4 (NO, I don't "think it's a difficult modification").
Make the following changes:
Leuchte4TFL LB4 - Lichtfunktion G 4 > Abblendlicht links
- Dimmwert GH 4 > *
Leuchte5 TFL RB32- Lichtfunktion G 5 > Abblendlicht rechts
- Dimmwert GH 5 > *
* = select the desired illumination level (I'm not sure what value you want)
Note: when choosing the value for Lichtfunktion G above - make sure that you don't confuse Abblendlicht links/rechts with Abbiegelicht links/rechts (the two Leuche-commands look similar - but they are very different)
Don
going back to where we left off, today I made the change by setting the brightness to 50%. this weekend I will test them on the road in the evening to see the effect and above all to understand if they can bother others. In any case, as always, your modification worked the first time... You are flawless! 🤗 |
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jun 24, 2024 7:55:30 GMT
as promised over the weekend I tested the low beam configuration with the DRLs at night.
Even though no car coming towards me has ever flashed at me, I think it can bother people a little.
I will do some tests over the next few nights to gradually lower the brightness from the current 50%.
Also because, actually thinking about it, the portion of the headlight that creates the DRL is the same as that which creates the high beam... therefore a value that is too high can be annoying even if reduced by half its power...
I will update the final solution here as soon as I find it.
in the meantime I realized that although I paid attention to the difference between "Abblendlicht links/rechts" and "Abbiegelicht links/rechts", I carelessly set Abblendlicht links for both "Lichtfunktion G 4" and "Lichtfunktion G 5", instead of the correct "Abblendlicht rechts" at G 5.
What does this error cause? Because in reality it seems to me that it works correctly as I wanted.
in summary, it is currently configured incorrectly like this:
Lichtfunktion G 4>Abblendlicht links V
Lichtfunktion G 5>Abblendlicht links X
|
|
|
|
Post by dv52 (Australia) on Jun 24, 2024 22:55:43 GMT
Also because, actually thinking about it, the portion of the headlight that creates the DRL is the same as that which creates the high beam... therefore a value that is too high can be annoying even if reduced by half its power... Yes, you are correct, both the DRLs and high-beam lamps on halogen headlight fittings on a Golf mk7 use the same reflector - which does NOT have the correct cut-off characteristics for nighttime driving on shared carriageways! That is the reason why most DRLs are factory disabled when the low-beam lamps are switched-ON on this car - and it's also why DRLs are factory coded to dim to 31% when used as Parking-Lights/Position-Lights in the meantime I realized that although I paid attention to the difference between " Abblendlicht links/rechts" and " Abbiegelicht links/rechts", I carelessly set Abblendlicht links for both "Lichtfunktion G 4" and "Lichtfunktion G 5", instead of the correct "Abblendlicht rechts" at G 5. What does this error cause? Because in reality it seems to me that it works correctly as I wanted. in summary, it is currently configured incorrectly like this: Lichtfunktion G 4>Abblendlicht links VLichtfunktion G 5> Abblendlicht links XAbblendlicht links/rechts=Low beam left/right Abbiegelichts links/rechts = Cornering light left/right
For halogen low-beam lamps, it doesn't matter if you coded the right-side lamp with the left-side Leuchte-command for the low-beam function - because these headlight fittings are very simple. However, this error is important for more sophisticated fittings like Xenon/LED headlights with Dynamic Light Assist where the lamps swivel around curving roads for better visibility
Even though the inadvertent error doesn't matter in your car - as a technical nicety and because it offends the rules of Leuchte-rogramming (which I find abhorrent! ), I suggest that you use the correct setting for the right-side low-beam lamp - please!
|
|
sm4rk
New Member
Posts: 19
|
Post by sm4rk on Jul 3, 2024 14:00:52 GMT
With this message I just wanted to update my final configuration which appears to be functional and which does not disturb the opposing cars. At the same time, I then take this opportunity to attach a reminder programming diagram for any future changes to the values. I hope it can be useful to someone else in the future.  DRL intensita.pdf (60.37 KB) |
|
