Electrical P2097 + BMcables= Alcoholism
P2097 + BMcables= Alcoholism
OK, so my problems began when my 2006 non-S Cooper convertible triggered a code for the post cat O2 sensor. Long story short, I replaced the sensor and as I’m sure you can guess, P2097 triggered. OK, so time to re-set the adaptive data so I bought a cable and software from bmcable on Ebay. Here’s where the fun begins.
I installed the software with no problems and proceeded to attempt to clear the code and re-set the adaptives. As I’m sure you can guess, I’m having issues communicating between my computer and my car.
In INPA, the battery and ignition dots are black when I’m plugged into the car. When I hit the “Info” button, F1, It shows all question marks for the EDIABAS info (ini path, Ecu path, interface). When I double click the EDIABAS button in the tray, EDIABAS shows the proper location for ediabas.ini and STD:OBD for the interface. I checked C:\EDIABAS\Bin\EDIABAS and remote host and diagnosisport are set correctly (192.168.68.1 and 6801). When I click R50, shift+F4, it gives me an option for memory errors which I’ve used to clear the P2097 code. The fact that I get no info from the information tab leads me to believe I have a comm issue but hitting shift+F4 allows me to clear codes. Wait, there’s more…
DIS appears to be my bigger issues. I can’t get DIS to communicate with the car at all. When I click administration/config/diagnostic head, nothing shows up in “free diagnostic heads”. Also, on the main screen, there are no colored blocks in the box that’s third from the right end at the top of the screen. When I click the “Diagnosis” button on the main screen, the diagnosis start screen comes up but there is no option for Mini so I can’t even attempt to diagnose.
Needless to say, I’m getting frustrated after three days of reading NAM, Bimmerforums, and bmwcoding and still feeling lost. I really don’t want to be “That guy”, I’ve searched and I’ve read and I’m still screwed, LOL. Please help me get my wifes Mini back on the road (legally). I need to get this thing inspected and the registration renewed. ANY help given would be greatly appreciated! Thanks
I installed the software with no problems and proceeded to attempt to clear the code and re-set the adaptives. As I’m sure you can guess, I’m having issues communicating between my computer and my car.
In INPA, the battery and ignition dots are black when I’m plugged into the car. When I hit the “Info” button, F1, It shows all question marks for the EDIABAS info (ini path, Ecu path, interface). When I double click the EDIABAS button in the tray, EDIABAS shows the proper location for ediabas.ini and STD:OBD for the interface. I checked C:\EDIABAS\Bin\EDIABAS and remote host and diagnosisport are set correctly (192.168.68.1 and 6801). When I click R50, shift+F4, it gives me an option for memory errors which I’ve used to clear the P2097 code. The fact that I get no info from the information tab leads me to believe I have a comm issue but hitting shift+F4 allows me to clear codes. Wait, there’s more…
DIS appears to be my bigger issues. I can’t get DIS to communicate with the car at all. When I click administration/config/diagnostic head, nothing shows up in “free diagnostic heads”. Also, on the main screen, there are no colored blocks in the box that’s third from the right end at the top of the screen. When I click the “Diagnosis” button on the main screen, the diagnosis start screen comes up but there is no option for Mini so I can’t even attempt to diagnose.
Needless to say, I’m getting frustrated after three days of reading NAM, Bimmerforums, and bmwcoding and still feeling lost. I really don’t want to be “That guy”, I’ve searched and I’ve read and I’m still screwed, LOL. Please help me get my wifes Mini back on the road (legally). I need to get this thing inspected and the registration renewed. ANY help given would be greatly appreciated! Thanks
A few thoughts....
On some cables, a pin, #8 if I recall must be split or bonded for some cars..a spec changed in 2004....so depends on the spec the cable you made was for...
Next thought...
Which O2 sensor did you get? NTK/NGK seem to be the one that works best...
others sometimes cause issues....
next...inspect the exhaust CLOSELY for leaks...a tiny LEAK can let o2 in...and throw off the calculations....
And finely...the cat COULD BE DEAD...how many miles?
On some cables, a pin, #8 if I recall must be split or bonded for some cars..a spec changed in 2004....so depends on the spec the cable you made was for...
Next thought...
Which O2 sensor did you get? NTK/NGK seem to be the one that works best...
others sometimes cause issues....
next...inspect the exhaust CLOSELY for leaks...a tiny LEAK can let o2 in...and throw off the calculations....
And finely...the cat COULD BE DEAD...how many miles?
Ok, short update. After doing some more research, I found out how to add Mini as an option for diagnosing in DIS. I was able to add RR as well, not that I'll ever need it but I figured while I was in there, I might as well choose that option as well. So, now I'm able run diagnosis on my Mini but still haven't been able to reset adaptives. I've checked for leaks on the intake and exhaust side but I would still need to reset to clear the code so I would still be in the same boat whether I fixed a leak or not. Probably gonna go ahead and replace both O2's with the proper part but again, no reset of adaptives will still mean I will have the light. Lovely.
One last update. I finally reset the adaptives in INPA and the CEL has been off for about 75 miles or so. I'm getting the car inspected as I type. I tested the O2's using DIS and they both checked out fine. The theory that the voltages using Bosch sensors aren't quite right doesn't seem to hold out in my case. It tested just fine. Not to say that this will always be the case but, so far so good.
Thread
Thread Starter
Forum
Replies
Last Post
Interior/Exterior How-To: X-Pel Headlight Protection Install
cooperdude
Interior/Exterior
2
Aug 2, 2005 10:50 AM




