RoyJ

A plain OBDII reader should be fine for all your vehicles with the
possible exception of the 2006 Nissan.

I did a google search, was not coming up with anything definitive. I was
looking at buying a scanner last summer (working a problem with another
vehicle). My research said that OBD I was a '80's to 1995 vintage
system, plain OBD II was mid 90's (depends on what vehicle), the CAN
system (Controller Area Network) protocol was introduced on SOME
vehicles in 2004, all vehicles by 2008(?) The plug is the same for CAN
vehicles, the software is different. The plain OBD II would work for my
current vehicles, just seemed silly to buy something that would not work
for any new vehicles. Price was about double to get the CAN capability,
didn't buy anything.

A plain OBDII reader should be fine for all your vehicles with the
possible exception of the 2006 Nissan.

I was looking at the IEQUUS products, all CAN capable, didn't buy one.
http://www.iequus.com/products.php?category_id=1_10_7

twaldron wrote:
> Not they way I was understanding the 9145 Scanner...are you talking
> about the 9175 Reader...not that it matters? I need this to read 1997
> Ford, 2001 Jeep, 2003 Jeep, and 2006 Nissan. I believe they are all
> OBC-II past 1996. Don't know why 2004-2006 would be any different.
> Please explain.
>
> tw
>
> RoyJ wrote:
>
>> Does not say it is upgradable to the CAN protocols. Won't work on
>> anything from 2004 (?) and up.
>> http://www.actron.com/publish/2006/0...atsnew_1_6.pdf
>>
>> Outatime wrote:
>>
>>> twaldron wrote:
>>>
>>>> Ah, I just went with a Actron CP9145....no PC stuff but portable.
>
>

RoyJ

A plain OBDII reader should be fine for all your vehicles with the
possible exception of the 2006 Nissan.

I did a google search, was not coming up with anything definitive. I was
looking at buying a scanner last summer (working a problem with another
vehicle). My research said that OBD I was a '80's to 1995 vintage
system, plain OBD II was mid 90's (depends on what vehicle), the CAN
system (Controller Area Network) protocol was introduced on SOME
vehicles in 2004, all vehicles by 2008(?) The plug is the same for CAN
vehicles, the software is different. The plain OBD II would work for my
current vehicles, just seemed silly to buy something that would not work
for any new vehicles. Price was about double to get the CAN capability,
didn't buy anything.

A plain OBDII reader should be fine for all your vehicles with the
possible exception of the 2006 Nissan.

I was looking at the IEQUUS products, all CAN capable, didn't buy one.
http://www.iequus.com/products.php?category_id=1_10_7

twaldron wrote:
> Not they way I was understanding the 9145 Scanner...are you talking
> about the 9175 Reader...not that it matters? I need this to read 1997
> Ford, 2001 Jeep, 2003 Jeep, and 2006 Nissan. I believe they are all
> OBC-II past 1996. Don't know why 2004-2006 would be any different.
> Please explain.
>
> tw
>
> RoyJ wrote:
>
>> Does not say it is upgradable to the CAN protocols. Won't work on
>> anything from 2004 (?) and up.
>> http://www.actron.com/publish/2006/0...atsnew_1_6.pdf
>>
>> Outatime wrote:
>>
>>> twaldron wrote:
>>>
>>>> Ah, I just went with a Actron CP9145....no PC stuff but portable.
>
>

twaldron

Thanks for the explanation. This is why it's taken me so long to pull
the trigger. I'll take a look at the IEQUUS as I've not heard of that
one. I really need it to read the Nissan, so maybe I jumped too soon
even with all the hesitation. Technology....

