Clarifications on “Hard Code” clearing with regular scanner vs. Dealer tools
Thread Starter
|
Neutral
Joined: Jun 2023
Posts: 1
Likes: 0
Clarifications on “Hard Code” clearing with regular scanner vs. Dealer tools
My ‘06 R53 popped code P2096 for long term post-cat O2 sensor lean burn a few months ago. Since then, it comes back every 1-3 drive cycles/every 3-10 miles after I clear it (but I often just leave it).
There are no other lean burn symptoms- not down on power, not running hot, not crazy MPG, etc.
Seeing people say that it can be air, fuel, or spark related, I’ve replaced filters, plugs and wires, and the rear O2 sensor and done my best to rule out any obvious exhaust leaks or intake leaks.
However, it still comes back like clockwork.
In my latest forum deep-dive, I’ve come across folks who say they experienced the same issue, made a fix to a potential cause, and had it come back until they used a dealer tool to reset/clear “adaptations.”
I’ve been using a ~$30 Amazon scan tool that makes the SES light go away and indicates no stored or pending codes. I’ve seen a lot of P2096 threads with people saying their scan tools can’t clear the code, so I figured since mine does I was set. But is this some “lesser” level of clearing that could be resulting in P2096 coming back even if the root cause is resolved? Should I try to find a more advanced tool that can dive deeper to resolve this?
There are no other lean burn symptoms- not down on power, not running hot, not crazy MPG, etc.
Seeing people say that it can be air, fuel, or spark related, I’ve replaced filters, plugs and wires, and the rear O2 sensor and done my best to rule out any obvious exhaust leaks or intake leaks.
However, it still comes back like clockwork.
In my latest forum deep-dive, I’ve come across folks who say they experienced the same issue, made a fix to a potential cause, and had it come back until they used a dealer tool to reset/clear “adaptations.”
I’ve been using a ~$30 Amazon scan tool that makes the SES light go away and indicates no stored or pending codes. I’ve seen a lot of P2096 threads with people saying their scan tools can’t clear the code, so I figured since mine does I was set. But is this some “lesser” level of clearing that could be resulting in P2096 coming back even if the root cause is resolved? Should I try to find a more advanced tool that can dive deeper to resolve this?
5th Gear
Joined: Aug 2003
Posts: 839
Likes: 225
Do yourself a favor and get a hold of a BMW/MINI specific scanner. They are able to read the hex codes from the modules which often provide a clearer picture of the actual problem. This is because there's sometimes several different hex codes associated with one P code. Knowing only the P code doesn't give you the full picture.
I can't speak specifically to your scanner, but more often than not the adaptations get reset when you clear error codes. In your case, it might be a good idea to try a DME reset using the hidden menu.
I can't speak specifically to your scanner, but more often than not the adaptations get reset when you clear error codes. In your case, it might be a good idea to try a DME reset using the hidden menu.
5th Gear
Joined: Jan 2006
Posts: 991
Likes: 224
My ‘06 R53 popped code P2096 for long term post-cat O2 sensor lean burn a few months ago. Since then, it comes back every 1-3 drive cycles/every 3-10 miles after I clear it (but I often just leave it).
There are no other lean burn symptoms- not down on power, not running hot, not crazy MPG, etc.
Seeing people say that it can be air, fuel, or spark related, I’ve replaced filters, plugs and wires, and the rear O2 sensor and done my best to rule out any obvious exhaust leaks or intake leaks.
However, it still comes back like clockwork.
In my latest forum deep-dive, I’ve come across folks who say they experienced the same issue, made a fix to a potential cause, and had it come back until they used a dealer tool to reset/clear “adaptations.”
I’ve been using a ~$30 Amazon scan tool that makes the SES light go away and indicates no stored or pending codes. I’ve seen a lot of P2096 threads with people saying their scan tools can’t clear the code, so I figured since mine does I was set. But is this some “lesser” level of clearing that could be resulting in P2096 coming back even if the root cause is resolved? Should I try to find a more advanced tool that can dive deeper to resolve this?
There are no other lean burn symptoms- not down on power, not running hot, not crazy MPG, etc.
Seeing people say that it can be air, fuel, or spark related, I’ve replaced filters, plugs and wires, and the rear O2 sensor and done my best to rule out any obvious exhaust leaks or intake leaks.
However, it still comes back like clockwork.
In my latest forum deep-dive, I’ve come across folks who say they experienced the same issue, made a fix to a potential cause, and had it come back until they used a dealer tool to reset/clear “adaptations.”
I’ve been using a ~$30 Amazon scan tool that makes the SES light go away and indicates no stored or pending codes. I’ve seen a lot of P2096 threads with people saying their scan tools can’t clear the code, so I figured since mine does I was set. But is this some “lesser” level of clearing that could be resulting in P2096 coming back even if the root cause is resolved? Should I try to find a more advanced tool that can dive deeper to resolve this?
I have no detailed info on trouble shooting a P2096 code but I'd hazard a guess you have more trouble shooting to do. For intake leaks/exhaust leaks you need to be sure there are none. That the code reappears after some engine run time suggests the problem may be temperature related.
Thread
Thread Starter
Forum
Replies
Last Post
Drivetrain Check Engine Light, code 08343 and P0130
SteveS
Drivetrain (Cooper S)
8
Apr 27, 2010 03:22 AM