Thanks for the update GW1.

Looks good so far now lets hope
your hot readings are reasonable.

I too cannot post images since I
dont subscribe to those services.

Thats awesome! You, MJ and Maf have
led the way for your 7.3L buddies. I
appreciate your help and hope they do
too.

Thanks again.

Edit:

MJ:

Check your psn posting of pids…

IATf is showing incorrect span. Should be -0.00314.
Boost is missing ) after B.

Edit2:

TFTf is showing incorrect span. Should be -0.00360.

Ian, if you are reading this thread, can you look
at the polynomial equations. The parser is throwing
paren errors even though the various bits are wrapped
in parens as you suggested in other threads.

The equations work in Excel so I believe this maybe a
parser issue and was hoping you would spot it in the
equation.

Quote from Capp777 on January 20, 2014
Thats awesome! You, MJ and Maf have
led the way for your 7.3L buddies. I
appreciate your help and hope they do
too.

Thanks again.

Edit:

MJ:

Check your psn posting of pids…

IATf is showing incorrect span. Should be -0.00314.
Boost is missing ) after B.

Edit2:

TFTf is showing incorrect span. Should be -0.00360.

End Quote.

Added TFTf correction for psn.

Maf:

For your boost problem try…

Boost
((((A*256)+B)*0.00109)-15.73)-([221127]*0.1) or
((((A*256)+B)*0.00109)-15.73)-[221127]

Not sure if the *0.1 is needed. If your boost reading
is near ~13.2 then use second equation. If your boost
reading is near ~0.0 continue using the first equation.

This boost equation uses your trucks extended pid for
baro.

Quote from Capp777 on January 13, 2014
MJ:

TP V
Header: C410F1
Mode/Pid: 221154

EGR TP
Header: C410F1
Mode/Pid: 22096C

More pids that might
be tp related.

Edit:

TP V
Header: C410F1
Mode/Pid: 220917

TP V
Header: C410F1
Mode/Pid: 220918

End Quote.

Two more to try for TP.

You can just enter A or (A*256)+B.

Test response will display the raw hex data
returned by the ecu if it is successful. The
challenge is getting the correct equation for
the raw hex data returned… if it works.

Again, since the 7.3’s are prone to shutting
down with some diagnostic commands test
with KOEO for safety.

Edit:

Will you also post the test response for
221154? MJ’s gauge read zero but he did
get a response. The raw hex data may
still hold an answer.

Capp I test TP V
221154
C410F1
(A*256)+B

Response was
Equation 0.0
6211540000

I have no idea what that means.

220917 and 220918 neither had no response.

If you are using the equations for
EBP psia, MAP psia and Baro psia
they should agree +/- 0.5 with KOEO.

If you subtract the baro value from
the psia reading it will give you psi.
This is what MJ is doing to get near
zero readings on his EBP.

Thanks for testing the other TP sensors.
I will keep looking…

If you get another chance, will you try
the second attempt at the TFT F
polynomial pid to see if parser will
accept this version. (I removed sets of
parens that wrapped the ^ bits.

Thanks again for your help.

Edit:

Am I confusing accelerator pedal pid
with throttle position pid?

Edit2:

It appears that Torque cannot handle exponents
as written in the polynomial equations.

TFT F
-0.00000000000194*(((A*256)+B)*((A*256)+B)*((A*256)+B))
+(0.0000002*(((A*256)+B)*((A*256)+B)))+(-0.0096*((A*256)+B))+258

IAT C
-0.00000000000196*(((A*256)+B)*((A*256)+B)*((A*256)+B))
+(0.000000196*(((A*256)+B)*((A*256)+B)))+(-0.00774*((A*256)+B))+144

IAT C
-0.00000000000196*(((A*256)+B)*((A*256)+B)*((A*256)+B))
+(0.000000196*(((A*256)+B)*((A*256)+B)))+(-0.00774*((A*256)+B))+144

that is a lot of typing
it seemed to eat that. I will test that and Acel POS in AM.

thank you

Can you post the raw hex values with the
associated IAT C reading from test response
in pid editor? I would like to verify this equation
is giving the expected results by hand.

Torque would not let me wrap the first line of
the equation in parens without error.

Edit:

Pid removed because I couldn’t verify the
source.