Back in the olden days around the 80's the auto world started using the ALDL interface on a lot of cars which was the precursor to the OBDI and then the OBDII interface. I was forced to get some basic understanding because I was doing a few Corvette engine transplants so with the FI engines I needed to install the ECM's to get it to run. I first started using SW and an old laptop but as the technology improved moved on to a few different scanners and now either use my plug in unit or my Torque Pro BT unit.
So my question is , is there some or many on this form who do not have or use a OBDII code reader. It seems like a cheap investment just to see and reset a code prior to getting the issue fixed. Just wondering

 

I have a bluetooth odb reader... but I found it lacking in giving the complete codes. I purchased one of those Cable/SDD packages from British Diagnostics on ebay... much more powerful.

 

So cheap and practical, why not have one?

Bought a wifi one on eBay. Downloaded "Dash Command" from the app store.

Aside from codes, provides a lot of metrics that may interest people

 

They're so cheap and useful that you'd think everyone would get one - and they may well do, once they know such things exist and are so cheap!

 

I'm a bit of a dinosaur with my Scan Gauge, but since I don't have a smart phone, it makes sense. At least I can see my water temp!

 

First things to do with a new (to you) car or any car you've had a while but not yet done: check codes, check OBD monitors are all set (aka complete), check OBD live data for sensors you understand (IAT, ECT, TPS, ...), then watch fuel trims. Do this while the car is OK and make notes. Then you have a baseline if/when it acts up.

Cost? $10-20 and quite a bit of time. But you can do it in a suit if you like, no oily stuff or getting cramped under the car involved.

 

Any suggestions on what code reader is worth buying? Seems like there are the standard OBDII readers that are cheap and work across all cars, for reading basic codes. But then there are Jag specific ones that apparently enable you to 'do more' - looks like $100 upwards. Then the dealer-type $1000 and more. Any guidance on whether the basic is fine, or do the more specialized ones have a lot more features?

 

The ids/sdd software and readers give you the same software the dealers use. There are issues with using the latest version due to its requirement for a full time internet connection.... But for a 2010, you can use the older versions. The software is complex and potentially harmful if you mess with something you shouldn't. A basic obdii reader and app will let you see codes and reset them as well as access to certain data like water temps that we can't normally see. If you are really going to diagnose your problems and fix them yourself, get the ids/add package. If you just want to get an idea of what your car is doing get an obdii reader.

 

I will throw some caution into this OBD mix.

Most auto manufacturers will advise against using these plug-in OBDII scanners simply because they are made by unknown manufacturers for genetic (non specific) car use and noone knows what circuitries are inside these plugs and how they might effect the car's electrical system. When plugged in, they are connecting right into the very complex electronic modules, including the ECM module.

I have been using one for all my Jags to show real-time engine operating parameters BUT... I have had several electrical glitches in my XKR and in our XF as the direct results of using them. Thus far, those glitches cleared when removing the OBDII plug but, no guarantees that a more serious glitch could harm the electrical systems.

 

No readers for me...I accept the fact that the dealer is much better than me at fixing this car.

 

Although some would use them as part of their DIY repair process I think the more useful part of having one is to see what you might be in for when you get an MIL (chk eng.) . It give you some insight and helps in reducing the dealer/indy BS . Kind of like trust but verify.

 

You're over-egging that pudding!

They connect to electronics mandated by law to be safe to connect into.

However, you're not meant to go shoving them in and pulling them out with power on. That's just a silly thing to do.

First switch car off & remove key.

 

I think he got the pudding just right. The point that he is making is that an inferior device might try to perform an unsupported operation which can possibly damage the car. The mandated law does not take this into consideration.

 

+1 for Sean's great advice here, complemented by that from [JagV8], I have been using successive versions of Mangoose+IDS/SDD for a few years, but stopped at Ver 139 which is good for all OBDII models up to and including 2014. Extraordinarily comprehensive and powerful but you have to be prepared to climb the learning curve. Essential for jobs like resetting TCM, resetting headlight leveller control module, reprogramming new keys and dozens of other "dealer equipment only" tasks.

Sean has mentioned the UK distributor, but I think they have worldwide supply chains and shipping. He didn't mention price and neither will I, but it's peanuts. Let google be your friend or try around that great bay in the clouds. If that's too challenging, go directly to their website.

Cheers,

Ken

 

Actually it does.

Have you read any of it let alone ALL of it? Well I have. Please stop posting that sort of nonsense. I'm sure it's well-meant but it's wrong.

 

My jag dealer will take my car for a week if they have to do diagnostics. So I use my OBDII and this forum to diagnose it myself. Than, depending on the problem, I can do minor stuff myself or bring the car to the dealer and tell them what I think is wrong and how I came up with my diagnosis, and then it takes them less time to fix it. Last time, they told me that I was correct and it only took a day instead of a week

 

The law covers the car, not the external device that you connect into it. Telling folks to be cautious about using inferior electronic devices is good advice. I work in technology and have seen plenty of hardware and software components perform erratically and do damage regardless of "the law" that was put into place. I will err on the side of caution thank you.

 

The car's OBD electronics can stand anything an OBD device however badly made can do, including shorts to ground and battery +.

What is it that you think is a problem that justifies your dire warnings? I am convinced you are wrong but please enlighten me.

BTW I too work in electronics - automotive electronics.

 

My Porsche mechanic has made plenty of money off customers using OBD devices that caused issues: A quick Google search is all you need:


MOTOR Magazine | OBD II |OBD II Ghosts & Gremlins ? Aftermarket Devices Can Create Service and Repair Nightmares


Multiple Conditions Caused by Aftermarket Devices Plugged into the Data Link Connector


If you believe that the OBD electronics can stand all you can throw at it, that's fine. We will just agree to disagree.

 

In low voltage electronics any spurious signal may cause undesirable interference in the operations of connected circuits.

In my personal experiences with plugged in bluetooth OBD II devices, thus far had 3 incidents: 1) A big warning popped up on my '10 XKR's electronic dash while doing normal cruising. It only cleared when I removed the OBD II. Only happened a single time, thus far, in about 4000 miles of driving the car.

2 & 3) My wife's XF's reaction to the OBD II was different: twice it refused to play music from my connected thumb drive until the OBD II was removed. It only does it, perhaps 10 percent of the driving times.

Neither one was serious to damage the car but, the warnings were there; The OBD II can and will cause unpredictable interference with the car's electronics. Since it is unpredictable, who knows what it may effect next.

I also work with electronics, being a Specialist Electrical Engineer, specializing in trouble shooting scenarios that others can not explain by normal testing methods. I could write a book on the various scenarios that I have come across where seemingly unrelated equipment causes multiple issues in peripheral devices. I am not an expert in automotive electronics but, I can easily see how a device, that in various states of operation could present a certain impedance to the car's computer circuitry, would trigger a transistor, causing unexpected scenarios.