RoyJ wrote:
> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I did a google search, was not coming up with anything definitive. I was
> looking at buying a scanner last summer (working a problem with another
> vehicle). My research said that OBD I was a '80's to 1995 vintage
> system, plain OBD II was mid 90's (depends on what vehicle), the CAN
> system (Controller Area Network) protocol was introduced on SOME
> vehicles in 2004, all vehicles by 2008(?) The plug is the same for CAN
> vehicles, the software is different. The plain OBD II would work for my
> current vehicles, just seemed silly to buy something that would not work
> for any new vehicles. Price was about double to get the CAN capability,
> didn't buy anything.
>
> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I was looking at the IEQUUS products, all CAN capable, didn't buy one.
> http://www.iequus.com/products.php?category_id=1_10_7
>
> twaldron wrote:
>
>> Not they way I was understanding the 9145 Scanner...are you talking
>> about the 9175 Reader...not that it matters? I need this to read 1997
>> Ford, 2001 Jeep, 2003 Jeep, and 2006 Nissan. I believe they are all
>> OBC-II past 1996. Don't know why 2004-2006 would be any different.
>> Please explain.
>>
>> tw
>>
>> RoyJ wrote:
>>
>>> Does not say it is upgradable to the CAN protocols. Won't work on
>>> anything from 2004 (?) and up.
>>> http://www.actron.com/publish/2006/0...atsnew_1_6.pdf
>>>
>>> Outatime wrote:
>>>
>>>> twaldron wrote:
>>>>
>>>>> Ah, I just went with a Actron CP9145....no PC stuff but portable.
>>
>>
>>


--
__________________________________________________ ___________________
2003 TJ Rubicon * 2001 XJ Sport * 1971 Bill Stroppe Baja Bronco

"There is a very fine line between 'hobby' and 'mental illness'."

Pronunciation: 'jEp Function: noun Date: 1940

Etymology: from g. p. (G= 'Government' P= '80 inch wheelbase')
A small general-purpose motor vehicle with 80" wheelbase, 1/4-ton
capacity and four-wheel drive used by the U.S. army in World War II.
__________________________________________________ ___________________

twaldron

Thanks for the explanation. This is why it's taken me so long to pull
the trigger. I'll take a look at the IEQUUS as I've not heard of that
one. I really need it to read the Nissan, so maybe I jumped too soon
even with all the hesitation. Technology....

RoyJ wrote:
> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I did a google search, was not coming up with anything definitive. I was
> looking at buying a scanner last summer (working a problem with another
> vehicle). My research said that OBD I was a '80's to 1995 vintage
> system, plain OBD II was mid 90's (depends on what vehicle), the CAN
> system (Controller Area Network) protocol was introduced on SOME
> vehicles in 2004, all vehicles by 2008(?) The plug is the same for CAN
> vehicles, the software is different. The plain OBD II would work for my
> current vehicles, just seemed silly to buy something that would not work
> for any new vehicles. Price was about double to get the CAN capability,
> didn't buy anything.
>
> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I was looking at the IEQUUS products, all CAN capable, didn't buy one.
> http://www.iequus.com/products.php?category_id=1_10_7
>
> twaldron wrote:
>
>> Not they way I was understanding the 9145 Scanner...are you talking
>> about the 9175 Reader...not that it matters? I need this to read 1997
>> Ford, 2001 Jeep, 2003 Jeep, and 2006 Nissan. I believe they are all
>> OBC-II past 1996. Don't know why 2004-2006 would be any different.
>> Please explain.
>>
>> tw
>>
>> RoyJ wrote:
>>
>>> Does not say it is upgradable to the CAN protocols. Won't work on
>>> anything from 2004 (?) and up.
>>> http://www.actron.com/publish/2006/0...atsnew_1_6.pdf
>>>
>>> Outatime wrote:
>>>
>>>> twaldron wrote:
>>>>
>>>>> Ah, I just went with a Actron CP9145....no PC stuff but portable.
>>
>>
>>


--
__________________________________________________ ___________________
2003 TJ Rubicon * 2001 XJ Sport * 1971 Bill Stroppe Baja Bronco

"There is a very fine line between 'hobby' and 'mental illness'."

Pronunciation: 'jEp Function: noun Date: 1940

Etymology: from g. p. (G= 'Government' P= '80 inch wheelbase')
A small general-purpose motor vehicle with 80" wheelbase, 1/4-ton
capacity and four-wheel drive used by the U.S. army in World War II.
__________________________________________________ ___________________

twaldron

Thanks for the explanation. This is why it's taken me so long to pull
the trigger. I'll take a look at the IEQUUS as I've not heard of that
one. I really need it to read the Nissan, so maybe I jumped too soon
even with all the hesitation. Technology....

