When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Jim, I have the same scantool (OBDLink) and don't believe that the OBDwiz software works well with the 7.3, but I could be wrong. I have used the OBDwiz software on my other 3 vehicles though with great success (Subaru, VW and Mercury).
Let us know what you find out though, you may be a pioneer in using the software for the 7.3 truck.
Jim, I have the same scantool (OBDLink) and don't believe that the OBDwiz software works well with the 7.3, but I could be wrong. I have used the OBDwiz software on my other 3 vehicles though with great success (Subaru, VW and Mercury).
Let us know what you find out though, you may be a pioneer in using the software for the 7.3 truck.
Digging through their forum I found an old post that said it wasn't programmed for use with the 7.3 diesel because these motors weren't OBDII compliant at that time.
I sent a request to find out if they have upgraded the product to facilitate use with my truck. I'll post back when they answer.
Unless a decimal on one of the PIDs is out of place, the HPOI shouldn't go over 1. Even with a decimal out and a result of over 10 - it doesn't look good. John - that's about what your HPOI was before you dropped in an HPOP, unless my memory is slipping from under me.
I remember the discussion and I moved it to be a 1-10 scale, else it disappears on the graph. All tied to the FIPW.
Here is a copy of the (10x) scaled data and one set back to (1x) original scale. The first is much easier to interpret, IMHO. Your calculations, just a 1-10 scale
Original (1x) data scale:
Data for (1x) scale:
Should be the same data interpretation but on a wider scale that fits the other data scales on the graph. Potayto, Potawto
OK... if we're fudging the numbers to fit the scale instead of adapting the scale to match the numbers - that works. I just needed that piece of info.
HPOP is marginal, so it is unknown what would happen if single-shots with big nozzles were thrown in there. I know I would budget for an HPOP if I were planning to power up - just in case.
standard smandard, its all a matter of how you interpret the info....the truck is compliant enough to allow the use of the OBD adapters (thankfully)
Well Yes and No.
The *connector* is OBDII compliant as required by law at that time, but it is NOT OBDII-software/protocol compliant.
You can connect OBDII devices, but you must use the *PWM1850* standard instead of OBDII standard protocol.
That is what we mean when we say it is not OBDII compliant. If your adapter and software do not support PWM1850, it will not connect to the PCM and never will
I had the truck hooked up and running while testing with Forscan and decided to give the OBDwiz a try.
As soon as the program opened my truck died and wouldn't start. Unhooked the OBDwiz and she fired back up again.
I guess until I have the money to invest in something better I will have to stick with the Forscan.
I had the truck hooked up and running while testing with Forscan and decided to give the OBDwiz a try.
As soon as the program opened my truck died and wouldn't start. Unhooked the OBDwiz and she fired back up again.
I guess until I have the money to invest in something better I will have to stick with the Forscan.
Mismatched protocol. The same thing can happen if you have a bad PID in one of the other programs.
Clearing the CEL (DTC) codes often does the same- you should NEVER clear DTCs while the truck is running
You're on the right track.
Torque Lite is free, Torque Pro is...Maybe $5? Under $10, so easy.