56 PSI sounds more electrical, like an open/shorted wire. The physical limitation of the sensor usually takes the max to 53 PSI, but 56 PSI likely indicates full voltage on the signal line, a missing ground, or the sensor is internally shorted.

 

It looks like we can create our own predefined sets of PIDS. For example I created a file called FTE.csv with the following in it:

[ EDIT ] The only ones that worked (from what I tried) were MAT and BARO. I think the problem was that Auto needed to be added. I've updated the data below.[ /EDIT ]
[ EDIT ] Adding "Auto" for the header seems to have worked. These all produce a number now.[ /EDIT ]
[ EDIT ] Changed prefix to get these to sort at top of pick list. Changed EOT from Degrees C to Degree F. Added Altitude (untested)[ /EDIT ]

Name,"ShortName","ModeAndPID","Equation","Min Value","Max Value","Units","Header"
#FTE_Manifold Air Temperature,"MAT","2216E0","A*(9/5)-38",-10,250,"°F","C410F1"
#FTE_Engine Oil Temperature,"EOT","221310","(((A*256)+B)/100)-40",0.0,250.0,"°C","Auto"
#FTE_Engine Oil TemperatureV2,"EOTV2","221310","(((((A*256)+B)/100)-40)*1.80)+32",0.0,250.0,"°F","Auto"
#FTE_Barometer,"BARO","221442","((A*256)+B)*0.0362 5",10,15,"PSI","C410F1"
#FTE_Manifold Absolute Pressure,"MAP","221440","((A*256)+B)*0.03625",0,45 ,"PSI","Auto"
#FTE_Manifold Gauge Pressure,"Boost","221440","(((A*256)+B)*0.03625)-[221442]",0.0,30.0,PSI,"Auto"
#FTE_Exhaust Back Pressure (Absolute),"EBP","221445","((A*256)+B)*0.03625",0. 0,55.0,PSI,"Auto"
#FTE_Exhaust Gauge Pressure,"EGP","221445","(((A*256)+B)*0.03625)-[221442]",0.0,30.0,"PSI","Auto"
#FTE_Fuel Injector Pulse Width,"FIPW","221410","((A*256)+B)*.008",0.0,6.0,m s,"Auto"
#FTE_Injector Control Pressure,"ICP","221446","((A*256)+B)*.57",0.0,3000 .0,"PSI","Auto"
#FTE_Injector Pressure Regulator (Injector Control Pressure Duty Cycle),"IPR","221434","A*0.39063",0.0,100.0,"%","A uto"
#FTE_Torque Converter Slip,"Slip","2211b8","((A*256)+B)/4",0.0,1000.0,"RPM","Auto"
#FTE_Transmission Fluid Temperature,"TFT","221674","((A*256)+B)/8",0,250,"°F","Auto"
#FTE_Transmission Gear,"Gear","2211b3","A/2",0,4,"Gear","Auto"
#FTE_Altitude,"Alt","221442","(14.7-(((A*256)+B)*0.03625))*2143",0,10000,"ft.",C410F1


I put it in in the .torque/extendedpids folder and it showed up in the "Add predefined set" list. This list is much easier to pick from vs the long list of Ford PIDs in Torque Pro.

Does anyone know if there's a way to get to the other ford definitions so they can be combined into a custom set?

Also, I have **not** checked the above for typos. It's supposed to match the values in the first post of this thread.

 

I downloaded the Ford predefined set of PIDs and altered all the calculations I use. I will eventually come up with some creative combinations to get new reference numbers, to incorporate what I've learned for the sake of a pass/fail number on specific PID combinations. You have done what I have not for a while - get off my butt.

If you click your CP, there's a rep lying in wait.

 

I've update the table above. Most of those did not work. I wasn't able to test them all yet, but it appears as if leaving the last column blank causes a problem. The fix, I hope, is to add "Auto". The only reason I think Auto should work is that seemed to be the only difference in the definition imported in the table and one that was already defined for the same PID in Torque.

I noticed that the EOT formula in this thread is the same as the one in the Torque app, but the torque app is Degrees C and the one above is Degrees F. Doesn't that mean that one is wrong?

 

I would say yes. In the MAT equation you listed above it looks like the sensor reading is being converted from C to F, but the offset is wrong. C to F is F=C*(9/5)+32. I suppose this could mean that the sensor is reporting on the centigrade scale, with 100 degrees between water freezing and boiling, but with some other reference point. And if one sensor reports with centigrade, you could assume they all do, so EOT would also be in C.

Is there a source for all of these equations somewhere?

 

Well, tjmike, you've inspired me to play with torque again. I haven't touched it in months other than reading codes on some of my in-laws' chevys.

 

No real source, it's just what users have developed over time. Don't ask me why the temperature formula works, but it's accurate on Stinky - as confirmed by AE. I don't know if the voltage of the sensor translates directly to degrees C or not, it may need a math function to get C.

 

I tweaked the csv list some, including making so it will sort to the top for selecting gauges.

I'm pretty sure the EOT formula on the first page needs to be Degrees C not Degrees F. That change is reflected in the csv data too. I also added an EOTV2 one to test defining in degrees F. Those two version now match the one already defined in custom Ford PIDs in Torque.

 

I played around with Torque a bit, and under settings /units, there's a switch to report temp in either F or C. So methinks your observation about the EOT equations being the same yet with different results is in error. But as my truck is down at the moment, I can't verify this.

 

Yes, I could have done something wrong, it wouldn't be the first time.

Maybe someone can run a test:

In Torque Settings, go to units and uncheck Use Celsius.

Add these two definitions and try them out at operating temp [EDIT] KOEO - see below [/EDIT]:

Name,"ShortName","ModeAndPID","Equation","Min Value","Max Value","Units","Header"
#EOTc,"EOTc","221310","(((A*256)+B)/100)-40",0.0,250.0,"°C","Auto"
#EOTf,"EOTf","221310","(((A*256)+B)/100)-40",0.0,250.0,"°F","Auto"


See which one seems more reasonable.

 

This is where I interject: Never test a new PID with the engine running. The problems that existed before may have been resolved with app and OS updates, but there was a time when testing a new PID could cause running issues.

 

Since it's a temp sensor, no reason for the engine to be running, KOEO should be fine. I'm only guessing here, but is Torque doing it's temp conversion based on the "Units" field in the definition? By that, the EOTf would report per the equation, but EOTc would get converted post sensor/PID with the Torque settings/units "Use Celsius" unchecked? I can't even check that as my wiring harness is sitting right next to my injectors...

 

Yes. Torque does a conversion based on the units field plus the value you pick in Settings.

You can change the Celsius check box in the settings value on the fly. Torque will do it's conversion on the next incoming sample.

You can also just go into the extended PID section and do edit/test and note the value there.

I edited my test request to be EOEO.

 

Dumb question here but when entering the equations do we change the asterisk to the multiply symbol and the slash to the division symbol?

 

If it's on your keyboard, have at it.