M.Tuner/03 6L/OBDII
Thread Starter
|
Senior Member
Joined: Mar 2001
Posts: 994
Likes: 0
From: Sparks, Nevada
M.Tuner/03 6L/OBDII
Hi
I realize this isn't the diesel bd. and maynot be appropriate or even no one knows, but remembered reading here that tuner could read DTC's, just looking for any input, so......
Has anyone tried or know of someone who has tried to read codes on 03 6L PSD with the tuner or other scan tool..when... SES or ck. e. light is on, indicating a trb. code has been set, but scanner can't read? Or.....
I would assume if no trb. light on, no DTC has been set, so nothing for scan tool to read. Would scan tool indicate no codes found? Would it show (Error) if there was communication prb. between it and PCM or where ever DTC's are stored?
For.. Calif...Mass. 03 6L registered trucks and maybe other states? Would have white sticker near radiator, indicating "Calif. emissions/EPA/OBD II" certified.
Short version...current FMC recall to update OBDII, because maynot be able to read DTC's w/various diagnostic tools.
TIA....OT
I realize this isn't the diesel bd. and maynot be appropriate or even no one knows, but remembered reading here that tuner could read DTC's, just looking for any input, so......
Has anyone tried or know of someone who has tried to read codes on 03 6L PSD with the tuner or other scan tool..when... SES or ck. e. light is on, indicating a trb. code has been set, but scanner can't read? Or.....
I would assume if no trb. light on, no DTC has been set, so nothing for scan tool to read. Would scan tool indicate no codes found? Would it show (Error) if there was communication prb. between it and PCM or where ever DTC's are stored?
For.. Calif...Mass. 03 6L registered trucks and maybe other states? Would have white sticker near radiator, indicating "Calif. emissions/EPA/OBD II" certified.
Short version...current FMC recall to update OBDII, because maynot be able to read DTC's w/various diagnostic tools.
TIA....OT
Former Sponsor
Joined: Mar 1998
Posts: 13,385
Likes: 4
From: Virginia
Hi OT,
You *cannot* use just an OBD-II scan tool and plug it in to read codes in any 6.0 PSD (2003 or 2004) or in the 2004 F-150's, either.
The reason why is because they have the CAN (controller area network) on board, and the scan tool *must* be CAN-compatible - which no Micro Tuner is at this time, though that will change in the future.
So you cannot plug in a Micro Tuner to any 2003 or 2004 6.0 PSD, or any 2004 or newer F-150 either, and read codes - it has to be a CAN-compatible scanner.
The primary problem with OBD-II is that there are no real standards other than the connector itself and the "generic" OBD-II codes, in practical terms, though that is not technically correct. On OBD-II vehicles without CAN, you can plug an OBD-II scan tool in and read codes (when using a Micro Tuner, you must use a Micro Tuner for a Ford to read FoMoCo's, and for a GM you must use a GM version of the Micro Tuner to read OBD-II codes on GM's, and so on). But you usually cannot get any of the manufacturer-specific data without having some type of diagnostic tool that is compatible with each different automakers extended data - otherwise you just get the generic OBD-II basic codes.
When you plug in a scan tool, it generally tells you whether it has connected or not, to any OBD-II vehicle - so you should get some kind of message - just not having any codes doesn't make the scanner inactive, you should get a no codes present message if there were no codes - but that isn't your problem, your problem is that your 6.0 PSD vehicle is CAN, so you need a CAN-capable scanner to read codes.
For example, Ford dealerships using the NGS Star tester had to send them in for a $$$ upgrade to the NGS Plus, which *does* have CAN-capability.
Those using AutoTap version 2.x already have CAN capability built into the hardware, but it's not in the software yet - I just talked to them again yesterday, and they think by March they'll have CAN capability built into the software, too.
The bottom line is, you need a CAN-compatible scan tool to read codes in *any* 6.0 PSD or 2004 or newer F-150 - and, the federal government is requiring that *ALL* vehicles (well, passenger cars & "light" trucks) have CAN by the 2007 model year. Which is nice, as CAN gives higher throughput rates, and you also no longer have problems reading all of the manufacturer-specific extended data - a CAN-compatible scanner can read *all* the manufacturers CAN-equipped vehicles codes, whether they are just standard OBD-II or manufacturer specific is no longer a concern with CAN, thus the main reason all vehicles must have CAN by 2007. Many aftermarket shops have complained bitterly about the fact that OBD-II is not much of a "standard," because you have to have *additional* capabilities beyond just a generic OBD-II code scanner to be able to see any of the extended manufacturer-specific powertrain data.
In short - wait until CAN_compatible scanners get a bit less expensive before trying to buy one for personal use, is my suggestion - and in the meantime, AutoZone scans for vehicle codes free of charge - so you might want to call your local AutoZone and see if their scanner is CAN-compatible in a pinch.
Good luck!
You *cannot* use just an OBD-II scan tool and plug it in to read codes in any 6.0 PSD (2003 or 2004) or in the 2004 F-150's, either.
The reason why is because they have the CAN (controller area network) on board, and the scan tool *must* be CAN-compatible - which no Micro Tuner is at this time, though that will change in the future.
So you cannot plug in a Micro Tuner to any 2003 or 2004 6.0 PSD, or any 2004 or newer F-150 either, and read codes - it has to be a CAN-compatible scanner.
The primary problem with OBD-II is that there are no real standards other than the connector itself and the "generic" OBD-II codes, in practical terms, though that is not technically correct. On OBD-II vehicles without CAN, you can plug an OBD-II scan tool in and read codes (when using a Micro Tuner, you must use a Micro Tuner for a Ford to read FoMoCo's, and for a GM you must use a GM version of the Micro Tuner to read OBD-II codes on GM's, and so on). But you usually cannot get any of the manufacturer-specific data without having some type of diagnostic tool that is compatible with each different automakers extended data - otherwise you just get the generic OBD-II basic codes.
When you plug in a scan tool, it generally tells you whether it has connected or not, to any OBD-II vehicle - so you should get some kind of message - just not having any codes doesn't make the scanner inactive, you should get a no codes present message if there were no codes - but that isn't your problem, your problem is that your 6.0 PSD vehicle is CAN, so you need a CAN-capable scanner to read codes.
For example, Ford dealerships using the NGS Star tester had to send them in for a $$$ upgrade to the NGS Plus, which *does* have CAN-capability.
Those using AutoTap version 2.x already have CAN capability built into the hardware, but it's not in the software yet - I just talked to them again yesterday, and they think by March they'll have CAN capability built into the software, too.
The bottom line is, you need a CAN-compatible scan tool to read codes in *any* 6.0 PSD or 2004 or newer F-150 - and, the federal government is requiring that *ALL* vehicles (well, passenger cars & "light" trucks) have CAN by the 2007 model year. Which is nice, as CAN gives higher throughput rates, and you also no longer have problems reading all of the manufacturer-specific extended data - a CAN-compatible scanner can read *all* the manufacturers CAN-equipped vehicles codes, whether they are just standard OBD-II or manufacturer specific is no longer a concern with CAN, thus the main reason all vehicles must have CAN by 2007. Many aftermarket shops have complained bitterly about the fact that OBD-II is not much of a "standard," because you have to have *additional* capabilities beyond just a generic OBD-II code scanner to be able to see any of the extended manufacturer-specific powertrain data.
In short - wait until CAN_compatible scanners get a bit less expensive before trying to buy one for personal use, is my suggestion - and in the meantime, AutoZone scans for vehicle codes free of charge - so you might want to call your local AutoZone and see if their scanner is CAN-compatible in a pinch.
Good luck!
Thread Starter
|
Senior Member
Joined: Mar 2001
Posts: 994
Likes: 0
From: Sparks, Nevada
Mike my man, you continue to amaze me. 
Tks. for info. That answered all my questions. Certainly an eye opener for me and others that couldnt read codes w/their non CAN scanner. Geez!
OT
Tks. for info. That answered all my questions. Certainly an eye opener for me and others that couldnt read codes w/their non CAN scanner. Geez!
OT
Senior Member
Joined: Feb 2001
Posts: 496
Likes: 0
From: Chicago Burbs
The AutoXRay unit has CAN capability. I recently upgraded mine to the 6000 model through their program. Have no idea on CAN though as my newest vehicle is my 01 SCab.
http://www.autoxray.com/default.htm
http://www.autoxray.com/default.htm