RoyJ wrote:
> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I did a google search, was not coming up with anything definitive. I was
> looking at buying a scanner last summer (working a problem with another
> vehicle). My research said that OBD I was a '80's to 1995 vintage
> system, plain OBD II was mid 90's (depends on what vehicle), the CAN
> system (Controller Area Network) protocol was introduced on SOME
> vehicles in 2004, all vehicles by 2008(?) The plug is the same for CAN
> vehicles, the software is different. The plain OBD II would work for my
> current vehicles, just seemed silly to buy something that would not work
> for any new vehicles. Price was about double to get the CAN capability,
> didn't buy anything.
>
> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I was looking at the IEQUUS products, all CAN capable, didn't buy one.
> http://www.iequus.com/products.php?category_id=1_10_7
>
> twaldron wrote:
>
>> Not they way I was understanding the 9145 Scanner...are you talking
>> about the 9175 Reader...not that it matters? I need this to read 1997
>> Ford, 2001 Jeep, 2003 Jeep, and 2006 Nissan. I believe they are all
>> OBC-II past 1996. Don't know why 2004-2006 would be any different.
>> Please explain.
>>
>> tw
>>
>> RoyJ wrote:
>>
>>> Does not say it is upgradable to the CAN protocols. Won't work on
>>> anything from 2004 (?) and up.
>>> http://www.actron.com/publish/2006/0...atsnew_1_6.pdf
>>>
>>> Outatime wrote:
>>>
>>>> twaldron wrote:
>>>>
>>>>> Ah, I just went with a Actron CP9145....no PC stuff but portable.
>>
>>
>>


--
__________________________________________________ ___________________
2003 TJ Rubicon * 2001 XJ Sport * 1971 Bill Stroppe Baja Bronco

"There is a very fine line between 'hobby' and 'mental illness'."

Pronunciation: 'jEp Function: noun Date: 1940

Etymology: from g. p. (G= 'Government' P= '80 inch wheelbase')
A small general-purpose motor vehicle with 80" wheelbase, 1/4-ton
capacity and four-wheel drive used by the U.S. army in World War II.
__________________________________________________ ___________________

twaldron

Ok. I called Actron and they said all CP9145s from 2005 and up are CAN
compatible and have newer software installed. Since I'm ordering new
there is little to no chance that I'd receive and older model unless it
gets pulled from some really old stock. Also, their site says this for
the 9145:

- Tool is fully upgradeable, accommodating future vehicles (including
C.A.N.)

Which is nice! :) So, I should be good to go on the '06 Nissan too. It
was $188 shipped, so that's not too bad. I can pay that off with a
couple of Check Engine lights.

Those IEQUUS products look really nice as well, and are about the same
price for the top end ones. ($199)

Thanks for your input.

tw

RoyJ wrote:

> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I did a google search, was not coming up with anything definitive. I was
> looking at buying a scanner last summer (working a problem with another
> vehicle). My research said that OBD I was a '80's to 1995 vintage
> system, plain OBD II was mid 90's (depends on what vehicle), the CAN
> system (Controller Area Network) protocol was introduced on SOME
> vehicles in 2004, all vehicles by 2008(?) The plug is the same for CAN
> vehicles, the software is different. The plain OBD II would work for my
> current vehicles, just seemed silly to buy something that would not work
> for any new vehicles. Price was about double to get the CAN capability,
> didn't buy anything.
>
> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I was looking at the IEQUUS products, all CAN capable, didn't buy one.
> http://www.iequus.com/products.php?category_id=1_10_7
>
> twaldron wrote:
>
>> Not they way I was understanding the 9145 Scanner...are you talking
>> about the 9175 Reader...not that it matters? I need this to read 1997
>> Ford, 2001 Jeep, 2003 Jeep, and 2006 Nissan. I believe they are all
>> OBC-II past 1996. Don't know why 2004-2006 would be any different.
>> Please explain.
>>
>> tw
>>
>> RoyJ wrote:
>>
>>> Does not say it is upgradable to the CAN protocols. Won't work on
>>> anything from 2004 (?) and up.
>>> http://www.actron.com/publish/2006/0...atsnew_1_6.pdf
>>>
>>> Outatime wrote:
>>>
>>>> twaldron wrote:
>>>>
>>>>> Ah, I just went with a Actron CP9145....no PC stuff but portable.
>>
>>
>>


