skmj
New Member
Posts: 9
|
Post by skmj on Mar 16, 2021 11:14:24 GMT
Hi guys, new OBDeleven user here. I've been doing several changes via the provided apps in OBDeleven and I'm mostly happy with the results. However, I've just noticed my parking lights have somehow changed settings/behavior and I'm confused how to revert back to the old settings while keeping the app improvements. I have been studying the DV52 coding white paper but so far I haven't gained a good enough understanding of how the different channels/banks/etc. work together, so I'm hoping you guys can help me out. My car is a MY15 MK7 2.0 TDI with the premium headlights (with DLA, etc.). It was sold new in Norway if this makes any difference. My problem right now is that the outer DRL "U" isn't lit up if the light switch is set to parking lights, only the innermost "dot" (to my understanding this should translate to only Leuchte8FL working, while Leuchte4TFL isn't - correct?). Before I started fiddling with the apps, both these were on with low brightness if parking lights were selected. If the switch is set to AUTO or dipped beam, the dot is on, but the U isn't. I have also noticed that when CH/LH lights are activated, only the dot is lit up with the fogs. I would like to have the DRL "U" on full brightness alongside the dipped beams and on the same brightness as the dot when parking lights are activated. I'd also like to keep full brightness DRLs (both U and dot) with fogs for switch setting "0". Can anyone point me in the right direction to solve this? Any pointers highly appreciated! Adding a couple of screenshots with current settings from the daytime running lights page along with Leuchte2, Leuchte4 and Leuchte8 settings for reference:     |
|
skmj
New Member
Posts: 9
|
Post by skmj on Mar 16, 2021 19:46:51 GMT
Okay, so after some more Googling and more fiddling I managed to both get the lights working as I would like to AND get even more confused in the process...  Now, my problem is that there seems to be some dimming value that overrides the other settings. So the DRL "U"s are full brightness in setting 0 and AUTO/dipped, but they will not dim when parking lights are selected regardless of dimming value. I also tried programming the parking lights to dim when the indicator/hazards are on, but I can only get them to turn off. However, the brightness does get reduced when DRLs are on and indicators are used. Can anyone help me and clear up how this is all tied together and how I can sort this out? I've attached my current "working" settings for the left side for reference.   |
|
|
|
Post by newty on Mar 16, 2021 19:58:57 GMT
Please have a look at 09->Daytime running lights-> "Standlicht aktiviert zusätzlich Tagfahrlicht". (Translates Parking lights also light up DRL):
In my EU car, this was active from factory (why???) - but causes the DRLs to go on full brightness when switching to parking lights.
|
|
skmj
New Member
Posts: 9
|
Post by skmj on Mar 22, 2021 8:21:25 GMT
Sorry, a bit slow to reply here. Thanks for your input though!
I was pretty sure that 09->Daytime running lights-> "Standlicht aktiviert zusätzlich Tagfahrlicht" wasn't activated, but I had to check to be sure.
Sooo... I'm still confused about what to do here. Does anyone have an idea why dimming values for DRL's are ignored/thrown away?
|
|
|
|
Post by dv52 (Australia) on Mar 22, 2021 21:21:46 GMT
skmj : Hi. I really don't understand what you are saying about the current state of the DRL lamps on your car and you haven't posted-up the FULL Leuchte-set values (meaning the complete 19 x adaptation channels).
Anyhow, if I'm correctly reading the data that you have made available - try this:
- Leuchte2SL VLB10-Lichtfunktion B 2 > not active
If my suggestion doesn't fix your problem, re-explain your problem using different words and post-up the FULL Leuchte-set values
Don
|
|
skmj
New Member
Posts: 9
|
Post by skmj on Mar 25, 2021 7:57:21 GMT
Thanks for your input, Don.
How can I export the current Leuchte-set values as you request without just dumping my coding history?
I find an export feature for coding history, but my history is so full of changes back-and-forth that I doubt it will be easy to trace it back to give meaningful insight. Maybe especially considering that the apps don't tell you what they change.
EDIT: My Lichtfunktion B 2 is already set "not active" for Leuchte2SL VLB10.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Mar 25, 2021 9:43:33 GMT
skmj I presume these settings are in control unit 09 in which case just take a backup of control unit 09 and post that so the guys can have a look at it as that will contain all the settings for the Leuchte-set values. I have documented how to here cupra280.co.uk/obd11.html#backup
|
|
skmj
New Member
Posts: 9
|
Post by skmj on Apr 7, 2021 16:43:40 GMT
Thanks so much for your input @testeronline ! I've tried following the steps outlined, but when I try to email the log the app says "generating log" before a red "unknown error" banner at the bottom appears. I can't really seem to get past this error, I've checked app permissions etc. but no luck. Getting a little bit frustrated because I'm not able to provide the information needed to get help with my original issue...  |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 7, 2021 18:02:06 GMT
Did you just do a backup of Control unit 09, and i presume you are using Android. Firstly do a clear cache of the app Secondly make sure when you are trying to get the backup that you use the filter for Backup only and set the Time to 7 days to ensure you keep the size down. If it fails at the start of the process then afraid its a support call. If it fails after a while then have a look on your phone using below details. There are times when the app is not working well so when you try and email files from the app it just does not work. This is a bug but if it happens The do a search on your phone for file called history.txt or in this folder Android/data/com.voltasit.obdeleven/cache/history.txt and send it manually via email. fingers crossed that helps.
Otherwise I am afraid its taking pictures.
|
|
skmj
New Member
Posts: 9
|
Post by skmj on Apr 7, 2021 20:42:18 GMT
Allright! Finally some progress on this  Although it's rather annoying to manually go through my phone to find what I'm looking for, it's easily forgiven considering how awesome obdeleven actually is in the grand scheme of things. Thanks again for your help, testeronline - much appreciated! BTW, Android 11 on S20 Ultra. Found my history.txt in Phone\Android\data\com.voltasit.obdeleven\files\ Okay, so here goes a dump of Control Module 09 from this afternoon. Hopefully it's human readable! Any help towards my previous questions regarding why dimming of parking lights is now acting up would be greatly appreciated! history.txt (120.13 KB) |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 7, 2021 21:16:37 GMT
dv52 (Australia) / newty are the expert's in these matters hopefully they can help but yes it is easily readable. Yes its a pain, its an occasion bug we see from time to time so I will raise it with support and hopefully they can fix it again.
|
|
|
|
Post by dv52 (Australia) on Apr 7, 2021 22:39:53 GMT
Now, my problem is that there seems to be some dimming value that overrides the other settings. So the DRL "U"s are full brightness in setting 0 and AUTO/dipped, but they will not dim when parking lights are selected regardless of dimming value. I also tried programming the parking lights to dim when the indicator/hazards are on, but I can only get them to turn off. However, the brightness does get reduced when DRLs are on and indicators are used. skmj : Hi again - seems like you have been on quite a learning journey (always a good thing IMO)
So - the behavior that you describe above is exactly how the lamps have been programmed.
I have replicated the pertinent Leuchte-set for the left-side lamp, but what I'm about to say also applies to the right-side Leuchte-set (i.e. Leuchte5 TFL RB32)
From your Back-up file:
Leuchte4TFL LB4
Lasttyp 4 > 1 - LED Tagfahrlichtmodul Versorgung
Lampendefektbitposition 4 > 3a
Fehlerort mittleres Byte DTC-DFCC 4 > 49
Lichtfunktion A 4 > Tagfahrlicht
Lichtfunktion B 4 > Abblendlicht links
Dimmwert AB 4 > 127
Lichtansteuerung HD AB 4 > always
Lichtfunktion C 4 > Standlicht allgemein (Schlusslicht, Positionslicht, Begrenzungslicht)
Lichtfunktion D 4 > nicht aktiv
Dimmwert CD 4 > 127
Dimming Direction CD 4 > maximize
Lichtfunktion E 4 > Blinken links aktiv (beide Phasen)
Lichtfunktion F 4 > nicht aktiv
Dimmwert EF 4 > 0
Dimming Direction EF 4 > minimize
Lichtfunktion G 4 > nicht aktiv
Lichtfunktion H 4 > nicht aktiv
Dimmwert GH 4 > 0
Dimming Direction GH 4 > maximize
Lichtfunktion B has been programmed for low-beam. This light-function is superfluous to what you want to do and it will clash with the Parking light function on Lichtfunktion C 4. Plus, full illumination of angel-eyes (i.e. what you call the "U's") at night-time via the setting on Dimmwert AB will blind on-coming traffic because the fittings don't have any cut-off characteristics. Setting-up the low-beam function on the "power-supply" Leuchte-set at full illumination normally isn't a problem - but in your case, the low-beam function doesn't appear on the "signal" Leuchte-set for the left-side lamp (i.e. Leuchte2SL VLB10) - so there is no control instructions to tell the central electrics module to how to use this function - hence, full illumination, I guess
I suggest that you change Lichtfunktion B 4 > nicht aktiv
Don
|
|
skmj
New Member
Posts: 9
|
Post by skmj on Apr 8, 2021 7:20:27 GMT
Thanks. I enjoy the learning process of this too. Although I'm not an expert in coding, I thought I had a basic understanding of it. Guess VW has proven me wrong, haha  I'll try what you suggest for for Lichtfunktion B4 to see what changes. But if you don't mind elaborating, why is there a clash between functions A/B and C/D in this case? My understanding from reading your white paper was that functions G/H had the highest priority over the other pairs, therefore, shouldn't a "call" (in lack of a better expression) for "Standlicht allgemein" override both "Tagfahrlicht" and "Abblendlicht links", and therefore set the output to this function? Now, I also see a potential problem that the Dimmwert CD 4 > 127, I guess that has means "Standlicht allgemein" will have the same brightness as the DRL's anyway? I guess same goes for the Dimmwert EF 4 > 0 - this won't only dim the DRL's but completely turn them off when the indicators are used, correct? Dimming direction seems incorrect, too. Hope you don't mind discussing these things with me a bit more. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Apr 8, 2021 8:46:29 GMT
Quick update, They have done a new release this morning v35.1 which fixes the bug on History email on Android 11.
|
|
|
|
Post by dv52 (Australia) on Apr 8, 2021 21:49:17 GMT
skmj I'm delighted that you have taken an interest in Leuchte-programming! As to your clarification questions, I recently answered similar questions HERE
Don
|
|
skmj
New Member
Posts: 9
|
Post by skmj on Apr 9, 2021 7:13:53 GMT
Thanks. That's was a very helpful thread to learn from. Considering the left side lamps in the following I just wish to clarify before going out and messing around a lot with how it setup currently: For a function I wish to perform on the Leuchte2SL (i.e. the "how to use" Leuchte-set), does each bank and alpha channel require it's own corresponding identical/supporting setting for the same bank on Leuchte4TFL(i.e. the "power supply" Leuchte-set)? Or to try to ask in a more graphical way: Does Leucte2SL Lichtfunktion E 2 always require a corresponding Leuchte4TFL Lichtfunktion E 4 in order to work? I'm under the impression that the answer isn't necessarily always yes, but I've been wrong many times before. My theory (for what it's worth) is that if the only setting on Leuchte4TFL is Lichtfunktions A 4 > aktiv 100 % with a dimmwert of 127 power will always be supplied to the DRL, then you can freely set up and stack priorities of how the lamp works in the Lichtfunktions for Leuchte2SL. Am I on to something here? EDIT: And now that I've given my theory some more thought, it probably wouldn't work because there would be no way to turn off the lamps with uninterrupted power coming to them. EDIT2: Solved! My theory was (obviously) incorrect. A corresponding "power supply" in Leuchte4TFL is required for each function you intend to use in Leuchte2SL. I'm a little puzzled why the Tagfarhrlicht function needs to have a higher priority than Standlicht Allgemein to work as I intented, but I finally got this working with correct dimming behaviour and everything so finding out why will have to wait for another day. I'd be happy to share screenshots and/or dumps from 09 if anyone needs it. Thanks to everyone who helped! |
|
Although it's rather annoying to manually go through my phone to find what I'm looking for, it's easily forgiven considering how awesome obdeleven actually is in the grand scheme of things. Thanks again for your help, testeronline - much appreciated!