View Full Version : 1996 XJ is it OBD I or ODB II?

February 15th, 2012, 17:26
I have a 1996 Jeep XJ Country and I'm trying to figure out if its OBD I or OBD II.

I have gotten it scanned at Auto Zone and have had it scanned with a friends scanner it has the port at the bottom under the steering wheel but the main reason I'm asking is because I bought the Torque app for android to monitor my rpms, gas, speed, etc... and it won't read my jeep but will read my brothers 2006 Trailblazer.

So I'm just curious if it isn't reading it because its not an OBD II?

Anyone have any ideas?

February 15th, 2012, 17:28
2, do you have a Bluetooth adapter plugged into your jeeps port

Johnnie Walker
February 15th, 2012, 17:36
1996 was when OBD2 became the industry standard. I recently purchased a BT elm adapter on amazon for less than 30$ works great.

February 15th, 2012, 17:41
Yeah I have the Bluetooth adapter plugged in...This is what I bought;


I've followed the directions but it doesn't work in my jeep but it works in the 2006 Trailblazer...I knew I had an OBDII but it doesn't work its so frustrating...

February 15th, 2012, 18:01
You guys have any ideas? Could my ECU fuse be blown or something?

When I plug the blue tooth adapter into my ECU, the adapter light comes on...idk what to do.

February 15th, 2012, 18:29
Check all the fuses in the passenger kick well and the pdc along the passenger fender.. if all looks good and if you go to autozone and plug in a scanner and if it works your in good shape, might be a bad adapter you got.

Matthew Currie
February 15th, 2012, 18:31
The 96 is both II and I. OBDII should work, but if you have any doubts about its functionality, I'd find someone with a plain old OBDII reader and see what happens.

February 15th, 2012, 18:37
I've had it scanned at Auto Zone and it working fine, and I've also had it scanned by a friend and it worked fine too...

I will check the fuses tomorrow, but if the adapter was bad why would it work perfectly fine on the 2006 Trailblazer?

February 15th, 2012, 18:40
if its picking up a scanner then the obdII port on your xj is working. I dont know what to say about that adapter you got. to my understanding the 96 is a bit of a bastard child when it comes to obdII

February 15th, 2012, 18:42
Did you Google the issue?

February 15th, 2012, 18:53
I've tried googling and came up with nothing, I checked all the fuses and they are all fine...

The adapter works fine on other cars just not my jeep...which is the main reason I bought the damn thing! haha

February 15th, 2012, 18:54
Some of those come defective. You might have a defective one. Contact the seller and see about exchanging it.

February 15th, 2012, 19:01
Some of those come defective. You might have a defective one. Contact the seller and see about exchanging it.

You think its defective even if it worked on a 2006 Trailblazer?

February 15th, 2012, 20:32
all motor vehicles were mandated to be OBD II compliant by 1/1/1996.

Remember that OBDII isn't necessarily the SAME thing from 96 to 2012 there are over 5 differenet ISO protocals (how each vehicle platform communicates via OBDII interface.) The standard is WHAT the communicate, where the ALDL is located (within a certain # of feet from the driver's floor), the size and shape of the ALDL, universal/generic codes, and certain data/DTC parameters and how/when they are set.

GM for example use SAE J1850 protocal for communication, Chrysler and many Europeans use ISO 9141. If it worked on one OBD II GM SUV and not your XJ it is likey that it is a software on your scanner/tool isn't ISO 9141 compliant. PM your seller or contact the store you got it and specifically ask if it works on your year make and model if it supposed to get another one and see if that takes care of it.

OBDII has been enhanced a number of times through years too. The inclusion of more monitors, data lists, Misfire monitors, and CAN networks.

Paul Airhart
May 27th, 2016, 17:07
I know this is an old thread, but for those looking to find out if their 96' is an OBD-I or OBD-2, you can check the mnfg date on the sticker on the drivers door. Mine was built 12-95 and has OBD-I. My OBD-II scanner won't work and it gives me OBD-I codes using the turn the key and count method. Just FYI

Colonel Panik
May 28th, 2016, 08:33
What version is your bluetooth scanner? Those that have V2.0 or V2.1 or higher
do not always work on 96 vehicles. V1.xx will work fine.

May 28th, 2016, 12:32
Unless your 96 is an early build and for some reason has OBD1, I can confirm that that exact bluetooth scanner and Torque should work fine.

96 XJ Sport.

I don't know my build date, but it is early enough that my 96 has the 95 fuse panel. My 96 is OBD2.

I use the same one, and I run a digital dashboard off to the side when I drive. I cracked the scanner open, and re-ran the power lead so that it draws off the accessories of the Jeep instead of the OBD2 port. That way it turns off when the Jeep is off. I use Torque as well.

Sometimes, I have to mess with the phone a bit to get it to sync up. Sometime disabling, then re-enabling the bluetooth on the phone helps. Sometimes I have to go into the bluetooth detected devices on the phone and tell it to forget the device, and then find it again.

I have also used 3 of these BAFX on the Jeep, and all of them worked. (I have one carry in my day bag (to help friends), I have one permanently wired in, and I gave one to a friend.

Btw, because the 96 xj is a very early OBD2, it doesn't have a ton of data pids available, but it has some good ones.
O2 sensors voltage, Fuel trims, vacuum psi, system voltage, coolant temperature, speed, rpm, open/closed loop indication, throttle position, etc.

May 28th, 2016, 12:36
I have also found that if I turn the bluetooth on my regular phone, before the digital dash (just another phone), that I have a hard time connecting the scanner to the digital dash phone. It is like my normal phone is trying to get it first, then when I turn off the bluetooth on my regular phone, and repair the digital dash phone, it works fine.

I have used a Nexus 4 (digital dash) and a Nexus 5 (my day to day phone), and a Nexus 7 Tablet (a while ago when I was first playing with it) and all worked.