usse
New Member
Posts: 12
|
Post by usse on Sept 3, 2022 21:58:21 GMT
Hello everybody,
I recently replaced the original headlight switch of my audi that doesn't have the position "Auto" with a new one that have now the position "Auto". After replacing it and so an error in the dashboard but I manager to solve it using obdeleven by activating a bit related to the sensor that is on the switch.
Also I added from obdeleven app two features: Fog light ON as DRL and scandinavean mode
The problem I have now that I noticed yesterday is that at night as the position is in of switch is "Auto" I noticed that the light of my car is not good and when I trying the High beam it doesn't work. I stopped the car and I noticed that the light are still in the same configuration as the configuration of the day (DRL) so no low beam is ON at night even if the switch is in "Auto" position, so it is like the Auto position is fix and not adapting by detecting the night and turning the low beam also. So to turn low beam I was obliged to turn the position from "Auto" to "High beam"
Any idea how to fix this issue ?
|
|
|
|
Post by dv52 (Australia) on Sept 4, 2022 5:31:15 GMT
usse : hmm...I assume that "sensor that is on the switch" means that you retrofitted a non OEM sensor - meaning NOT the Audi sensor that's fitted to the windscreen glass (likely you have the Chinese built button style sensor and the Chinese rotary light switch) Is this assumption correct? So, maybe check the coding values on the central electrics module as requested below and report your findings: - You say the you activated "a bit related to the sensor that is on the switch". Which Bit was this exactly?
- What is the value of Byte 06 on the long-code string?
- What is the value of Byte 07 on the long code string
- What is the value of the channel Daytime running lights-Tagfahrlicht Dauerfahrlicht bei Handbremse abschalten?
Don
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 4, 2022 10:20:12 GMT
Hi Dv52,
Thank you for your prompt reply.
Yes I confirm that the I retrofitted a non OEM sensor cause I got it via amazon, it is likely chinese.
I'll try to get all the information you need and get back to you as soon as possible
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 5, 2022 13:54:48 GMT
Hi Dv52,
In answer to your questions:
You say the you activated "a bit related to the sensor that is on the switch". Which Bit was this exactly?
Under "Central Electrics" long coding, I switched the "LDS_mit_AFL" from No to YES
What is the value of Byte 06 on the long-code string?
When I open long coding I don't see bytes, I see only names, supposing we start by byte 0, if the byte 6 is "UGDO", then its value is "not installed"
What is the value of Byte 07 on the long code string
if the byte 7 is "Schiebedachmodul_MD_1", then its value is "not installed
What is the value of the channel Daytime running lights-Tagfahrlicht Dauerfahrlicht bei Handbremse abschalten?
The value of "Tagfahrlicht Dauerfahrlicht bei Handbremse abschalten" is not active
|
|
|
|
Post by dv52 (Australia) on Sept 6, 2022 0:20:19 GMT
What is the value of Byte 06 on the long-code string? When I open long coding I don't see bytes, I see only names.................. hmm...... I think that it might be useful to go back to basics!!
The long-code string on ALL UDS modules (being the modules used on your Audi A3 8V) are reported in hexadecimal numbers (look it up if you are not familiar with Hex). OBD11 has a separate screen that translates these hex numbers into words - but users are able switch between words and hex numbers (I prefer hex numbers).
Maybe read OBD11 instructions for how to access long-code HERE and in particular, note screenshot #6
Don
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 6, 2022 9:26:56 GMT
Hi,
It's OK, I am familiar with hexadecimal numbers without any problem, I think my obdeleven by default doesn't show in hexadecimal, I thought they removed the hexadecimal part to make it easy to use.
I'll try to switch it to hexadecimal mode and get back to you with the results
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 6, 2022 11:55:45 GMT
These are the results
Byte 6:
bit 0 = 0 (light sensor = not installed)
bit 1 = 0
bit 2 = 0 (All-weather light = Not active)
bit 3 = 0 (Emergency assist = Not installed)
bit 4 = 0 (light control modul = Not active)
bit 5 = 1 (Xenon shutter = Installed)
bit 6 = 0
bit 7 = 0 (Brake light is also flashing light = not active)
Byte 7:
bit 0 = 1 (Search lighting = ...)
bit 1 = 0 (Search lighting = ...)
bit 2 = 1 (Light switch via LIN databus = installed)
bit 3 = 1 (Light switch with front fog lights = installed)
bit 4 = 1 (Light switch rear fog lights = installed)
bit 5 = 1 (Light switch with assistance driving light = installed)
bit 6 = 1 (Light switch with position lights = installed)
bit 7 = 1 (Humidity sensor = installed)
|
|
|
|
Post by dv52 (Australia) on Sept 7, 2022 0:00:34 GMT
Excellent - thanks! So - as you can see, Byte 6, Bit 0 tells the central electrics module that a light-sensor is installed. In truth, OBD11 is telling lies because it's actually the 2 x software switches on Bit 0 and Bit 1 that provide the full story to the hex09 module about the sensor (which in truth can be actually both a light and rain sensor) Because you are familiar with hex - I assume that you know that 2 x Bits mean that there are 4 x possible states (for Bit 0 and Bit 1).
In your car, the value for these Bits is hex00 - which decodes to sensor not installed. If you had installed the OEM sensor, the communication language between the sensor and the module would have been LIN (which is a single wire comms protocol). The value for these 2 x Bits that tells the hex09 module to start talking in LIN is hex02 which in Binary is:
I assume that your non-OEM sensor still uses LIN - I suggest that you try the settings above with your Chinese sensor
Don
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 7, 2022 8:09:22 GMT
Good, thank you for your explanation Don, I'll try to change the value from hex00 to hex02 and see the results.
Once done, I'll need to wait till the night to see if it works fine LoL.
I'll keep you informed
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 7, 2022 14:55:05 GMT
After changing the value of byte 6 from from hex00 to hex02 (bit 1 = 1) I have no on the Dashboard the error : Automatic headlights: malfunction
And after scan, I have one error in Central Electrics : Rain/light recognition sensor (Fault code U10F600)
Any idea ?
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 7, 2022 20:29:41 GMT
Also I noticed that at this moment of fault and switch at position "Auto" the lowbeam button was green even if it was the day not the night and in exterior the light of low/high beam was ON.
|
|
|
|
Post by dv52 (Australia) on Sept 7, 2022 23:03:43 GMT
usse : I'm not surprised - my suggestion was a guess given that I'm trying to understand how the non-OEM sensor operates. Now that you have tried asking the central electrics module to operate as if an OEM sensor is installed and this has resulted in the error message - my thinking is that the non OEM sensor doesn't talk to the hex 09 module. Instead, my conclusion is that the non-OEM sensor ONLY talks to the rotary light switch (which is called "LDS"). If I'm correct (and I may not be correct), it suggests that the problem is either in the interface between the LDS and the non OEM sensor, or in the sensor itself! I assume that the sensor is correctly located so that it can "see" ambient light levels. You don't have "to wait till to night to see if it works"- you can simulate night by simply covering the sensor and you can simulate daytime by shinning a torch onto the sensor (the OEM sensor has a time delay, so wait for a period of time when simulating light-levels)
Check that the pins on the senor connector are not bent, or pushed-in and then check that the connector is correctly located when plugged into the LDS.
Don
PS: why is Byte 7, Bit 7= 1? If you haven't installed an OEM sensor (which is where the humidity sensor is located on some OEM sensors) - how does the car have this sensor?
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 8, 2022 8:29:50 GMT
Hi Don,
OK, I'll check the pins and the connector, but I think that if there was issue of communication between the switch and the central, all the other button won't work but in this case all the position of the LDS work fine except the "Auto" position, may be the information sent by the sensor is not understod by the central or the central see an uncoherence in the configuration of the bits. It can bee like that ?
In response to your question, I don't know why the Byte 7, Bit 7= 1 I don't know if it is like that by default because I never change it, or may be because of my action days ago further to the first issue when I switched the "LDS_mit_AFL" from No to YES, may be "LDS_mit_AFL" is the Byte 7, Bit 7, is it possible ?
Do you think do non OEM sensor doesn't have the humidity sensor ? how can I check if it has or no ?
|
|
|
|
Post by dv52 (Australia) on Sept 8, 2022 23:28:05 GMT
Hi Don, OK, I'll check the pins and the connector, but I think that if there was issue of communication between the switch and the central, all the other button won't work but in this case all the position of the LDS work fine except the "Auto" position, may be the information sent by the sensor is not understood by the central or the central see an uncoherence in the configuration of the bits. It can bee like that ? hmm......... I don't know - you could be correct. The problem is (of course) that it's a non OEM sensor -so anything is possible!!. This is how the OEM sensor and LDS is wired:  I suggest that you check the native factory wiring on the LDS - does your car have 4 x wires as shown in my diagram? In response to your question, I don't know why the Byte 7, Bit 7= 1 I don't know if it is like that by default because I never change it, or may be because of my action days ago further to the first issue when I switched the "LDS_mit_AFL" from No to YES, may be "LDS_mit_AFL" is the Byte 7, Bit 7, is it possible ? Do you think do non OEM sensor doesn't have the humidity sensor ? how can I check if it has or no ? So, here's the thing - there are 2 x Humidity sensors on MQB platform cars like the Audi A3 8V; an "external" sensor and an "internal" sensor. The external sensor is connected to the Air Con module and it's located inside the outer air vent under the windscreen - so not part of the matters discussed here. The internal sensor is connected to the hex09 module and as I have already said, it's normally integrated into the OEM rain/light sensor (on some sensors).
If you select Live data option in OBD11 for the central electrics module and you use the search vector "humidity" - Internal Humidity sensor should be returned. Does the sensor reading show actual values? |
|
usse
New Member
Posts: 12
|
Post by usse on Sept 9, 2022 15:04:20 GMT
Hi Don,
I checked the pins on the senor connector and they are not bent, or pushed-in and the connector is correctly located when plugged into the LDS.
In response to your question:
I suggest that you check the native factory wiring on the LDS - does your car have 4 x wires as shown in my diagram?
=> Yes my car has 4 wires connected as follow:
Green/purple wire connected to pin 1 of the LDS
Grey/purple wire connected to pin 2 of the LDS
Brown wire connected to pin 3 of the LDS
Green wire connected to pin 4 of the LDS
If you select Live data option in OBD11 for the central electrics module and you use the search vector "humidity" - Internal Humidity sensor should be returned. Does the sensor reading show actual values?
==> When I select "Internal humidity sensor" in live data of central electrics, it gives the following values:
Dew point: 11.6 °C
Windshield temperature 11.6 °C
Sensor temperature 22.0 °C
Relative humidity 71.5%
Earlier you said "why is Byte 7, Bit 7= 1? If you haven't installed an OEM sensor (which is where the humidity sensor is located on some OEM sensors) - how does the car have this sensor?"
=> Do you think this bit 7 of Byte 7 should be 0 ? do you think I can give it a try by switching the value of this bit from 1 to 0 ?
|
|
|
|
Post by dv52 (Australia) on Sept 9, 2022 21:27:31 GMT
hmm........ you could try removing the tick from Bit 7 - but your readings suggest that the internal humidity sensor is installed
my hunch is that the non-OEM sensor is faulty
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 10, 2022 10:05:57 GMT
OK. I see, I give it a last try by removing the bit 7 to see.
When I did mu test I noticed that all positions of the LDS work fine, when I put the switch in positions "zero", "sidelights" or "lowbeam" there is no error on the dashboard. Once I put it in position "Auto" the error is displayed on the dashboard this means at this moment when the central ask the sensors to give some information while with the other positions the central doesn't need more information. May be in the position "Auto" at the moment when the central ask for humidity or light sensor values there is no response or one of them respond and the other n o or both doesn't respond.
Do you know which Byte and which bit for light sensor and which Byte and which bit for Humidity sensor ? so I can do some test by activating or deactivating and see. May be for each each sensor there are two bits one to tell the central if it is installed or no and one to tell the central if it is activated or no
Any idea ?
|
|
|
|
Post by dv52 (Australia) on Sept 10, 2022 22:50:45 GMT
Of course you are free to continue to pursue this fault as being a coding problem - but I suspect that it's an equipment problem. The answer to your Byte/Bit question has already been discussed - re-read my replies above.
Don
|
|
usse
New Member
Posts: 12
|
Post by usse on Sept 11, 2022 14:17:02 GMT
OK. Thank you for all your replies
|
|
