Torque App Ford Extended PIDs
#1
Torque App Ford Extended PIDs
I have created these, please take a look and log them in your phone, share with the class on the values you get.... enjoy....
BTW nice forum!
FICM Main Power
FMP
PID: 2209D0
Unit: Volts
Max/Min: 50/0
Equation: ((A*256)+B)*(100/256)/100
FICM Logic Power
FLP
PID: 2209CF
Unit: Volts
Max/Min: 50/0
Equation: ((A*256)+B)*(100/256)/100
FICM Vehicle Power
FVP
PID: 2209CE
Unit: Volts
Max/Min: 50/0
Equation: ((A*256)+B)*(100/256)/100
Fan Speed Sensor
FAN
PID: 22099F
Unit: RPM
Max/Min: 1000/0
Equation: ((A*256)+B)*(1/4)
Injection Control Pressure
HPOP
PID: 221446
Unit: PSI
Max/Min: 5000/0
Equation: ((A*256)+B)*(57/100)
Fuel Pump Duty Cycle
FPDC
PID: 221672
Unit: %
Max/Min: 100/0
Equation: A*100/128
Torque into Torque Converter
TC TQ
PID: 2209CB
Unit: Lb-Ft
Max/Min: 1000/0
Equation: ((A*256)+B)*(1/1)
Engine Oil Temp
EOT
PID: 221310
Unit: Deg. F
Max/Min: 300/0
Equation: ((((A*256)+B)/100)+40)*(9/5)+32
VGT Duty Cycle
VGT
PID: 22096D
%
Max/Min: 100/0
((A*256)+B)*(100/32767)
FUEL LEVEL
FUEL
PID: 2216C1
%
Max/Min: 100/0
((A*256)+B)*(100/328)
This one was fun!!!!!! Its converted into GPH instead of mm^3 per sec.
Volume Fuel Desired
221411
VFD
0.0
50.0
x.1
GPH (gallons per hour)
((((((A*256)+B)*(100/16)/10)*8)*3600)*3785411.78)
AUTO
CYL #1 Cumulative Misfires
22160E
1CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #2 Cumulative Misfires
22160F
2CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #3 Cumulative Misfires
221610
3CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #4 Cumulative Misfires
221611
4CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #5 Cumulative Misfires
221612
5CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #6 Cumulative Misfires
221613
6CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #7 Cumulative Misfires
221614
7CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #8 Cumulative Misfires
221615
8CM
0.0
100.
X1
MISFIRES
((A*256)+B)
Injection Pressure Regulator Duty Cycle
221434
IPR
0.0
100.0
x1
%
(A*13.53)/35
AUTO
Injection Timing BTDC
2209CC
INJ
-50.0
50.0
X1
DEG.
((A*256)+B)*(10/64))/10
AUTO
Battery Voltage
VBatt
221172
0.
16.0
(A/16)
AUTO
BTW nice forum!
FICM Main Power
FMP
PID: 2209D0
Unit: Volts
Max/Min: 50/0
Equation: ((A*256)+B)*(100/256)/100
FICM Logic Power
FLP
PID: 2209CF
Unit: Volts
Max/Min: 50/0
Equation: ((A*256)+B)*(100/256)/100
FICM Vehicle Power
FVP
PID: 2209CE
Unit: Volts
Max/Min: 50/0
Equation: ((A*256)+B)*(100/256)/100
Fan Speed Sensor
FAN
PID: 22099F
Unit: RPM
Max/Min: 1000/0
Equation: ((A*256)+B)*(1/4)
Injection Control Pressure
HPOP
PID: 221446
Unit: PSI
Max/Min: 5000/0
Equation: ((A*256)+B)*(57/100)
Fuel Pump Duty Cycle
FPDC
PID: 221672
Unit: %
Max/Min: 100/0
Equation: A*100/128
Torque into Torque Converter
TC TQ
PID: 2209CB
Unit: Lb-Ft
Max/Min: 1000/0
Equation: ((A*256)+B)*(1/1)
Engine Oil Temp
EOT
PID: 221310
Unit: Deg. F
Max/Min: 300/0
Equation: ((((A*256)+B)/100)+40)*(9/5)+32
VGT Duty Cycle
VGT
PID: 22096D
%
Max/Min: 100/0
((A*256)+B)*(100/32767)
FUEL LEVEL
FUEL
PID: 2216C1
%
Max/Min: 100/0
((A*256)+B)*(100/328)
This one was fun!!!!!! Its converted into GPH instead of mm^3 per sec.
Volume Fuel Desired
221411
VFD
0.0
50.0
x.1
GPH (gallons per hour)
((((((A*256)+B)*(100/16)/10)*8)*3600)*3785411.78)
AUTO
CYL #1 Cumulative Misfires
22160E
1CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #2 Cumulative Misfires
22160F
2CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #3 Cumulative Misfires
221610
3CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #4 Cumulative Misfires
221611
4CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #5 Cumulative Misfires
221612
5CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #6 Cumulative Misfires
221613
6CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #7 Cumulative Misfires
221614
7CM
0.0
100.
X1
MISFIRES
((A*256)+B)
CYL #8 Cumulative Misfires
221615
8CM
0.0
100.
X1
MISFIRES
((A*256)+B)
Injection Pressure Regulator Duty Cycle
221434
IPR
0.0
100.0
x1
%
(A*13.53)/35
AUTO
Injection Timing BTDC
2209CC
INJ
-50.0
50.0
X1
DEG.
((A*256)+B)*(10/64))/10
AUTO
Battery Voltage
VBatt
221172
0.
16.0
(A/16)
AUTO
#4
#5
#7
I wasn't using the latest version of Torque when I started the thread the first time around but have since upgraded. It doesn't look like I gained much with the predefined PID set for my truck. I need to keep messing around with it though. Thanks for posting these.
No prob. any question lemme know. also if you get a reading that is "wrong" I can look into fixing it....
Soon they will be predefined pids for the ford. I have given them to the developer. But I dont know when they will be released.
Trending Topics
#8
#11
if there is something special that you want to be able to read let me know and I can figure something out for ya....
#12
Hey Jester - I changed the math on the EOT from the A-40 that was downloaded to the math you post here, but my temps are impossibly high, about 2x (see below) what it should be.
I tried simply adding )/2 (with a leading parenthesis) to correct it, but that just tweaked it lower than it should be, was less than half.
Should I change it to be (A*128) instead of (A*256) ? Sorry if this is a stupid question, I am not yet wholly familiar with OBDII
I tried simply adding )/2 (with a leading parenthesis) to correct it, but that just tweaked it lower than it should be, was less than half.
Should I change it to be (A*128) instead of (A*256) ? Sorry if this is a stupid question, I am not yet wholly familiar with OBDII
#13
I see what happened....
torque is trying to scale that value into converting a *c reading into *F which is on your gauge.
Do this:
for the units of the gauge type in Deg *F or just Deg. dont let torque scale the equation.
Also put the equation right back where it is....its a bummer but it works.
lemme know what you get.
also....
The reasoning for the equations is that the ford's PCM reads and runs everything in hexadecimal. so we are taking a hex value and converting it into something that we can read. when you change A*128 from A*256 has really nothing to do with the final value. that just converts a 2 bit response into decimal. (notice most have that (a*256)+B) that just sets up the equation on pids that spit out 2 bits of info. some are simple like trans gear.... like a*.5....but its a 07E1 header in the PID line and it wiggs out sometimes....grrrrrr....
it sure is fun....to try to figure this out....a sense of achievement.
torque is trying to scale that value into converting a *c reading into *F which is on your gauge.
Do this:
for the units of the gauge type in Deg *F or just Deg. dont let torque scale the equation.
Also put the equation right back where it is....its a bummer but it works.
lemme know what you get.
also....
The reasoning for the equations is that the ford's PCM reads and runs everything in hexadecimal. so we are taking a hex value and converting it into something that we can read. when you change A*128 from A*256 has really nothing to do with the final value. that just converts a 2 bit response into decimal. (notice most have that (a*256)+B) that just sets up the equation on pids that spit out 2 bits of info. some are simple like trans gear.... like a*.5....but its a 07E1 header in the PID line and it wiggs out sometimes....grrrrrr....
it sure is fun....to try to figure this out....a sense of achievement.
#14
I see what happened....
torque is trying to scale that value into converting a *c reading into *F which is on your gauge.
Do this:
for the units of the gauge type in Deg *F or just Deg. dont let torque scale the equation.
Also put the equation right back where it is....its a bummer but it works.
lemme know what you get.
also....
The reasoning for the equations is that the ford's PCM reads and runs everything in hexadecimal. so we are taking a hex value and converting it into something that we can read. when you change A*128 from A*256 has really nothing to do with the final value. that just converts a 2 bit response into decimal. (notice most have that (a*256)+B) that just sets up the equation on pids that spit out 2 bits of info. some are simple like trans gear.... like a*.5....but its a 07E1 header in the PID line and it wiggs out sometimes....grrrrrr....
it sure is fun....to try to figure this out....a sense of achievement.
torque is trying to scale that value into converting a *c reading into *F which is on your gauge.
Do this:
for the units of the gauge type in Deg *F or just Deg. dont let torque scale the equation.
Also put the equation right back where it is....its a bummer but it works.
lemme know what you get.
also....
The reasoning for the equations is that the ford's PCM reads and runs everything in hexadecimal. so we are taking a hex value and converting it into something that we can read. when you change A*128 from A*256 has really nothing to do with the final value. that just converts a 2 bit response into decimal. (notice most have that (a*256)+B) that just sets up the equation on pids that spit out 2 bits of info. some are simple like trans gear.... like a*.5....but its a 07E1 header in the PID line and it wiggs out sometimes....grrrrrr....
it sure is fun....to try to figure this out....a sense of achievement.
When I remove the math for the C to F conversion, it was reading about 175-180 constantly on the way up, about 180 When ECT was up to 195ish. That doesn't sound right, eh?
I know something in the math, whether conversion or bitcount is wrong, because it was reading 260 just a min after starting it this morning.
#15
It has °F should it change it to be deg *F instead?
When I remove the math for the C to F conversion, it was reading about 175-180 constantly on the way up, about 180 When ECT was up to 195ish. That doesn't sound right, eh?
I know something in the math, whether conversion or bitcount is wrong, because it was reading 260 just a min after starting it this morning.
When I remove the math for the C to F conversion, it was reading about 175-180 constantly on the way up, about 180 When ECT was up to 195ish. That doesn't sound right, eh?
I know something in the math, whether conversion or bitcount is wrong, because it was reading 260 just a min after starting it this morning.
Yea that should work if you remove the math for the conversion. (the equation is like it is because it was created before torque automatically converted temp in the settings)
Your oil temp will be lower than the coolant until they get up to temp.
when you first start the truck is the oil and coolant temp within 2 degrees?
for sake of testing dont put anything in the units and put the formula in exactly as shown. see what you get on start up and after being on the highway.