|
|
Post by dv52 (Australia) on Oct 5, 2022 19:56:45 GMT
hmm....... I don't think so!!
Unless this is a very unusual car (aside from having the most peculiar coding in the hex09 module) - that particular rotary light switch DOES have a rear fog light switch (this is required as part of the road rules in ALL world markets)!! Try this: turn the switch to either the  (Parking-Lights/Side-lights) position, or to the  (low-beam) position. Then pull-out the center turret of the rotary light switch.
The rear fog should illuminate and you should get a light symbol  appear on your dash inside the upper right of the tacho dial to confirm the lighting function.
It isn't possible to pull-out the center turret if the rotary light switch is in the  position. This is all explained in the owner's manual!
As for the fog light illuminating with reverse, this is a common tweak - it is used to provide greater illumination when reversing - it likely won't be the cause of an error message
Don
|
|
grbac
Junior Member
Posts: 51
|
Post by grbac on Oct 6, 2022 15:46:20 GMT
Hi Don,
the rotary switch can't be pulled, I tried it too. I'll just buy the one with the fog light function.
Do you, by any chance, have the "stock/factory" code for my type of lights for the following adaptations?
Leuchte 35 LED Warnblinktaster C48
Leuchte27NSL RC6
Leuchte23SL HLC10
thank you in advance
|
|
|
|
Post by dv52 (Australia) on Oct 6, 2022 21:42:25 GMT
the rotary switch can't be pulled, I tried it too. I'll just buy the one with the fog light function. hmm......I'm surprised that your car has an actual fog-light lamp integrated into the tail-light fittings and yet it doesn't have a rotary light switch with a fog-light facility. I hope that you concur with my incredulity and with my conclusion that this is a very odd arrangement!! The only way that such a strange set-up makes sense (to me at least) is that the tail-lights on your car are not factory fitted- but rather they have been retrofitted to the car as an after-sale item. If this is correct, then the oddness of the non-OEM arrangement for the tail-lights raises the further specter that the wiring from the hex09 module to the tail-lights is also non-OEM. And if this is true (as I believe that it must be true) then "we have a problem Huston"!! So, here's the thing - yes, you can "buy the one with the fog light function" and yes, you can plug a new rotary-light-switch (it's called a "LDS") into the existing connector on the car - BUT!!
Why do you believe that simply installing a new LDS will work? Or asked another way, why do you believe that this car has the requisite wiring loom for a new LDS that can operate the rear fog-light - when this is a car that was built in Mexico without a LDS that had fog-light capability and presumably, also was NOT fitted with tail-lights that had a fog-light lamp?
VW is not known for their largess for cars that leave the production-line!! In fact, quite the opposite - VW are renown of cost efficiency where-ever possible on their production-line. Meaning that in general, factory built cars are fitted with just the correct amount of copper wiring needed (no more, and no less)!!
Do you, by any chance, have the "stock/factory" code for my type of lights for the following adaptations? Leuchte 35 LED Warnblinktaster C48 Leuchte27NSL RC6 Leuchte23SL HLC10 thank you in advance Again, hmm........!!
Why do you ask - at least one of these Leuchte-sets (and maybe two) are not used on a Golf mk7 which has factory fitted incandescent tail-lights? Maybe further confirmation that this is a car with non-OEM tail-lights?
Perhaps the better way forward for your question is for you to post-up the values for these Leuchte-set on your car? To be clear, I need to see ALL 19 x channels for each Leuchte-set (either in screenshots, or as a typed-list)
|
|
grbac
Junior Member
Posts: 51
|
Post by grbac on Oct 7, 2022 0:08:39 GMT
Hi Don,
about the LDS, with the purchase of a LDS I'm just hoping it will work so I can at least use the rear fog light instead of just having it without a switch that can turn it on.
For the adaptations:
--------------------------------------
Leuchte 35 LED Warnblinktaster C48
--------------------------------------
Lasttyp 15
41 - LED Kleinleistung
Lampendefektbitposition 15
0
Fehlerort mittleres Byte DTC-DFCC 15
6
Lichtfunktion A 15
Nicht aktiv
Lichtfunktion B 15
Nicht aktiv
Dimmwert AB 15
100
Lichtansteuerung HD AB 15
Always
Lichtfunktion C 15
Nicht aktiv
Lichtfunktion D 15
Nicht aktiv
Dimmwert CD 15
0
Dimming Direction CD 15
Maximize
Lichtfunktion E 15
Nicht aktiv
Lichtfunktion F 15
Nicht aktiv
Dimmwert EF 15
0
Dimming Direction EF 15
Maximize
Lichtfunktion G 15
Nicht aktiv
Lichtfunktion H 15
Nicht aktiv
Dimmwert GH 15
0
Dimming Direction GH 15
Maximize
--------------------------------------
Leuchte27NSL RC6
--------------------------------------
Lasttyp 27
36 - LED Kleinleistung
Lampendefektbitposition 27
0
Fehlerort mittleres Byte DTC-DFCC 27
47
Lichtfunktion A 27
Blinken links Hellphase
Lichtfunktion B 27
Nicht aktiv
Dimmwert AB 27
127
Lichtansteuerung HD AB 27
Always
Lichtfunktion C 27
Nicht aktiv
Lichtfunktion D 27
Nicht aktiv
Dimmwert CD 27
0
Dimming Direction CD 27
Maximize
Lichtfunktion E 27
Nicht aktiv
Lichtfunktion F 27
Nicht aktiv
Dimmwert EF 27
0
Dimming Direction EF 27
Maximize
Lichtfunktion G 27
Nicht aktiv
Lichtfunktion H 27
Nicht aktiv
Dimmwert GH 27
0
Dimming Direction GH 27
Maximize
--------------------------------------
Leuchte23SL HLC10
--------------------------------------
Lasttyp 23
18 - 2* 5W
Lampendefektbitposition 23
A
Fehlerort mittleres Byte DTC-DFCC 23
29
Lichtfunktion A 23
Blinken rechts Hellphase
Lichtfunktion B 23
Nicht aktiv
Dimmwert AB 23
120
Lichtansteuerung HD AB 23
Always
Lichtfunktion C 23
Nicht aktiv
Lichtfunktion D 23
Nicht aktiv
Dimmwert CD 23
0
Dimming Direction CD 23
Maximize
Lichtfunktion E 23
Nicht aktiv
Lichtfunktion F 23
Nicht aktiv
Dimmwert EF 23
Dimming Direction EF 23
Maximize
Lichtfunktion G 23
Nicht aktiv
Lichtfunktion H 23
Nicht aktiv
Dimmwert GH 23
0
Dimming Direction GH 23
Maximize
|
|
|
|
Post by dv52 (Australia) on Oct 7, 2022 23:10:34 GMT
I have no idea what was intended with the settings in these 3 x Leutche-sets!! When Leuchte 35 LED Warnblinktaster C48 is activated (it's not always active), the Leuchte-set operates the LED in the hazard warning light switch. Does the button illuminate when it's pressed on this car? ONLY IF NOT (emphasis on these words), try this: Leuchte 35 LED Warnblinktaster C48 Lasttyp 15 > 41 - LED Kleinleistung Lampendefektbitposition 15 > 0 Fehlerort mittleres Byte DTC-DFCC 15 > 63 Lichtfunktion A 15 > Warnblinktaster_Suchbeleuchtung Lichtfunktion B 15 > not active Dimmwert AB 15 > 100 Lichtansteuerung HD AB 15 > Always Lichtfunktion C 15 > not active Lichtfunktion D 15 > not active Dimmwert CD 15 > 0 Dimming Direction CD 15 > maximize Lichtfunktion E 15 > not active Lichtfunktion F 15 > not active Dimmwert EF 15 > 0 Dimming Direction EF 15 > maximize Lichtfunktion G 15 > not active Lichtfunktion H 15 > not active Dimmwert GH 15 > 0 Dimming Direction GH 15 > maximize
Again for repeat emphasis - DON'T make these changes if the the hazard warning light switch works OK because it will cause further errors to an already very sick hex09 module! Instead, do this: Lasttyp 15 > nicht aktiv
Leuchte27NSL RC6 and Leuchte23SL HLC10 are a complete nonsense (to me at least)!!!
Both on NAR and RoW model mk7/7.5, Leuchte27NSL RC6 is NOT activated when the car is fitted with incandescent tail-lights and Leuchte23SL HLC10 is normally dedicated to the rear left inside lamp - which is usually operated as a Parking Light.
Do the 2 x inside lamps on the tail-light operate as Parking Lights (Position lights)? Please answer this question.
As I have already said- my guess is that these tail-lights have been retrofitted after the car was built. This means that someone has had to reconcile the wiring loom for the tail-lights on a NAR built model with the wiring requirements for EU tail-lights (which are not the same)
Did you retrofit the tail-lights, or did you arrange for this retrofit? Please answer this question. If so, then you would have needed to also install a cross-wiring harness, or you would have needed to install extra wires from the new tail lights to the hex09 module (or you would have needed to do parts of both options and re-pin the positions of the connectors on the tail-lights). How was the retrofit of the new tail-lights done? Please answer this question
Again, I am at a complete loss to understand the programming - but my wild guess is that someone has attempted to use these 2 x Leuchte-sets to operate the rear turn-signal lamps (which are not present on NAR incandescent fittings). If I'm correct, the attempt has been incorrectly implemented and if I'm not correct, then I just don't know!!
Don
|
|
grbac
Junior Member
Posts: 51
|
Post by grbac on Oct 8, 2022 14:48:57 GMT
Hi Don, so first thing I noticed is that there is no "Warnblinktaster_Suchbeleuchtung" option in Leuchte 35 LED Warnblinktaster C48 (the button isn't blinking when you press it). The parking/position lights work like they should ( imgur.com/a/xqFqshm ) you can see it on the right ones better To answer the last question, if I retrofitted them? No, I bought the car like this, so I don't really have an answer if they were or weren't retrofitted. |
|
|
|
Post by dv52 (Australia) on Oct 8, 2022 22:20:45 GMT
so first thing I noticed is that there is no "Warnblinktaster_Suchbeleuchtung" option in Leuchte 35 LED Warnblinktaster C48 (the button isn't blinking when you press it). OK - then try:
- Lichtfunktion A 15 > nicht_definiert_4C
The parking/position lights work like they should ( imgur.com/a/xqFqshm ) you can see it on the right ones better Yes, I see. It's not clear on your picture - do the inner lamps illuminate when the Position-lights are active at a lower intensity than the outer lamps when the Brakes are pressed?
With my suggested changes which you implemented for the outer-lights - both the inner and outer lights should have the same illumination intensity when the position lights are active (and the brakes are NOT pressed). This is a safety arrangement so as not to confuse the driver's intention for other cars at the rear
To answer the last question, if I retrofitted them? No, I bought the car like this, so I don't really have an answer if they were or weren't retrofitted. That's not good news because you can't provide any further information regarding how the car's wiring was changed when the tail-lights were retro fitted!
hmm....... how to proceed??
I guess the ONLY way forward is simply to accept my earlier guess that the 2 x Leuchte-sets in question were meant to operate the turn-signal lamps and to fix the incorrect Leuchte-programming (I think).
So, entirely based on this guess - try this:
for Leuchte27NSL RC6 and Leuchte23SL HLC10 - Lasttyp> 12 - Blinkleuchten
- Dimmwert AB > 100
|
|
grbac
Junior Member
Posts: 51
|
Post by grbac on Oct 17, 2022 7:33:48 GMT
Hi Don,
sorry for late response (was positive for covid).
So now that I changed the
Leuchte 35 LED Warnblinktaster C48
to
Lichtfunktion A 15 > nicht_definiert_4C
and now the button lighs up when I open the car door and it stays lit up all the time when ignition is ON and blinks when pressed. Is it supposed to be ON all the time?
The Fault lighting is still there sadly.
All the blink lights work as they should, at least from what I can see.
I don't see any problem with the brake lights or the position ones.
The reverse lights work normally too although I willl turn off the fog light that turns on when in R.
I really don't find any other "irregular" thing on it, but will keep looking and playing with it.
|
|
|
|
Post by dv52 (Australia) on Oct 17, 2022 21:32:54 GMT
Hi Don, sorry for late response (was positive for covid). So now that I changed the Leuchte 35 LED Warnblinktaster C48 to Lichtfunktion A 15 > nicht_definiert_4C and now the button lighs up when I open the car door and it stays lit up all the time when ignition is ON and blinks when pressed. Is it supposed to be ON all the time? No it isn't!! - post up screenshots of Leuchte 35 LED Warnblinktaster C48 -please |
|
grbac
Junior Member
Posts: 51
|
Post by grbac on Oct 18, 2022 6:55:34 GMT
Hi, so here is the screenshot of the adaptation C48 imgur.com/a/6wxWrstI saw in a couple of videos that other people have the light turned all all the time too (it turns on when unlocking the car, while driving...and turns off when they lock it), same thing with me. |
|
|
|
Post by dv52 (Australia) on Oct 18, 2022 22:33:43 GMT
grbac : OK - I suspect that we might have an understanding problem - caused in the main by my perfunctory previous response "No" and also likely due to my thick Australian accent (albeit I don't believe that I have an accent!!  )
The Leuchte- command nicht_definiert_4C works like this: On ignition switch-on, the LED back lighting in the hazard switch will illuminate in a much dimmed mode (indicating the position of the button, rather than the operation of the button) - when the hazard button is pressed, the LED should fully illuminate in blink mode.
From your words, I suspect that this is what happens - which is correct!!
Don
|
|
grbac
Junior Member
Posts: 51
|
Post by grbac on Oct 19, 2022 18:13:07 GMT
Oh, ok, then its all good. One more question, are these two adaptations set up as rhey should be? HRA65 ( imgur.com/a/QbxzyF6 ) HLC10 ( imgur.com/a/LBukYGo ) aren't those two supposed to be HRA65 the rear right light and HLC10 the rear left light? If so, aren't they supposed to be the same "Lasttyp"? Sorry if I'm wrong, just trying to find whers the fault coming from.(and learn a little) |
|
|
|
Post by dv52 (Australia) on Oct 19, 2022 21:52:05 GMT
On a RoW mk7 with OEM (meaning factory built) incandescent tail-lights, yes the 2 x Leuchte-sets in question are factory assigned as you say.
BUT, as evidence by the length of this thread - your car is very far from having OEM assigned Leuchte-sets for the rear lamps!!
Don
|
|
|
|
Post by dv52 (Australia) on Oct 23, 2022 21:37:14 GMT
grbac : arrhh.......... you are back - my best customer on this forum (I'm clearly not charging enough )!! First - I can't access your adaptation channel data. When I try, it says that I must ask permission and I refuse to sign into anything as a condition of extracting information!!
But, the Leuchte command for the right-side turn signal is Blinken rechts Hellphase. From your previous data, you posted this
--------------------------------------
Leuchte23SL HLC10
--------------------------------------
Lasttyp 23
38 LED Blinkleuchten (18 - 2* 5W)
Lampendefektbitposition 23
A
Fehlerort mittleres Byte DTC-DFCC 23
29
Lichtfunktion A 23
Blinken rechts Hellphase
Lichtfunktion B 23
Nicht aktiv
Dimmwert AB 23
127 (120)
Lichtansteuerung HD AB 23
Always
Lichtfunktion C 23
Nicht aktiv
Lichtfunktion D 23
Nicht aktiv
Dimmwert CD 23
0
Dimming Direction CD 23
Maximize
Lichtfunktion E 23
Nicht aktiv
Lichtfunktion F 23
Nicht aktiv
Dimmwert EF 23
Dimming Direction EF 23
Maximize
Lichtfunktion G 23
Nicht aktiv
Lichtfunktion H 23
Nicht aktiv
Dimmwert GH 23
0
Dimming Direction GH 23
Maximize
Now, as I have said numerous times in our long discourse in this long thread - there is much about the coding on your hex09 module that I don't understand. The changes that I have already suggested to this Leuchte-set are in bold above - the bracket value is the original setting in your post.
So, and to repeat my previous advice, Leuchte23SL HLC10 is not usually factory assigned to the right-side turn-signal lamp. However, clearly someone has changed the normal OEM allocation of Leuchte-sets on your car. Again I repeat my previous advice that I suspect that this was done because whoever retro-fitted your LED tails needed to find extra wires in the loom - but I'm guessing
All that can suggest is that you confirm the values in my listing above!
For the Scandanavian DRL tweak, the adaptation channel for your version hex09 module is: - Außenlicht_Front-Tagfahrlicht-Dauerfahrlicht aktiviert zusaetzlich Standlicht
However, this tweak illuminates the Parking Light lamps on the tail-lights during daytime - so it works by energizing the OEM wires that are factory assigned to the Parking Light function on the tail-light fittings. Again on your car - the wires that are assigned to the Parking Light function on the tail-light fittings are NOT the OEM assignment.
Not a problem attempting this tweak - but it may not work as you expect
Don
|
|
grbac
Junior Member
Posts: 51
|
Post by grbac on Oct 24, 2022 16:39:49 GMT
Thank you again for keeping up with my nonsense al this time. Sorry for the link I added a new one without the need of signing in. Ok, I did the Leuchte HLC10 adaptation, but there is something triggering the left and right stop light while turning on left turn signal (right turn signal works fine). When I lock or unlock the car the turn signals blink twice (as they should), but the outer brake lights do as well, although that doesn't bother me, actually looks nice. Video of left turn signal: imgur.com/a/kd9flZkCurrent adaptation backup: www.dropbox.com/s/ls3tq27wae6pdg7/OBDeleven_Log.txt?dl=0I saw tha some time ago, you helped another guy with the same lights as mine ( forum.obdeleven.com/thread/1962/request-golf-sportwagen-light-coding ) Should I try to copy the adaptation he provided (the "Ver 1 synchronously flash") and then edit the ones you mentioned and see what happends? If nothing helps, I guess I'll have to go to a VW dealership to "factory reset" the adaptations or to do whatevers is needed to make it work right. |
|
|
|
Post by dv52 (Australia) on Oct 24, 2022 20:39:20 GMT
grbac : I've looked at your latest "adaptation backup" and I note that there have been further changes made that I can best describe as being "innovative" (and I'm selecting my words with great care)!! There's clearly lots of free-thinking coding going-on here
In respect of your latest problem with the left turn-signal and according to your latest backup, the Leuchte-command for this function (i.e. Blinken links Hellphase) now appears on 3 x separate Leuchte-sets as follows: - Leuchte18BLK HLA60
- Leuchte19BLK HRC31
- Leuchte27NSL RC6
Each of these Leuchte-sets controls an individual wire on the hex09 module and each of these wires (usually) is terminated onto a lamp base on the tail-light fittings.
Of course there is only ONE lamp in the tail lights that is meant to operate as the left turn-signal, so the coding is interesting at best- but it's problematic from a practical perspective
I think that we need to reset - and most importantly, we need to put a halt to any additional modifications to the hex09 module so that we have a stable adaptation channel database - please! Please make a NEW backup of the hex09 module and post-up AND please don't make any further mods
In respect of the latest problem with the left/right stop lights - I suspect that this is a relic of the original "Yankee" coding on the car . The hex09 module has the following adaptation channel: - Aussenlicht_Heck - Bremslicht ist auch Blinklicht
In Google-English, this translates as "Outside rear light - Brake light is also a flashing light". On RoW modules, the factory value for this channel is no - on Yankee cars the default setting is yes. Your module value is yes.
Don |
|
grbac
Junior Member
Posts: 51
|
Post by grbac on Oct 26, 2022 16:15:44 GMT
Adaptations backup www.dropbox.com/s/0hjop8d9co8jcd8/OBDeleven_Log%20hex9%20backup.txt?dl=0This is the result of current adaptations (video) imgur.com/a/BhpzZHjWhen car is ON and lights are ON too, the tail lights (brake/park) work fine, just for the right turn signal, which stays ON all the time whatever you do. When I unlock the car, the left side blinks 2x normally (blinker/light above), but on the right side only the the light above blinks 2x, the blinker doesn't do anything, stays OFF. When Hazard button pressed = look at the video When left turn signal ON = left signal and light above it blink as it should When right turn signal ON = right signal stays ON even without turning on right turn signal lever all the time and light above it blinks as it should. |
|
|
|
Post by dv52 (Australia) on Oct 26, 2022 21:23:32 GMT
hmm.......... I totally lost with absolutely no understanding of what's happen here!! The latest backup settings make no sense to me - at all!! What country is this car driven in? What country was this car manufactured for? Your position that when the hazard lights are turned-on. "the left signal and light above it blink as it should" is not as I understand how this function operates on cars sold in other world markets (and it's certainly NOT as MQB platform cars operate for RoW models down here) - which is like this: - For RoW models - on both car-sides, the front and rear turn-signal lamps (only) blink when the hazard light function operate
- For NAR models - on both car sides, the front turn-signal lamps and the rear outer lamps (which work as both Brake and turn/signal lights) blink when the hazard light function operates. Of course, these Yankee models don't have separate rear turn-signal lamps, so "the left/right signal" can't blink as hazard lights on NAR models!!!
From a practical perspective, the hazard light function simply flashes ANY lamp that is programmed with the "Blnken Rechts/Links Hellphase" Leuchte-command. As I read your latest Backup data, you have these Leuchte-commands programmed into multiple lamps (read Leuchte-sets) on the taillights, so I suspect this is reason for your observations. But I repeat - I don't understand !!!
Don
|
|
grbac
Junior Member
Posts: 51
|
Post by grbac on Oct 27, 2022 23:04:31 GMT
So with a little bit of tinkering and looking in my first backup ever made with OBDEleven I found out that my Leuchte23SL HLC10 - Lichtfunktion A 23 was set to Blinken recht Hellphase instead of Standlicht allgemein (Schlusslicht...) so I changed that back to that and now my right turn signal works as it should, but is still wierd as hell, because as far as I know, Leuchte23SL should be the left inner lamp set. Now that it works, I'm going to leave it as it is. I'm going to check/compare everything else in Central Electronics CU without changing nothing to see if I can find any other reason for the lighting fault, if not, I'm returning back to the tail lights and maybe have a look at the connections to se if somebody did something with them.
|
|
mk7
New Member
Posts: 14
|
Post by mk7 on Oct 28, 2022 15:19:30 GMT
Hey Don, I have read so many of your posts over the past few months I feel like I know you!! I have done all that I can at this point and am at a wall. Here's a quick synopsis: - MK7 Golf R
- On Bags
- DCC Deleted
- Direct Wired Level Sensor/Turned to 1 Sensor
- Still Have AFS light/No Basic Settings Issue
When you direct wire the Rear Level Sensor, do you splice in to the rear sensor and keep it connected to the DCC module? Or do you cut the Black/Brown/Blue lines at the harness and direct wire them to the AFS module breaking the connection to the DCC module?
Here are the codes I am getting PRE-Clearing Faults:
17 Dashboard
System description: KOMBI
Software number: 5G1920858B
Software version: 8311
Hardware number: 5G1920858B
Hardware version: 304
ODX name: EV_DashBoardVDDMQBAB
ODX version: 009051
Long coding: 0B2D081A6688CF0502887B0B5400000000000000
Trouble codes:
U101400 - Control module incorrectly coded
static
_________________________________________
55 Headlight Regulation
System description: AFS-ECU
Software number: 7P6907357D
Software version: 0090
Hardware number: 7P6907357A
Hardware version: H07
Serial number: --------------
ODX name: EV_HeadlRegulVWAFSMQB
ODX version: 001120
Long coding: 026A000109000000
Trouble codes:
C107E54 - Headlight No basic setting
static
U10BA00 - Local data bus No communication
static
_________________________________________
After I Scan and Clear Faults I only have 55 Headlight Regulation:
55 Headlight Regulation
System description: AFS-ECU
Software number: 7P6907357D
Software version: 0090
Hardware number: 7P6907357A
Hardware version: H07
Serial number: --------------
ODX name: EV_HeadlRegulVWAFSMQB
ODX version: 001120
Long coding: 022A00010B000400
Trouble codes:
C107E54 - Headlight No basic setting
static
U10BA00 - Local data bus No communication
static
|
|
|
|
Post by dv52 (Australia) on Oct 28, 2022 21:43:45 GMT
Hey Don, I have read so many of your posts over the past few months I feel like I know you!! Wow - I'm honored, but allow me to suggest that it's a futile and ultimately it's not a worthwhile pursuit because there ain't nothing special about dv52 (Australia) !!! Anyhow, just to add a face to the sad personality - here's a pic of me with my current life time partner (think about it) at a recent picnic: I'm the good-looking guy on the left !! When you direct wire the Rear Level Sensor, do you splice in to the rear sensor and keep it connected to the DCC module? Or do you cut the Black/Brown/Blue lines at the harness and direct wire them to the AFS module breaking the connection to the DCC module? hmm........ I have no idea what changes that you have made. However, on a RoW mk7 without DCC but with a hex 55 module installed, it is normal (albeit it isn't necessary) to connect 1 or 2 x level sensors directly to the module.
Of course it depends on the particular part number used, but the way that the module knows how many sensors to operate is normally via the status of the software switches on the long-code string. Alas, I don't have much information about these software switches on a hex55 module in my MQB database- but you should be able to view this data via OBD11 on your car
Don
|
|
mk7
New Member
Posts: 14
|
Post by mk7 on Oct 28, 2022 22:27:13 GMT
Hahahaha looking good!!! So in order to not have the suspension fault because I have airbags, I followed the below thread: www.vwvortex.com/threads/dcc-delete-on-nar-2015-golf-r.9493140/My vehicle has DCC and AFS already; however with the bags it throws codes. So I followed the above steps to remove DCC from my vehicle. The last part I cannot get is for it to read off the leveling sensor and I have "No Basic Settings" in the Headlight (55) Module with the following trouble codes: "C107E54 - Headlight No basic setting static U10BA00 - Local data bus No communication static" All I want to do is either make it work properly as I hard wired the rear leveling sensor to the AFS module as instructed in the link above OR anything to just get the AFS Error light to turn off. Like I have TPMS turned off. Is there anything I can post to help illustrate my issues? TY!! |
|
|
|
Post by dv52 (Australia) on Oct 28, 2022 23:36:43 GMT
mk7 : hmm........ OK - so your link says (only relevant parts included): b. "55-Headlight Range"
c. "Coding - 07"
f. Check Bit 3 of Byte 1 (source_leveling_info - 0=CAN 1=SENSOR)
g. Uncheck Bit 1 of Byte 2 (lwr_sensors 0=1_sensor / 1=2_sensors) (single or dual axle level sensing)
Maybe check that these changes have been made correctly (no offense intended). Or better still, post-up a copy of the long-code string on the hex55 module (again, no offense intended). In fact, even more better-er - post up full details of the hex55 module (so we are clear what module is installed on your car)
Also try the following procedure on the hex55 module (it's a 2-part procedure) - albeit, I'm not sure that the module will allow it:
Important: Make sure the car is fully settled on its suspension and that the vehicle is on level ground
Procedure 1
- Select hex 55 - Xenon Range module
- Select Basic Settings
- Select Basic headlamp setting and start the procedure
- This is where you would adjust the headlights using their manual adjusting screws as referenced against a suitable aiming target - but in your case go to the next step
- Wait a period of time (suggest 10 seconds)- then stop the procedure
Procedure 2 (still in Basic Settings)
- Select Acknowledge basic setting and start the procedure
- The reference settings from Procedure 1 above should now be "recorded" in the module
- Wait a period of time (suggest 3 seconds)- then stop the procedure
- Back-out of the module, clear any error codes and exit OBD11 software (don't forget to disconnect the OBD11 dongle)
Don
|
|
mk7
New Member
Posts: 14
|
Post by mk7 on Oct 29, 2022 1:45:27 GMT
In fact, even more better-er - post up full details of the hex55 module (so we are clear what module is installed on your car)
How do I do this? Pardon my ignorance. Is this what you're looking for? Control unit: 55 Headlight Regulation System description: AFS-ECU Software number: 7P6907357D Software version: 0090 Hardware number: 7P6907357A Hardware version: H07 Serial number: -------------- ODX name: EV_HeadlRegulVWAFSMQB ODX version: 001120 Backup name: Stock Long coding: 022202010B000400 Subsystems: Subsystem: LeiMo links Long coding: 2E0000 |
|
|
|
Post by dv52 (Australia) on Oct 29, 2022 12:05:51 GMT
Excellent - you are clearly a quick learner!!! OK, here's a copy of the long-code string from your hex55 module rearranged to be more readable:
Byte Hex Binary
00 02 00000010
01 22 00100010
02 02 00000010
03 01 00000001
04 0B 00001011
05 00 00000000
06 04 00000100
07 00 00000000If you are not aware, the Binary value is read from right-to-left. This means that Bit 0 is the right most digit in the Binary value and the left most digit is Bit 7
And again for reference, here's a synopsis of the coding instructions from your link:
b. "55-Headlight Range"
c. "Coding - 07"
f. Check Bit 3 of Byte 1 (source_leveling_info - 0=CAN 1=SENSOR)
g. Uncheck Bit 1 of Byte 2 (lwr_sensors 0=1_sensor / 1=2_sensors) (single or dual axle level sensing)
So - look at your Byte 1 Binary value and count 4 x places from the right (remember Bit 0 is the right-most digit). The 4th digit from the right is Bit 3 and its value is 0! This Bit should be 1 for a directly connected level sensor - according to your link instructions
Next, investigate your Byte 2 value. Again, count 2 x places from the right to find Bit 1 in the Binary value. Your Bit 1 =1 - it should be 0 for 1 x sensor
Don
|
|
mk7
New Member
Posts: 14
|
Post by mk7 on Oct 29, 2022 17:56:05 GMT
Excellent - you are clearly a quick learner!!! OK, here's a copy of the long-code string from your hex55 module rearranged to be more readable:
Byte Hex Binary
00 02 00000010
01 22 00100010
02 02 00000010
03 01 00000001
04 0B 00001011
05 00 00000000
06 04 00000100
07 00 00000000
Ok, so my mistake, the info I posted was the "Stock" Backup info. And I am not sure how you pulled the code list from what I posted above.... So here is the "Current" error code Backup: Control unit: 55 Headlight Regulation System description: AFS-ECU Software number: 7P6907357D Software version: 0090 Hardware number: 7P6907357A Hardware version: H07 Serial number: -------------- ODX name: EV_HeadlRegulVWAFSMQB ODX version: 001120 Backup name: Error Backup Long coding:
022E00010B000400
Here is what I was able to come up with, not sure if it is correct: Long Coding STOCK 022202010B000400Byte Hex Binary 00 02 00000010 01 22 0010 0010 02 02 000000 10 03 01 00000001 04 0B 00001011 05 00 00000000 06 04 00000100 07 00 00000000 Long Coding NEW 022E00010B000400Byte Hex Binary 00 02 00000010 01 2E 0010 1110 02 00 000000 00 03 01 00000001 04 0B 00001011 05 00 00000000 06 04 00000100 07 00 00000000 From what I can see the updates are correct but I need to investigate the change from Bit 4 of Byte 1 changing from 0 to 1 as well. Should the updated long code be 022600010B000400? |
|
mk7
New Member
Posts: 14
|
Post by mk7 on Oct 29, 2022 20:25:19 GMT
Update, it doesn't matter what I do, I still have these two errors:
"C107E54 - Headlight No basic setting
static
U10BA00 - Local data bus No communication
static"
|
|
|
|
Post by dv52 (Australia) on Oct 29, 2022 20:51:14 GMT
Almost correct - but not quite (no offense intended, but I suspect that you may have forgotten about Bit 0 position for the Byte 1 change- common mistake)!!
If you are now saying that that before the change, the long-code string on the hex55 module was:
Then the new value based on the link instructions in your previous post (and assuming that you have re-wired 1 x sensor directly onto the hex55 module) should be: To help explain why this is so, I include the table below (note the positions of Byte1, Bit3 & Byte 2, Bit 1): Byte HEX <----------------------------BITS---------------------->
7 6 5 4 3 2 1 0
00 02 0 0 0 0 0 0 1 0
01 2A 0 0 1 0 1 0 1 0
02 00 0 0 0 0 0 0 0 0
03 01 0 0 0 0 0 0 0 1
04 0B 0 0 0 0 1 0 1 1
05 00 0 0 0 0 0 0 0 0
06 04 0 0 0 0 0 1 0 0
07 00 0 0 0 0 0 0 0 0
Don |
|
mk7
New Member
Posts: 14
|
Post by mk7 on Oct 29, 2022 21:11:40 GMT
I did direct wire the rear sensor. Question being do I splice into the rear sensor wires or do I cut them so they are no longer connected to the DCC module? I have updated the code, scanned, cleared and have the same errors  "55 Headlight Regulation System description: AFS-ECU Software number: 7P6907357D Software version: 0090 Hardware number: 7P6907357A Hardware version: H07 Serial number: -------------- ODX name: EV_HeadlRegulVWAFSMQB ODX version: 001120 Long coding: 022A00010B000400 Trouble codes: C107E54 - Headlight No basic setting static U10BA00 - Local data bus No communication static"
|
|
mk7
New Member
Posts: 14
|
Post by mk7 on Oct 29, 2022 21:14:49 GMT
This is the pre clear codes log:
____________________________________________________________
"09 Central Electrics
System description: BCM MQBAB HNA
Software number: 5Q0937085BL
Software version: 0175
Hardware number: 5Q0937085AF
Hardware version: H24
Serial number: 01061621400392
ODX name: EV_BCMMQB
ODX version: 015001
Long coding: 00011B46C041A2E169E44000091C07201800000000000000000000000000
Subsystems:
System description: WWS 160731
Software version: 0551
Hardware version: 043
Serial number: 160804194142
Long coding: 0E4DDD
System description: RLHS
Software version: 0105
Hardware version: 042
Serial number: S5Y16M08D25H00M25S18
Long coding: 00A8DD
Trouble codes:
U112100 - Databus missing message
static
Date: 2022-10-29 14:59:50
Mileage: 45298 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 157
Terminal 15 status: On
Terminal 50 status: Off
Voltage: 12.3 V
Outside air temperature: 15.0 °C
Status Bremslichtschalter (HW): Off
Status Bremslichtschalter (CAN): Off
Off: operated
Parking light: not activated
Automatic high beam assist: not activated
Low beam: not activated
Parking light left: not activated
Parking light right: not activated
Letzte Weckursache/ Werte [00;2E]: keine Störschutzursache
CAN-Bus_aktiv: On
---------------------------------------------------------------
55 Headlight Regulation
System description: AFS-ECU
Software number: 7P6907357D
Software version: 0090
Hardware number: 7P6907357A
Hardware version: H07
Serial number: --------------
ODX name: EV_HeadlRegulVWAFSMQB
ODX version: 001120
Long coding: 022A00010B000400
Trouble codes:
C1081F0 - Left headlamp power output stage not coded
static
Date: 2022-10-29 15:07:05
Mileage: 45298 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 157
C1082F0 - Right headlamp power output stage not coded
static
Date: 2022-10-29 15:07:05
Mileage: 45298 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 157
C107E54 - Headlight No basic setting
static
Date: 2022-10-29 15:04:31
Mileage: 45298 km
Priority: 1
Malfunction frequency counter: 1
Unlearning counter: 157
U10BA00 - Local data bus No communication
static
Date: 2022-10-29 15:04:30
Mileage: 45298 km
Priority: 2
Malfunction frequency counter: 2
Unlearning counter: 157
---------------------------------------------------------------
5F Multimedia
System description: MU-S-NS-US
Software number: 3Q0035880A
Software version: 0360
Hardware number: 3Q0035880A
Hardware version: H30
Serial number: VWZAZ2S0639499
ODX name: EV_MUStd4CTSAT
ODX version: 001022
Long coding: 02730002000000005122000200180800DF0207F401208105C6
Subsystems:
System description: ABT_Std-2_Nav
Software version: 1031
Hardware version: H53
Serial number: VWZ8Z9SJX007HV
System description: NAR 2016/17
Software version: 0445
Hardware version: ---
Serial number: --------------------
Trouble codes:
B11CF53 - Tuner for satellite radio Deactivated
static
Date: 2022-10-29 14:56:09
Mileage: 45298 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 157
Dynamic environmental data: 0286804FF70000000000000000
U111100 - Function limitation due to missing message
static
Date: 2022-10-29 14:13:11
Mileage: 45298 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 157
Dynamic environmental data: 028676184402
|
|
) 
