Jeep Commander Forum banner

1 - 8 of 8 Posts

·
Registered
Joined
·
338 Posts
Discussion Starter #1
I have an older 10+ year acktron OBDII reader that is not linking with my 2010 Commander. Is it possible that it is not compatible or do I have some other issue like a problem/defect with the Commander or scanner?

I am thinking of replacing it with one of these:

http://www.concoursdirect.com/dodge-ram-hemi-diablo-predator.html

but that is a different conversation.
 

·
Registered
Joined
·
338 Posts
Discussion Starter #2
Anybody??????

Has anybody ever had an OBDII scanner not work in a OBDII car?

I wondering if this is a bigger issue I'm having or a simple incompatibility.
 

·
Registered
Joined
·
480 Posts
Don't know about the compatibility but I have the diablo tuner and it works great. If you just need to pull codes that is already built into the commander. Cycle the key from off to start (without turning it over) three times ending in the start position (insert key go to start, off, start, off, start). Your digital readout on your gauge cluster will say "dtc codes" and either list them or say done if there is none.
 

·
Super Moderator
Joined
·
14,914 Posts
If you just need to pull codes that is already built into the commander. Cycle the key from off to start (without turning it over) three times ending in the start position (insert key go to start, off, start, off, start). Your digital readout on your gauge cluster will say "dtc codes" and either list them or say done if there is none.
That doesn't work on the 2010 models, which is what he has.
 

·
Registered
Joined
·
480 Posts
Well thats a rip! oh well.
 

·
Registered
Joined
·
338 Posts
Discussion Starter #6
That doesn't work on the 2010 models, which is what he has.
Thanks for confirming that. I had already tried it, but nice to know it's not just me.

I really just want to clear the code(s) so the light will go out...... maybe I can just pop it with the finishing nail gun.........
 

·
Registered
Joined
·
338 Posts
Discussion Starter #7
As I wasn't getting much help here, I had to do my own internet search....DARN!

Anyway, here is what I found so far:

Generic OBD-II functionality is limited to cars using ISO 9141-2 ("CARB"), ISO 14230 ("KWP-2000") and ISO-15765 ("CAN") protocols. Our interfaces do not support the SAE J1850-VPW and J1850-PWM protocols used by most US-market GM and Ford products, so this cannot work on those cars. Most early (1996-2000) OBD-II compatible Chrysler cars used ISO-9141-2. Many newer Chrysler cars use SAE-J1850 and are incompatible. Most European and Asian cars use ISO and should be compatible. In US models, Generic OBD-II compatiblilty was required as of model year 1996. In Canada, 1998. In the European Market, 2001 (gasoline-powered) and 2004 (diesel-powered).
Interfaces: Our HEX+CAN interfaces support ISO 9141-2 ("CARB"), ISO 14230 ("KWP-2000") and ISO-15765 ("CAN") protocols. Our non-CAN HEX-, KEY-, and KII- series interfaces support ISO 9141-2 ("CARB"), ISO 14230 ("KWP-2000"), but do not support ISO-15765 ("CAN"). Our Micro-CAN interface support ISO-15765 ("CAN"), but do not support ISO 9141-2 ("CARB") or ISO 14230 ("KWP-2000") for generic OBD-II. The ISO-15765 ("CAN") protocol was introduced in a few cars in model year 2004 and became universally required in all cars sold in the US market for model year 2008.



So, it looks like it quite possible the older scanner that I used on my 96 Bronco and wife's 2002 Liberty may not work on the 2010 Commander.



 

·
Registered
Joined
·
1 Posts
My recent OBDll Reader Experiences

I purchased an OBDll code reader in April 04 and it would not work on an 09 Jeep Patriot. It is an Actron CP9135 on a "buy to borrow" basis and never returned it. The booklet is copywright 2003. It still works on all the older cars which I checked afterwards.

I recently purchased an Elm327 OBDll reader which works with a computer through the USB port (or wifi or Bluetooth if purchased that way) purchasable on Ebay. This module and cable connected to your computer (preferable a laptop) monitors active engine parameters with the car running and while driving, read by an assistant, which is superior to just the reader. Advanced software is available for each car model at a rather steep price. This system read the codes on my 09 Jeep just great and also read the engine parameters. I am surprised that Actron unit had such a short usable software life of 5 or 6 years in the future or maybe less! I wish it still worked; I am hesitant to rush out to the car possibly in the rain or snow with my fragile laptop and prefer the reader because it is more robust to just read codes.

My Elm327 reader uses a cable but now the Bluetooth or wifi option on ANY computer including an iPad makes it more friendly and just looking now at the prices of $10-15., WHY purchase a reader. The Actron unit was $150 now maybe $60.00.
 
1 - 8 of 8 Posts
Top