--
__________________________________________________ ___________________
2003 TJ Rubicon * 2001 XJ Sport * 1971 Bill Stroppe Baja Bronco

"There is a very fine line between 'hobby' and 'mental illness'."

Pronunciation: 'jEp Function: noun Date: 1940

Etymology: from g. p. (G= 'Government' P= '80 inch wheelbase')
A small general-purpose motor vehicle with 80" wheelbase, 1/4-ton
capacity and four-wheel drive used by the U.S. army in World War II.
__________________________________________________ ___________________

twaldron

Ok. I called Actron and they said all CP9145s from 2005 and up are CAN
compatible and have newer software installed. Since I'm ordering new
there is little to no chance that I'd receive and older model unless it
gets pulled from some really old stock. Also, their site says this for
the 9145:

- Tool is fully upgradeable, accommodating future vehicles (including
C.A.N.)

Which is nice! :) So, I should be good to go on the '06 Nissan too. It
was $188 shipped, so that's not too bad. I can pay that off with a
couple of Check Engine lights.

Those IEQUUS products look really nice as well, and are about the same
price for the top end ones. ($199)

Thanks for your input.

tw

RoyJ wrote:

> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I did a google search, was not coming up with anything definitive. I was
> looking at buying a scanner last summer (working a problem with another
> vehicle). My research said that OBD I was a '80's to 1995 vintage
> system, plain OBD II was mid 90's (depends on what vehicle), the CAN
> system (Controller Area Network) protocol was introduced on SOME
> vehicles in 2004, all vehicles by 2008(?) The plug is the same for CAN
> vehicles, the software is different. The plain OBD II would work for my
> current vehicles, just seemed silly to buy something that would not work
> for any new vehicles. Price was about double to get the CAN capability,
> didn't buy anything.
>
> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I was looking at the IEQUUS products, all CAN capable, didn't buy one.
> http://www.iequus.com/products.php?category_id=1_10_7
>
> twaldron wrote:
>
>> Not they way I was understanding the 9145 Scanner...are you talking
>> about the 9175 Reader...not that it matters? I need this to read 1997
>> Ford, 2001 Jeep, 2003 Jeep, and 2006 Nissan. I believe they are all
>> OBC-II past 1996. Don't know why 2004-2006 would be any different.
>> Please explain.
>>
>> tw
>>
>> RoyJ wrote:
>>
>>> Does not say it is upgradable to the CAN protocols. Won't work on
>>> anything from 2004 (?) and up.
>>> http://www.actron.com/publish/2006/0...atsnew_1_6.pdf
>>>
>>> Outatime wrote:
>>>
>>>> twaldron wrote:
>>>>
>>>>> Ah, I just went with a Actron CP9145....no PC stuff but portable.
>>
>>
>>


--
__________________________________________________ ___________________
2003 TJ Rubicon * 2001 XJ Sport * 1971 Bill Stroppe Baja Bronco

"There is a very fine line between 'hobby' and 'mental illness'."

Pronunciation: 'jEp Function: noun Date: 1940

Etymology: from g. p. (G= 'Government' P= '80 inch wheelbase')
A small general-purpose motor vehicle with 80" wheelbase, 1/4-ton
capacity and four-wheel drive used by the U.S. army in World War II.
__________________________________________________ ___________________

twaldron

Ok. I called Actron and they said all CP9145s from 2005 and up are CAN
compatible and have newer software installed. Since I'm ordering new
there is little to no chance that I'd receive and older model unless it
gets pulled from some really old stock. Also, their site says this for
the 9145:

- Tool is fully upgradeable, accommodating future vehicles (including
C.A.N.)

Which is nice! :) So, I should be good to go on the '06 Nissan too. It
was $188 shipped, so that's not too bad. I can pay that off with a
couple of Check Engine lights.

Those IEQUUS products look really nice as well, and are about the same
price for the top end ones. ($199)

Thanks for your input.

tw

RoyJ wrote:

> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I did a google search, was not coming up with anything definitive. I was
> looking at buying a scanner last summer (working a problem with another
> vehicle). My research said that OBD I was a '80's to 1995 vintage
> system, plain OBD II was mid 90's (depends on what vehicle), the CAN
> system (Controller Area Network) protocol was introduced on SOME
> vehicles in 2004, all vehicles by 2008(?) The plug is the same for CAN
> vehicles, the software is different. The plain OBD II would work for my
> current vehicles, just seemed silly to buy something that would not work
> for any new vehicles. Price was about double to get the CAN capability,
> didn't buy anything.
>
> A plain OBDII reader should be fine for all your vehicles with the
> possible exception of the 2006 Nissan.
>
> I was looking at the IEQUUS products, all CAN capable, didn't buy one.
> http://www.iequus.com/products.php?category_id=1_10_7
>
> twaldron wrote:
>
>> Not they way I was understanding the 9145 Scanner...are you talking
>> about the 9175 Reader...not that it matters? I need this to read 1997
>> Ford, 2001 Jeep, 2003 Jeep, and 2006 Nissan. I believe they are all
>> OBC-II past 1996. Don't know why 2004-2006 would be any different.
>> Please explain.
>>
>> tw
>>
>> RoyJ wrote:
>>
>>> Does not say it is upgradable to the CAN protocols. Won't work on
>>> anything from 2004 (?) and up.
>>> http://www.actron.com/publish/2006/0...atsnew_1_6.pdf
>>>
>>> Outatime wrote:
>>>
>>>> twaldron wrote:
>>>>
>>>>> Ah, I just went with a Actron CP9145....no PC stuff but portable.
>>
>>
>>


--
__________________________________________________ ___________________
2003 TJ Rubicon * 2001 XJ Sport * 1971 Bill Stroppe Baja Bronco

"There is a very fine line between 'hobby' and 'mental illness'."

Pronunciation: 'jEp Function: noun Date: 1940

Etymology: from g. p. (G= 'Government' P= '80 inch wheelbase')
A small general-purpose motor vehicle with 80" wheelbase, 1/4-ton
capacity and four-wheel drive used by the U.S. army in World War II.
__________________________________________________ ___________________

Jeff Strickland

"RoyJ" <spamless@microsoft.net> wrote in message
news:Dwhbh.4667$ql2.3428@newsread3.news.pas.earthl ink.net...
>A plain OBDII reader should be fine for all your vehicles with the possible
>exception of the 2006 Nissan.
>
> I did a google search, was not coming up with anything definitive. I was
> looking at buying a scanner last summer (working a problem with another
> vehicle). My research said that OBD I was a '80's to 1995 vintage system,
> plain OBD II was mid 90's (depends on what vehicle), the CAN system
> (Controller Area Network) protocol was introduced on SOME vehicles in
> 2004, all vehicles by 2008(?)

OBD II was required on all passenger cars and light trucks offered for sale
in the USA since 1996. There are a small number of cars and trucks that had
OBD II capability from 1995, but that is more of a production issue with the
automaker than compliance to the law. The law says it is not required until
'96 production.

I tend to stay pretty close to this sort of stuff, and I am not aware of a
move away from OBD II. Certainly, there are conventions that are better, and
CAN has been around for a very long time. I'm pretty sure that CAN serves a
different purpose than OBD II, and finding a new CAN is certainly possible
without any change to the diagnostic interface of OBD II.

Jeff Strickland

"RoyJ" <spamless@microsoft.net> wrote in message
news:Dwhbh.4667$ql2.3428@newsread3.news.pas.earthl ink.net...
>A plain OBDII reader should be fine for all your vehicles with the possible
>exception of the 2006 Nissan.
>
> I did a google search, was not coming up with anything definitive. I was
> looking at buying a scanner last summer (working a problem with another
> vehicle). My research said that OBD I was a '80's to 1995 vintage system,
> plain OBD II was mid 90's (depends on what vehicle), the CAN system
> (Controller Area Network) protocol was introduced on SOME vehicles in
> 2004, all vehicles by 2008(?)

OBD II was required on all passenger cars and light trucks offered for sale
in the USA since 1996. There are a small number of cars and trucks that had
OBD II capability from 1995, but that is more of a production issue with the
automaker than compliance to the law. The law says it is not required until
'96 production.

I tend to stay pretty close to this sort of stuff, and I am not aware of a
move away from OBD II. Certainly, there are conventions that are better, and
CAN has been around for a very long time. I'm pretty sure that CAN serves a
different purpose than OBD II, and finding a new CAN is certainly possible
without any change to the diagnostic interface of OBD II.