|
|
Post by cbaldan on Feb 24, 2020 10:07:56 GMT
Hello. I need help to fix my headlights back to original. Last Friday I received my brand new OBDeleven PRO and started playing with it. Many successes, I got too happy monkeying around and then something happened. My ride is a 2016 Audi A3 S-Line 1.8, with Xenon headlights. While in Headlight Regulation module, I set Highway Lights to active and applied. It said "Coding accepted", but it turned itself immediately to false. I panicked a little, then, one second later I heard the dashboard ding with the infamous error: - Headlight range control: system fault!
I froze for a bit, but I'll skip the description of all my terror. After much research, I learned here in the forum that I could fix that error by recalibrating the headlights using the Basic Settings menu. I did fix the dashboard error and after cleaning the fault it doesn't come back. But after that I noticed that everytime I turn the car on I can hear the headlights aim motor doing the self test but it's trying to go too far, yet, no error code. The issue is just like this guy: I took a full backup before playing the car, the long code matches, but not Advanced identification nor live data. Before
- Advanced identification: 2
2 - Live data: 3
After- Advanced identification: 38
- Live data: 30
I got a feeling that if I can return those values to the original it will be fixed. Anyone can help? Thanks! Attachments:
|
|
|
|
Post by dv52 (Australia) on Feb 24, 2020 21:32:30 GMT
Hello. I need help to fix my headlights back to original. Last Friday I received my brand new OBDeleven PRO and started playing with it. Many successes, I got too happy monkeying around and then something happened. My ride is a 2016 Audi A3 S-Line 1.8, with Xenon headlights. While in Headlight Regulation module, I set Highway Lights to active and applied. It said "Coding accepted", but it turned itself immediately to false. I panicked a little, then, one second later I heard the dashboard ding with the infamous error: - Headlight range control: system fault!
I froze for a bit, but I'll skip the description of all my terror. After much research, I learned here in the forum that I could fix that error by recalibrating the headlights using the Basic Settings menu. I did fix the dashboard error and after cleaning the fault it doesn't come back. I got a feeling that if I can return those values to the original it will be fixed. Anyone can help? Thanks! I'm not sure how you completed the basic setting stuff - but you need to run 2 x separate procedures in the hex55 module like this: Make sure the car is on level ground and that the suspension is settled
Procedure 1
- Select Xenon range control module @ address hex55
- 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 3 seconds)- then stop the procedure
Procedure 2 (still in Basic settings in hex55 module)
- 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
|
|
|
|
Post by cbaldan on Feb 26, 2020 16:22:47 GMT
Thanks for the quick reply.
I’m currently on a business trip and I don’t have the car. I’ll try that once I’m back.
Anyway, I did realize I had to go through 2 steps to recalibrate and acknowledge it - that post with the steps I followed said so too.
But, like I said, I never paid attention to the startup procedure of the headlights before I messed with it, so I don’t know if that is normal and expected.
It doesn’t sound too normal to me, but, you know, the startup procedure is a self check, I’d expect it to throw a faulty code if it detected any issues.
|
|
|
|
Post by cbaldan on Mar 14, 2020 23:14:34 GMT
So, I assume that is normal headlight behavior.
I've done some more coding and I kept checking the headlights for faults, but none came up for weeks after I did the calibration steps.
I'm convinced that noise was always there but I just never paid attention to it before.
|
|
|
|
Post by tiggyiggyiggy on Jun 22, 2020 2:51:01 GMT
Old thread, but does anyone know what to do if the above suggestions don't work? I have tried to program the basic settings, but it keeps coming up with an error (in OBDElevel PRO) error (13) Function cannot be performed, mess. length or format incorrect Any help would be much appreciated, as this is driving me crazy. I'm presuming that the error is due to coding rather than a blown bulb, as it only came up after I had been playing around with long coding, and I can't seem to get rid of it, even after re-setting everything I changed.  |
|
|
|
Post by tiggyiggyiggy on Jun 26, 2020 8:59:59 GMT
Just thought I would update this post in case someone else gets themselves in to the same trouble I did above, as it was a simple fix in the end, but there was nowhere anyone had actually had a solution. Thanks to dv52 (Australia) for taking the time to assist me and come up with this recommendation. ***The solution was to uninstall and reinstall the OBDEleven app!*** Strange, as I had previously cleared the data and cache of the app, and that made no difference, but after reinstalling it fully, I suddenly had the basic headlight settings again and I was able to run them and accept them. I managed to clear the errors, but my headlights still aren't working as they used to with dynamic cornering or static cornering light coming on, so now I have to try and enable them again. Fingers crossed I can get it back to how it was at least, or with the Dynamic Light Assist would be even better. |
|
|
|
Post by iuliannl on Aug 8, 2021 18:56:11 GMT
Hi! I am new here and unfortunately got very fast disappointed by my first usage of the OBDeleven PRO yesterday because of additional errors on the headlights(main beam fault & adaptive light fault) just after going through "Headlight Regulation" module on the app in the "long coding" where I did no change except once have reached end of the list have "swipe to write" by mistake, time when the a.m. alarms immediately occurred. What I have now is 03455 in Central Electrics & C107E54 in Headlight Regulation, reason why I am actually writing here. It is about an AUDI A6C7 from 2017 and I would very much appreciate anyone support in clarifying these faults and maybe an explanation how they have occurred? Indeed on the C107E54 is stated "No basic setting" and guess there shall be a way to restore to basic settings although nothing was changed but still error is there, right?
Might be I am out of topic with the next remark, but is connected with my first usage: today scanned again hoping the basic settings could be recognized after long time engine off, but unsuccessful. Got a call and had to leave the car, so I have forgot the OBDeleven in the slot with the car off and when I have started the car after 3-4 hours have been surprised to see the clock on the MMI is reset to 0:00. Any remark/comment is highly appreciated as I am very disappointed and believed I have purchased a licensed tool helping me to have a good control of my car and not creating useless headache. Thanks guys!
|
|
|
|
Post by dv52 (Australia) on Aug 8, 2021 22:19:07 GMT
iulian : First your AUDI A6C7 is built on a MLB platform and the cars that are the subject of this thread are MQB platform - very different. You should be seeking a response on the A6 part of the forum That said and whilst I don't really understand your English, I suspect that your "swipe to write mistake" may have altered some part of the module long-code. To find-out what change was inadvertently made, scroll-down to History in the module and read the records.
Then revert the change(s) back to the old value and clear the error
Don
|
|
|
|
Post by jamesaudi on Nov 26, 2022 12:09:18 GMT
Cbaldan talk about scary.. So for any of you out there coding, I'll give you a useful tip!! If you are going for the eu spec drl and lights on your mqb chass, well ill let you know that it is possible with code only and I have to emphasize or stress that at anytime even if someone tells you to do it do not do it!!
If you switch any of your code to eu or if your in the eu. Trying to code u.S. Drl, don't code where you switch actual regional restrictions ( u.S coding sting and switching to e.U. Code physically, id you do you will be so sad.
Lucky I understand hex somewhat amd was able to fix it somewhat quicky.
I had a host more like a mob of issues to where as soon as I programed that string of code my lights shut off and 24 bad coding it changed a bunch of stuff (so always make backups at a good point) so all on top of that it took features that came with my audi s-line from my back up camera tomy car not starting again when I turned it off for a aplit second because I panicked not going to lie.. Haha.
So I emphasize on this issue for the sake of your car. I have everything back to how I coded it excluding half and half scandinavian and joker/pace effect for my drl/drl/lights/tail lights and break.
Its dope. Sorry I dont have functions for coding it I just trial and errored it, get mirrors lol. I paid 10 for one app (relearn/transmission since ive had this obdeleven pro) I wont need to buy anything elseive coded most of it ive coded 140 different functions for my car in the last two days that ive had this obd..
Also thanks bigggggg time to all the devs for the codes I need to get it done amd also to everyone in the audi/mk7gti scene
|
|
|
|
Post by innomkr on Jan 12, 2023 21:09:24 GMT
I am experiencing a similar issue - after enabling the one-click app HBA with IQ.Lights my left beams stopped moving during the DLA presentation only noise was generated from the motors. After fiddling around, the motor started working again. I did basic settings on a flat surface many times and my headlights are now pointing very high(its impossible to drive during dark hours). Please suggest something. I have given detailed information is this thread but no answers... forum.obdeleven.com/thread/17867/hba-lights-app-caused-problems |
|
