: OBDII Not working
Jul 26th, 2012, 12:23 PM
Bought AutoEnginuity software which works via OBDII in 2009. Think I got it to work with the car once, but never since. Has always worked with my 2007 Jeep Wrangler X and recently tested it with another Euro car, a 2005 Audi A4.
I have run though the built in diagnostic routines and reset the instrument cluster. I have checked for proper voltage. I have tried connecting while the car is both off, on ACC, and cranking... I have purchased another OBDII reader, which again works with other cars but not my Mini. I have checked every single fuse in the passenger compartment panel, and found no faults.
Looking for additional options. Wondering if my last trip to the dealer (also 2009), if they may have disabled it. Also have a unichip, and curious if that could be the culprit. I believe I also had the unichip out for a while in 2009. Plan on removing it soon to check, but would be good to know if someone already has the answer.
2005 MCS, I am the original owner, and it has been here in Guam with me since 2007.
Jul 30th, 2012, 09:22 AM
Had the same "problem" on my R52 and took some digging to get the answer.
Not all 1st generation MINI's are OBD2 compatible. I'm not 100% sure, but I think BMW only started to implement the OBD2 protocol as standard since 2006-2007. It has only been mandatory in the US market, since 2008.
There should be a "OBD2 compatible" sticker or plate under the hood or somewhere on the car, if it is compatible.
So, you can't just use any OBD2 cable and software.
You need an EDIABAS cable, which looks exactly like the OBD2, but the pins inside the plug is configured slightly differently. So, you might get some communications going if you're using a standard cable, but you won't get full functionality.
The most popular software for doing basic diagnostics is called INPA and the NCS Expert will allow you to change some basic setting like comfort opening, DLR, etc.
I ordered my cable from Cable Shack, via EBay for ±$25. The best part was that it came with a bunch of software (3 DVD's) and all the data files that I needed for my R52. There are sites where you can download it from, it can be tricky to get the correct versions of the software and the model specific DATEN files - seems that most downloads are for BMW's.
I'd give you the link to where I ordered by cable from, but I haven't made 15 posts yet. (not sure why that'd make any difference...)
So, you'll have to search for "BMW USB OBD Cable lead Ediabas Inpa GT1 DIS SSS Progman" on EBay.Co.Uk.
Hope that solves your problem.
Jul 31st, 2012, 07:18 AM
Thanks, will look into that. Hesitant though, to buy more stuff...
According to Wikipedia, OBDII became mandatory in the USA in 1996, which I believed to be true... There was an update in 2008 however, that mandated the specific protocol to be used, because as far as I know there are about 6 different communication port protocols which are OBDII compliant.
For now I think I'm going to focus on removing the Unichip as a factor and see if that gets me anywhere.
Thanks for the EDIABAS stuff though, good gouge I probably wouldn't have found on my own.
Jul 31st, 2012, 03:47 PM
Sorry, what I should have said was that OBDII, in its current form, was only mandated in the US in 2008.
The 2008 update was rather significant. For example, it requires the interface pins #6 and #14 to be connected for CAN High and CAN Low.
Logically, after most car manufacturers had switched to the CAN bus protocols in 2006, the adapter/cable manufacturers would surely have followed. Resulting in most new(ish) scan tools and cables only supporting the new, standard protocol.
If you take a look at the adapter port in your car, I'm sure that you'll find pins 6 and 14 to be empty. I've attached a photo to show what mine looks like. You'll see that those pins are empty.
The Autoenginuity is rather pricy, so I can understand why you'd be hesitant to fork out more money for more equipment, but if you want to do more than just read diagnostic data, you will need BMW's OEM software which, AFAIK, only works via an EDIABAS interface. Remember, OBD2 only requires certain data to be readable, not all.
I had the same symptoms and basically came to the same conclusions that you have. The information that is out there is so frustratingly convoluted that I was close to giving up. But, once I got the correct hardware, the rest was pretty easy; practically plug-and-play.
(Don't bother with a RS232 serial OBD2 cable - not all USB-to-Serial converters seem to work.)
As for the dealer disabling your OBD port... I'm pretty sure that'd be illegal. Wasn't one of the reasons why OBD protocols were standardized and mandated, to enable 3rd parties to test emission levels and so forth?