7.3L PIDs for 2016 - Torque Pro and others.
#121
Well, thank you for all of the help and info. It is much appreciated. If you can find your tutorial on the cups, I'd greatly appreciate it, more info I have, better off I am.....I know now, clean is with brushes and acetone, but still would take more info.
What all mods do you have on your truck?
What all mods do you have on your truck?
#122
#124
#127
Here is the info from the first post on this thread, and a typo will make it not work:
Long name:Barometer
Short name: BARO
PID: 221442
Max/Min: 15.0/10.0
Unit: PSI
Equation: ((A*256)+B)*0.03625
Header: C410F1
You also need to go into your Torque Pro general settings to tell it to read things like PSI instead of Kpa, MPH instead of KPH, etc...
Long name:Barometer
Short name: BARO
PID: 221442
Max/Min: 15.0/10.0
Unit: PSI
Equation: ((A*256)+B)*0.03625
Header: C410F1
You also need to go into your Torque Pro general settings to tell it to read things like PSI instead of Kpa, MPH instead of KPH, etc...
#128
Hoping for a little help and direction to figure out what I am doing wrong.
This is my boost equation that was in the downloaded extended pids and seems to work.
Equation: (((A*256)+B)*0.03625)-BARO()
This is my exhaust equation that also seems to work
Equation: (((A*256)+B)*0.03625)-BARO()
for the life of me I can not get the following to work. Both seem to just give the same results as exhaust pressure absolute value.
(Exhaust Gauge Pressure variation) Equation: (((A*256)+B)*0.03625)-[221442]
(Turbo Pressure "Delta" or "Differential" variation) Equation: (((A*256)+B)*0.03625)-[221440]
I did just realize that I am using "EBP" for the short name rather than "EGP" or "TPD" since I was editing the existing pid rather than creating new. Not sure if that is what it is?
This is my boost equation that was in the downloaded extended pids and seems to work.
Equation: (((A*256)+B)*0.03625)-BARO()
This is my exhaust equation that also seems to work
Equation: (((A*256)+B)*0.03625)-BARO()
for the life of me I can not get the following to work. Both seem to just give the same results as exhaust pressure absolute value.
(Exhaust Gauge Pressure variation) Equation: (((A*256)+B)*0.03625)-[221442]
(Turbo Pressure "Delta" or "Differential" variation) Equation: (((A*256)+B)*0.03625)-[221440]
I did just realize that I am using "EBP" for the short name rather than "EGP" or "TPD" since I was editing the existing pid rather than creating new. Not sure if that is what it is?
#129
#130
I think I have it figured out but with a different solution. Have not driven it yet. TPD
I accidentally left PID blank and got values with the above formula from first post but was negative 8 key on engine off.
Tried simply exhaust minus map.
Numbers add up within 0.3 psi.
Any clue why this worked if it did but not the formulas in the first post? Possibly an update to the ap?
I accidentally left PID blank and got values with the above formula from first post but was negative 8 key on engine off.
Tried simply exhaust minus map.
Numbers add up within 0.3 psi.
Any clue why this worked if it did but not the formulas in the first post? Possibly an update to the ap?
#131
First, using BARO () is a callout to the barometer within the portable device, which many do not have. TP will then use sea level as the BARO value, which works pretty good at lower elevations. However... a trip to Salt Lake City, Denver, or the whole state of Montana will throw the readings into some weird results.
Another thing... I programmed everything in, including BARO - but I don't select BARO for a gauge. The key thing is to have BARO defined so TP has something to call. If I have the EBP formula with a call for 221442, but I didn't have the formula for 221442 - it would just use some raw data that the PCM spits out.
221445-221440 will take the raw data from the EBP and subtract the raw data from the MAP. If no conversion to the data is needed to get Kpa or PSI, then this will work just fine. If the raw data needs conversion, then this will give numbers that are confusing. I've been looking at some information on the sensors recently, and I am led to believe the raw numbers are in Kpa, and it's a simple matter the app converting it to PSI. This could very well be a change in the app.
As for the naming, it is absolutely crucial that the correct long name and PID number are exact without typos or the PCM freaks out. The short name is for your reference only, and it's helpful to have similar PIDs (EBP, EGP, TPD) short-named in a way that you remember what you did to the formula.
Another thing... I programmed everything in, including BARO - but I don't select BARO for a gauge. The key thing is to have BARO defined so TP has something to call. If I have the EBP formula with a call for 221442, but I didn't have the formula for 221442 - it would just use some raw data that the PCM spits out.
221445-221440 will take the raw data from the EBP and subtract the raw data from the MAP. If no conversion to the data is needed to get Kpa or PSI, then this will work just fine. If the raw data needs conversion, then this will give numbers that are confusing. I've been looking at some information on the sensors recently, and I am led to believe the raw numbers are in Kpa, and it's a simple matter the app converting it to PSI. This could very well be a change in the app.
As for the naming, it is absolutely crucial that the correct long name and PID number are exact without typos or the PCM freaks out. The short name is for your reference only, and it's helpful to have similar PIDs (EBP, EGP, TPD) short-named in a way that you remember what you did to the formula.
#132
First, using BARO () is a callout to the barometer within the portable device, which many do not have. TP will then use sea level as the BARO value, which works pretty good at lower elevations. However... a trip to Salt Lake City, Denver, or the whole state of Montana will throw the readings into some weird results.
Another thing... I programmed everything in, including BARO - but I don't select BARO for a gauge. The key thing is to have BARO defined so TP has something to call. If I have the EBP formula with a call for 221442, but I didn't have the formula for 221442 - it would just use some raw data that the PCM spits out.
221445-221440 will take the raw data from the EBP and subtract the raw data from the MAP. If no conversion to the data is needed to get Kpa or PSI, then this will work just fine. If the raw data needs conversion, then this will give numbers that are confusing. I've been looking at some information on the sensors recently, and I am led to believe the raw numbers are in Kpa, and it's a simple matter the app converting it to PSI. This could very well be a change in the app.
As for the naming, it is absolutely crucial that the correct long name and PID number are exact without typos or the PCM freaks out. The short name is for your reference only, and it's helpful to have similar PIDs (EBP, EGP, TPD) short-named in a way that you remember what you did to the formula.
Another thing... I programmed everything in, including BARO - but I don't select BARO for a gauge. The key thing is to have BARO defined so TP has something to call. If I have the EBP formula with a call for 221442, but I didn't have the formula for 221442 - it would just use some raw data that the PCM spits out.
221445-221440 will take the raw data from the EBP and subtract the raw data from the MAP. If no conversion to the data is needed to get Kpa or PSI, then this will work just fine. If the raw data needs conversion, then this will give numbers that are confusing. I've been looking at some information on the sensors recently, and I am led to believe the raw numbers are in Kpa, and it's a simple matter the app converting it to PSI. This could very well be a change in the app.
As for the naming, it is absolutely crucial that the correct long name and PID number are exact without typos or the PCM freaks out. The short name is for your reference only, and it's helpful to have similar PIDs (EBP, EGP, TPD) short-named in a way that you remember what you did to the formula.
Ok thanks that makes some sense. I downloaded the PIDS within the torque pro app for Ford then tried adding a few.
I am assuming I need to do this to "program" baro like you state above? :
Long name:Barometer
Short name: BARO
PID: 221442
Max/Min: 15.0/10.0
Unit: PSI
Equation: ((A*256)+B)*0.03625
Header: C410F1
The Min/Max values above are for realistic altitudes, but those who traverse the Rockies may see lees than 10 PSI (over 10,000 feet). If you do, you can change the Max/Min to 15.0/9.0.
Then I can use it here:
Boost
(AKA Manifold Gauge Pressure)
Short Name: Boost
PID: 221440
Units: PSI
Max/Min: 30.0/0.0 (stock) 40.0/0.0 (performance)
Equation: (((A*256)+B)*0.03625)-[221442]
"-[221442]" subtracts the Barometric sensor (located on the PCM on some trucks, external on others) reading from the MAP reading - and this gives you just the boost pressure above atmospheric pressure.
#134