Coding for turning on Audi Active Lane Assist (all cars with pre sense)
#981
#982
AudiWorld Member
Hmm.. I recommend doing some research on the topic. Your 2017 A6 is a "C7 Platform" vehicle, and I don't know whether that generation A6 supports Pre sense city (and by association, Audi Lane Assist).
#983
#984
Here is the coding and adaptations that I used to activate Audi Active Lane Assist, I am not making any promises or assuming responsibility, code at your own risk, But it worked perfectly for me. I do get a few faults but I think it is due to me trying to activate Traffic Sign Recognition. UPDATE: Unchecking the option for STA in A5 coding (Byte 16->Bit 5) and you will no longer get the congestion assist fault code.
You will get a few bings from your car about Pre Sense Malfunction, these will all go away once you are done. This will activate the self steering, steering wheel vibration, and lane crossing warning. Do all the coding then do adaptations.
You will get a few bings from your car about Pre Sense Malfunction, these will all go away once you are done. This will activate the self steering, steering wheel vibration, and lane crossing warning. Do all the coding then do adaptations.
#986
Audi A4 B9/8W.
I deactivated part 2 and then part 1 from the app and everything reverted back to normal luckily. I was scared I had messed up as I didn't know to take a backup!
I would like to understand how I maybe able to do this, but I have no experience coding using OBD11
I deactivated part 2 and then part 1 from the app and everything reverted back to normal luckily. I was scared I had messed up as I didn't know to take a backup!
I would like to understand how I maybe able to do this, but I have no experience coding using OBD11
#987
I was reading through the thread and I couldn't find any indication if someone managed to enable ALA on an A7 (or A6) using these instructions?
I have an A7 C7 2017 with matrix led, pre sense front, ACC and auto high beams.
I recently purchased OBD11, but I don't want to mess anything up
I have an A7 C7 2017 with matrix led, pre sense front, ACC and auto high beams.
I recently purchased OBD11, but I don't want to mess anything up
#988
I have 4 options, off, original, then the option to set I'd you have the stalk and the one without.
I've tried original and Off but it still activates.
#989
I know this a very old thread, but having an issue undo-ing this coding. I'm able to reverse all of it except some of the long coding on the A5 section.
"A5 - Frt Sens. Drv. Assist
HC>Active | Byte 16>Bit 7
EFP>Active | Byte 12>Bit 3"
Changing these two items back to their original "not coded" settings in OBDeleven comes up with an error "(22) Function cancelled, marginal conditions have not been met".
All other changes were rolled back successfully, so I don't think it's an order of operations thing. I've also rolled back all other minor coding changes I had so I don't think it's a conflict. Any ideas?
"A5 - Frt Sens. Drv. Assist
HC>Active | Byte 16>Bit 7
EFP>Active | Byte 12>Bit 3"
Changing these two items back to their original "not coded" settings in OBDeleven comes up with an error "(22) Function cancelled, marginal conditions have not been met".
All other changes were rolled back successfully, so I don't think it's an order of operations thing. I've also rolled back all other minor coding changes I had so I don't think it's a conflict. Any ideas?
#990
AudiWorld Senior Member
I know this a very old thread, but having an issue undo-ing this coding. I'm able to reverse all of it except some of the long coding on the A5 section.
"A5 - Frt Sens. Drv. Assist
HC>Active | Byte 16>Bit 7
EFP>Active | Byte 12>Bit 3"
Changing these two items back to their original "not coded" settings in OBDeleven comes up with an error "(22) Function cancelled, marginal conditions have not been met".
All other changes were rolled back successfully, so I don't think it's an order of operations thing. I've also rolled back all other minor coding changes I had so I don't think it's a conflict. Any ideas?
"A5 - Frt Sens. Drv. Assist
HC>Active | Byte 16>Bit 7
EFP>Active | Byte 12>Bit 3"
Changing these two items back to their original "not coded" settings in OBDeleven comes up with an error "(22) Function cancelled, marginal conditions have not been met".
All other changes were rolled back successfully, so I don't think it's an order of operations thing. I've also rolled back all other minor coding changes I had so I don't think it's a conflict. Any ideas?