|
|
Post by gamegenie on Sept 10, 2016 17:05:36 GMT
OBDeleven developers, please advise as to why my OBDeleven Pro app is triggering this " marginal conditions" error message when I try to use the Long Coding for A5 module of my Audi A3. I'm trying to activate the High Beam Assist as I have the Active Lane Assist package on my car that comes with the front facing camera mounted above the rear-view mirror. I saw that this was possible from numerous threads online discussing Vagcom/VCDS modifications and I was simply trying to follow these steps: My trouble is primarily with long coding Module A5, I was able to do the adaption and long coding for Module 9. 1. On the Long coding page I click on the 01 icon in the top right corner.  2. I change the Byte 02 value to Bit 1, click the green check mark to save and get this error.  3. I can only back out of this by undoing my change, so I do this returning to previous page and try to accomplish the long coding by simply selecting High Beam Assist for coding_Light_Assist.  4. Next click the Green arrow to save, boom same error as before, this time with a number in parenthesis. Please advise.  I thought I get lucky and could continue on past this regardless of the " marginal conditions" error at the A5 module. I went to my MMI, into the Car Systems and to Exterior lighting, and into Automatic headlights and saw that I now had check box for Headlight Assist select. I check that box and proceed to then push the high-beam stalk and that triggered a (A)High Beam fault error on the DIS. I need to figure out why I can't make changes to module A5 in long coding. |
|
|
|
Post by gamegenie on Sept 11, 2016 17:52:14 GMT
Need the security login code for modifying the A5 module.
I think I've hit a show-stopper at this point with the access code to that area.
Function_Module_Main_Beam_Assist and Function_Module_Road_Sign_Recognition are both in the Adaptations of the A5 Module and they are locked behind a security firewall.
|
|
|
|
Post by gamegenie on Oct 16, 2016 18:20:47 GMT
Update.
I figured out the A5 login code, found it searching online.
But the bigger update is that I successfully activated High Beam Assist.
Barring the recent Obdeleven app update through Google Play had no bug fixes (which would be the reason for this resolve), I resolved the problem I screenshot earlier by going through the steps with the car engine-off, and the Light Switch set to the OFF position. Only the ignition was ON.
Before I was doing this with the Car fully on (ignition + engine) and the Light switch was in Auto position.
When I went through the steps with all that turned off, the OBDeleven app accepted all my code changes.
Started up the car, turned the light switch back to Auto. Pressed the Stalk back to activate the High-Beam and it put the (A)= symbol on my DIS display which is the Light Assist symbol.
This is awesome. I knew there had to be more functions for my Active Lane Assist than just keep my car in the lane. Tonight I'm going to go cruising down dark roads to test the high beam assist.
|
|
|
|
Post by migzy on Nov 19, 2016 17:22:52 GMT
hey peeps i'm stuck trying to activate Module 09 - Adaptations - “Assistant light functions - Menuesteurung Fernlichtassistent" changed to 'PRESENT' on my MY17 TTS for the life of me i can'e see Menuesteurung Fernlichtassistent, i've tried with the engine off and on. All the other steps I can do without issues  Any ideas ? |
|
|
|
Post by MGRobbie on Dec 19, 2016 11:01:50 GMT
OBDeleven developers, please advise as to why my OBDeleven Pro app is triggering this " marginal conditions" error message when I try to use the Long Coding for A5 module of my Audi A3. I'm trying to activate the High Beam Assist as I have the Active Lane Assist package on my car that comes with the front facing camera mounted above the rear-view mirror. I saw that this was possible from numerous threads online discussing Vagcom/VCDS modifications and I was simply trying to follow these steps: I Made changes as follows: Module 09 - Adaptations - “Assistant light functions - Menuesteurung Fernlichtassistent" changed to 'PRESENT' Module A5 - Long Coding, change byte 2, use drop down menu to select correct coding - "02 Light/High Beam Assist Mode 2 - High Beam Assist (FLA) / Dynamic Light Assist (DLA)" I saved all but nothing changed apparently. Any suggestions?? |
|
|
|
Post by gamegenie on Dec 29, 2016 17:54:03 GMT
hey peeps i'm stuck trying to activate Module 09 - Adaptations - “Assistant light functions - Menuesteurung Fernlichtassistent" changed to 'PRESENT' on my MY17 TTS for the life of me i can'e see Menuesteurung Fernlichtassistent, i've tried with the engine off and on. All the other steps I can do without issues Any ideas ? I hope you seen my last post. Did you try this with your headlight set to the OFF position? |
|
|
|
Post by gamegenie on Dec 29, 2016 17:55:05 GMT
OBDeleven developers, please advise as to why my OBDeleven Pro app is triggering this " marginal conditions" error message when I try to use the Long Coding for A5 module of my Audi A3. I'm trying to activate the High Beam Assist as I have the Active Lane Assist package on my car that comes with the front facing camera mounted above the rear-view mirror. I saw that this was possible from numerous threads online discussing Vagcom/VCDS modifications and I was simply trying to follow these steps: I Made changes as follows: Module 09 - Adaptations - “Assistant light functions - Menuesteurung Fernlichtassistent" changed to 'PRESENT' Module A5 - Long Coding, change byte 2, use drop down menu to select correct coding - "02 Light/High Beam Assist Mode 2 - High Beam Assist (FLA) / Dynamic Light Assist (DLA)" I saved all but nothing changed apparently. Any suggestions?? Did you try this with the car on but the ENGINE OFF and the headlights switched to the OFF position? |
|
|
|
Post by MGRobbie on Jan 31, 2017 6:45:40 GMT
I think I did. Not sure. I will try again. Engine off, light off, ignition on. Than modify the setting. Keep you updated.
|
|
|
|
Post by MGRobbie on Feb 6, 2017 11:40:14 GMT
I have tried again to change these settings as follows:
Start button on
Engine off
Light switch off
No succes in changing this to HBA.
Do not know where to continue.
Can any of you display here the coding list.
looking forward to feedback.
|
|
|
|
Post by MGRobbie on Feb 11, 2017 14:37:04 GMT
OBDeleven developers, please advise as to why my OBDeleven Pro app is triggering this " marginal conditions" error message when I try to use the Long Coding for A5 module of my Audi A3. I'm trying to activate the High Beam Assist as I have the Active Lane Assist package on my car that comes with the front facing camera mounted above the rear-view mirror. I saw that this was possible from numerous threads online discussing Vagcom/VCDS modifications and I was simply trying to follow these steps: I Made changes as follows: Module 09 - Adaptations - “Assistant light functions - Menuesteurung Fernlichtassistent" changed to 'PRESENT' Module A5 - Long Coding, change byte 2, use drop down menu to select correct coding - "02 Light/High Beam Assist Mode 2 - High Beam Assist (FLA) / Dynamic Light Assist (DLA)" I saved all but nothing changed apparently. Any suggestions?? Got it working now. Thanks to all. |
|
|
|
Post by dv52 (Australia) on Mar 11, 2017 8:13:11 GMT
I Made changes as follows: Module 09 - Adaptations - “Assistant light functions - Menuesteurung Fernlichtassistent" changed to 'PRESENT' Module A5 - Long Coding, change byte 2, use drop down menu to select correct coding - "02 Light/High Beam Assist Mode 2 - High Beam Assist (FLA) / Dynamic Light Assist (DLA)" I saved all but nothing changed apparently. Any suggestions?? Got it working now. Thanks to all. hmm.................. I assume that "Module A5 - Long Coding, change byte 2" meant that Bit 0 was ticked. Might be worth checking!
Also check the value of Byte 2, Bit 0-2 in the module @ address hex09, which should be hex03, or in binary: Bit 0=1, Bit 1=1, Bit 2=0
|
|
