OBD II interface issue
OBD II interface issue
I have a 2007.5 SRW 3500 4x4 6.7 CTD built 4/07. I have no cel but I was checking to see if my older actron OBDII diagnostic tester would interface with the PCM. Following the proper testing sequence I get error 8888 flashing (no PCM interface).
I have no reason to believe the tester has continuity problems as it worked fine last month. I repaired my POS Ford F-250 after it decided to blow a spark plug out of the cylinder head. The tester read & subsequently cleared the myriad of codes that situation caused.
My owners manual states OBDII compliant...but it also references a 5.9 CTD. Is my truck OBDIII? If not, any suggestions welcome.
Thanks
I have no reason to believe the tester has continuity problems as it worked fine last month. I repaired my POS Ford F-250 after it decided to blow a spark plug out of the cylinder head. The tester read & subsequently cleared the myriad of codes that situation caused.
My owners manual states OBDII compliant...but it also references a 5.9 CTD. Is my truck OBDIII? If not, any suggestions welcome.
Thanks
I have a 2007.5 SRW 3500 4x4 6.7 CTD built 4/07. I have no cel but I was checking to see if my older actron OBDII diagnostic tester would interface with the PCM. Following the proper testing sequence I get error 8888 flashing (no PCM interface).
I have no reason to believe the tester has continuity problems as it worked fine last month. I repaired my POS Ford F-250 after it decided to blow a spark plug out of the cylinder head. The tester read & subsequently cleared the myriad of codes that situation caused.
My owners manual states OBDII compliant...but it also references a 5.9 CTD. Is my truck OBDIII? If not, any suggestions welcome.
Thanks
I have no reason to believe the tester has continuity problems as it worked fine last month. I repaired my POS Ford F-250 after it decided to blow a spark plug out of the cylinder head. The tester read & subsequently cleared the myriad of codes that situation caused.
My owners manual states OBDII compliant...but it also references a 5.9 CTD. Is my truck OBDIII? If not, any suggestions welcome.
Thanks
I think mine is model #175 , the older ones will not work on the newer trucks
Thanks for the help. I bought the code reader in 2000, so I'm sure that is the issue. What is the CAN Bus? Diesel specific, or just new technology (reason to sell more tools)?
I forget what it stands for but I am sure someone more knowledgeable will chime in with the correct answer.
Autozone has the scanners. I think they run around $160 or so.
I got mine from ebay. Think it was around $110.
If you are only looking for an inexpensive scan reader look at Harbor Freight. They recently had a can bus OBDII reader for around $50 dollars. It isn't clear in the ad for it but it will read and clear codes. Bought mine last year and works fine on my 07 5.9.
You should be able to check in the engine compartment for an emissions sticker that will verify your vehicle's interface.
ODBII scaners will connect to the Duramax, Cummins, and Powerstroke diesel vehicles; however, because their gross vehicle weight exceeds the maximum requirements of the OBDII standard, they are not OBDII compliant and a very limited amount of data and sensors will report with generic OBDII. However, with optional enhanced interfaces, the proprietary powertrain and other systems sensors are available.
CAN is short for Controller Area Network. It will be the required electrical interface for all vehicles beginning in the model year of 2008. Some vendors began using CAN in the model year of 2004. (the connector is the same BTW)
I think Chrysler adopted the CAN OBD-II protocol for their newer ‘05+ vehicles. Some ODB-II scanners can also communicate with CAN vehicles, some can't.
I don't think anything mass produced has ODBIII yet. Its still in regulation talk as far as I know.
ODBII scaners will connect to the Duramax, Cummins, and Powerstroke diesel vehicles; however, because their gross vehicle weight exceeds the maximum requirements of the OBDII standard, they are not OBDII compliant and a very limited amount of data and sensors will report with generic OBDII. However, with optional enhanced interfaces, the proprietary powertrain and other systems sensors are available.
CAN is short for Controller Area Network. It will be the required electrical interface for all vehicles beginning in the model year of 2008. Some vendors began using CAN in the model year of 2004. (the connector is the same BTW)
I think Chrysler adopted the CAN OBD-II protocol for their newer ‘05+ vehicles. Some ODB-II scanners can also communicate with CAN vehicles, some can't.
I don't think anything mass produced has ODBIII yet. Its still in regulation talk as far as I know.
Trending Topics
ODBII scaners will connect to the Duramax, Cummins, and Powerstroke diesel vehicles; however, because their gross vehicle weight exceeds the maximum requirements of the OBDII standard, they are not OBDII compliant and a very limited amount of data and sensors will report with generic OBDII. However, with optional enhanced interfaces, the proprietary powertrain and other systems sensors are available.
not really...the PSD, ctd and dmax ARE fully OBD II compliant. Only EPA-related codes are required to be reported through generic code readers, and this is true for ALL vehicles and diesel pickups as well. These are the P0xxx codes. P1xxx codes are manufacturer specific and do not have to be reported to generic code readers because they dont concern the EPA. For example the EPA wants any code reader to know that your EGR isnt functioning properly, but could care less if your oil pressure sensor has a short circuit.
The reason the newest diesels dont work with old code readers, is, because everyone said, the new CAN-bus, usually based on a SAE J1939 standard, is not compatible with the previously accepted J-1979 standard for OBD II. "J-1979" denotes what kind of OBD connector plug must be used, what data busses must exist, and what codes MUST be reported to generic code readers (EPA P0xxx codes). Up until (2003 I think it was??), ECM's HAD to report these generic EPA codes and general basic EPA data (throttle %, fuel, MAP, emmissions, etc) over an old slow data bus, either ISO 9091 (aisian/european codes), J1850VPW (GM), J1850PWM (ford), or keyword (something like that for chrysler, I forget)...
BUT as vehicles became more complex and ECM's became smarter, the companies started to abandon these slow data busses because they werent worth keeping around. Some manufacturers kept the slow data bus for the sole purpose of OBD compliance, and used a high speed data bus for everything else in the vehicle.
BUT finally in 2007 model year vehicles (I think it was 07), the EPA modified the J1979 OBD standards to allow manufacturers to use a common CAN-bus data bus (in place of the slow old data busses) for reporting generic EPA codes and EPA data......so thats why for the newest vehicles (ALL new 2007+ vehicles, not just HD diesel trucks), you need to have a generic code reader that is CAN-bus compatible. Sometime in the next couple years they are going to come out with a whole new OBD standard (rather than continue to revise and jury rig the J1979 OBD II standard) that will require the CAN-bus, as well as several other new features................
hope that helps
ben
Thread
Thread Starter
Forum
Replies
Last Post
greenone
3rd Generation Ram - Non Drivetrain - All Years
2
Aug 26, 2008 08:16 AM
TreeFarm
3rd Gen High Performance and Accessories (5.9L Only)
7
Mar 5, 2008 04:09 PM



