2017 Ford 7.3L Powerstroke Enhanced PIDs
#1
#3
The memory addresses above (22 plus four digits in the number under "PID") work on SD diesels, not OBS 7.3Ls. They can work on SD 7.3L, 6.0L, and it's my understanding they may even go right on through to the 6.7L. However, the 6.0L has more PIDs than the 7.3L, the 6.4L more than the 6.0L, and so on. Saying that, the header changes when going from one engine to the next.
That's the primer, now some of the many, many caveats:
That's the primer, now some of the many, many caveats:
- Not all of the math has been worked out and perfected, there are many stages of development at play here. Feel free to tinker, verify, and share your results.
- What works in one tune doesn't always work in another tune - be mindful of that.
- Some of my formulas either tackle a whole new task ("Virtual" gauge, like TPD), or compensate for the differences in my highly-modified truck.
- Some of the PIDs are not direct readings from a sensor - but they are a command to a control, and there may or may not be a sensor to confirm the control took place. IPR is a command with ICP sensor to confirm. Torque Converter Line Pressure is a control without a confirming pressure sensor.
- Many gauges use the math to arrive at a number that needs to be converted (like Kpa or degrees C), it is then up to the settings in the app to automatically convert them to F or PSI for you.
- Many devices with a % output can be easily altered to get a reading that makes more sense to you. Fuel level is a perfect example. If I want % fuel remaining, I can use (100/255)*A - or 0.3922*A - or A/2.55 may be easier to type into the formula. If I want the result to show an actual number that makes sense to me - my tank is 39 gallons (with Hutch/Harpoon mod). (39/255)*A or 0.149*A will give me gallons remaining (assuming I didn't screw up the arm on my fuel sender float). (147/255)*A or 0.5764*A will give me fuel remaining in liters. But then again... maybe you can do the liter thing in the formula and let the app convert it to gallons - I don't know. This is one of the many things that can be tinkered with by those with a curious mind - then shared here.
#5
#6
I'm always tinkering with the math. Sometimes I learn something new that prompts me to change the math (even though the change in accuracy may be so little you wouldn't spot it), sometimes I just convert the math to something easier to type, and sometimes I change the scale (like the FIPW) for graphing purposes.
#7
Trending Topics
#8
Odd ball question here. I have the ZF6 manual, and I'm just wondering where all of the auto trans sensor inputs go? TFT, TCSlip, TCLP, OSS, etc. I recently saw one unused connector hanging behind the driver's side wheelwell, and I think there was a plug near the ZF6. Is there a "swtich" in the PCM telling it that I have a ZF6? Just curious...
Never mind... sort of. Just realized there's a different PCM calibration for manual trans trucks.
Never mind... sort of. Just realized there's a different PCM calibration for manual trans trucks.
Last edited by SaintITC; 02-18-2017 at 08:33 AM. Reason: for before morning coffee...
#10
For some reason the TCSlip does not work on my truck, stays at zero. For now I laid the Ford one from the pre-defined list for Powerstroke on top of it and that one does work. Hopefully it is accurate. Leaving for the mountains of Northern NM tomorrow towing 7K and just loaded my new Galaxy tablet, mainly will be watching TFT and EOT. thanks for all your hard work Rich.
#11
Join Date: Mar 2015
Location: Blairsville, Pennsylvania
Posts: 5,277
Likes: 0
Received 26 Likes
on
26 Posts
For some reason the TCSlip does not work on my truck, stays at zero. For now I laid the Ford one from the pre-defined list for Powerstroke on top of it and that one does work. Hopefully it is accurate. Leaving for the mountains of Northern NM tomorrow towing 7K and just loaded my new Galaxy tablet, mainly will be watching TFT and EOT. thanks for all your hard work Rich.
I don't use RPM on a display in Torque Pro. Also early on, it would mess up the other gauges. Fine for logging, though
Maybe try a different display type and put it on a screen by itself?
When you go to add a display and have the list of available PIDs, is the TCSlip highlighted in Green? If so, that means it is receiving data. If not...
#13
(1996 model)
#14
#15
I need some help trying to get these PIDs into OBDLink for my iOS application.
The problems lie in my trying to use the gauge pressure PIDs which subtract the barometric pressure.
When referring to the BARO PID which is 221442
The PID formula
221445 A - Exhaust Gauge Pressure 0 30 PSI (((A*256)+B)*0.03625)-[221442] ECM EGP
shows as an error when I try and load it into OBDLink app. I think it might be due to how tourque pro reads the pid vaule in the formula vs how my OBDlink reads it.
I am wondering if I can use "READSAEPID" instead of [221442] just as done in the following PID
221310 A - Temperature Differential030*F(((((((A*256)+B)/100)-40)*1.8)+32)-(((readSaePid(05)*1.8)+32)))
Which does load correctly in my app. My only problem is I don't know how to get the READSAEPID to reference the barometric pressure.
Appreciate any help yall may have on this subject. I am actually learning quite a bit by reading through old threads however my handicap is the OBDlink app I'm using doesn't seem to be very popular (however it is highly customizable from a visualization perspective)
The problems lie in my trying to use the gauge pressure PIDs which subtract the barometric pressure.
When referring to the BARO PID which is 221442
The PID formula
221445 A - Exhaust Gauge Pressure 0 30 PSI (((A*256)+B)*0.03625)-[221442] ECM EGP
shows as an error when I try and load it into OBDLink app. I think it might be due to how tourque pro reads the pid vaule in the formula vs how my OBDlink reads it.
I am wondering if I can use "READSAEPID" instead of [221442] just as done in the following PID
221310 A - Temperature Differential030*F(((((((A*256)+B)/100)-40)*1.8)+32)-(((readSaePid(05)*1.8)+32)))
Which does load correctly in my app. My only problem is I don't know how to get the READSAEPID to reference the barometric pressure.
Appreciate any help yall may have on this subject. I am actually learning quite a bit by reading through old threads however my handicap is the OBDlink app I'm using doesn't seem to be very popular (however it is highly customizable from a visualization perspective)