|
Post by wiscorob on Dec 8, 2023 20:50:01 GMT
If this belongs in a more specific thread please let me know which one and I'll move it.
I just got an OBDEleven Pro iOS for my 2023 Jetta GLI and did a couple one click apps and a single long code change. The next morning I got an error on the dash that I can't get to clear. If anyone knows how to solve this, I would really appreciate the help!
-Rob
Problem:
Dashboard Notification; “Lane Assist Not Available” with Orange Triangle Illuminated
OBDEleven Fault:
A5 Driver Assistance Control Unit
Steering: Interface for lane departure warning system not coded
Fault Code: C10ACF2
History:
Only change made involving Steering/Driver Assistance;
Long Coding: Control Unit 44 Steering Assistance
Coding: Heading control assist
Old Value: Active
New Value: Not Active
Attempted Fixes:
1. Undo Previous Changes:
Control Unit 44 Steering Assistance
Long Coding: Lane assistant (there is no feature named “Heading control assist” and I think this is what I actually changed initially) change from “Not Active” to "Active": Results in notifications of roughly “Could Not Write” OR “Function Not Available” (I’ve tried this with engine on/off, hood open/closed with no success) The Lane Assist Feature continues to read "Not Active"
2. Soft Reset of Control Unit 44 Steering Assistance: Results in notification of roughly “Could Not Reset” OR “Function Not Available”
3. Soft Reset of Control Unit A5 Driver Assistance: Results in notification of roughly “Could Not Reset” OR “Function Not Available”
4. Clear Codes: Results in Codes on Dashboard and OBDEleven immediately reappearing
5: Searching through the app and forum for other things to try or similar posts with no luck.
|
|
jas15
New Member
Posts: 3
|
Post by jas15 on Dec 12, 2023 12:50:03 GMT
Sorry that I’m not replying with a solution, but I had the exact same thing happen to me last night. I couldn’t solve it so I ended up factory resetting adaptations DO NOT DO THIS! Thinking it would fix the problem… it fixed the problem… then chucked another 6 faults up instead.
What I was thinking I should have done is re-enabled the bit that gave me the adaptation options such as LDW/BAP personalisation then turn them off first, then undo the bit as I was thinking maybe it’s unavailable but the values are still used somewhere (and now incorrectly set)
Whatever you do, don’t do what I did and try a factory reset on adaptations!
I also saw elsewhere that the error is sometimes caused by Byte 12 Bit 5 (I may have it wrong) but it’s the STA feature
|
|