Torque PIDs...Take 2

[millinnium]

Those that are interested in the Learned Octane Adjust,

the readings in HEX and the result converted to % are:

DCEC = 54.81%

D145 = 73.01%

but i can't figure out the maths behind it. HEX converted to Decimal will make DCEC > D145 but the % result intepreted is the opposite...

 

[ecoboostsho]

Those that are interested in the Learned Octane Adjust,

the readings in HEX and the result converted to % are:

DCEC = 54.81%

D145 = 73.01%

but i can't figure out the maths behind it. HEX converted to Decimal will make DCEC > D145 but the % result intepreted is the opposite...

If you look up a few threads we've got it figure out I believe on Page 8.  On my car if I flash a new tune in it the LROA starts at 0 and after a long pull in 3rd and 4th at WOT jumps to 100% and then on my car it has slowly backed down to 75% over time.  I'm guessing I could use a little more octane but it is still on the positive side...

 

[SHOnUup]

Makes my brain hurt a little though...

Sent from my SM-G900V using Tapatalk

 

[ecoboostsho]

New PID Found:

Need equation figured out though.

1FA4 = -5.75A

Battery Current BATT CUR 224090 ((signed(A)*256)+b)/4 -600 600 Amp 726

I will have to see if I can get that PID on my car.  We can get 100's more of these pretty easily (I am just using a serial sniffer and watching the CAN bus using a Scan tool) the tricky part is always the equation.  If you can get me two points and two hex values we can calculate a potential formula assuming it is a linear response. 

i.e. if you know 1FA4 is -5.75 then just get me another value pair and we can plug it in to a basic line/slope equation and try it out.

 

[ecoboostsho]

Figured out something kind of cool today with Torque.  I was watching the Fuel pump Desired gauge and trying to compare it to the "Actual" to see how close they were.  It then occurred to me that it would be ideal to have this calculated and displayed as a gauge.  The idea being if you are at the track and/or running E85 you could start to see if your pump was getting behind and fuel pressure was dropping - which would be bad.  I then stumbled across an interesting way to subtract two PIDs in Torque (on a Prius site of all places!). 

You just create a new custom PID but you leave the "PID" field blank and then enter the PIDs in the formula section.  The trick is you have to reference each PID EXACTLY by name...no typos allowed.  We had figured out "Desired" earlier and while the "Actual" is already available in Torque I found out the PID ID the usual way figuring sometimes the Ford PID is actually better than the standard one due to more frequent updates.

So first make sure the following two custom PIDs are already defined in Torque.

Fuel Pump pressure "desired"
Name:  Fuel Pump Desired Pressure
PID:  2203dc
torque Equation: ((256*A)+b)*10*.145  readout in PSI.
Unit: PSI

Fuel Pump Rail Pressure2  (Already in Torque but I am calling it out specifically)
Name: Fuel Pump Rail Pressure2
PID: 22F423
Equation:  ((256*A)+b)*10*.145  readout in PSI.
Unit: PSI

Then add another custom PID in torque but as stated leave the actual PID field blank.  The PID name you are referencing is what is in between the {}  and as stated above the long names need to match exactly.

Differential Fuel Pump Pressure (Uses two previous PIDs to calculate a Torque "Virtual PID" and display the results!)
PID:
Name: Fuel Pressure Differential
Equation:  (VAL{Fuel Pump Desired Pressure}) - (VAL{Fuel Pump Rail Pressure2})
Unit: PSI

I did this and it works great!  the only thing I'm not sure of is the order the PIDs are all being scanned...If one PID was at the beginning of a scan and the other was at the end of scan this could create a larger "discrepancy" than is really there.  Still fun to watch though!

You could do the same thing with requested Air/Fuel vs Commanded Air/Fuel to see how far off the car is...kind of cool!

As always I updated the first post so you don't have to search through all this.

 

[Larrylu]

This new functionality reminds me of the process one had to go through to get a boost gauge with the MyCal Touch. Makes Torque a pretty powerful and flexible tool.

 

[millinnium]

Those that are interested in the Learned Octane Adjust,

the readings in HEX and the result converted to % are:

DCEC = 54.81%

D145 = 73.01%

but i can't figure out the maths behind it. HEX converted to Decimal will make DCEC > D145 but the % result intepreted is the opposite...

If you look up a few threads we've got it figure out I believe on Page 8.  On my car if I flash a new tune in it the LROA starts at 0 and after a long pull in 3rd and 4th at WOT jumps to 100% and then on my car it has slowly backed down to 75% over time.  I'm guessing I could use a little more octane but it is still on the positive side...

Hi Ecoboost, i have tried your formula  ((256*A)+B)/49152*100) but not getting the same result as what FORScan is showing.

For example:

Hex DCEC which FORScan calculated to 54.81% if plugged to your formula = 56556/49152*100 = 115.06%

Hex D145 which FORScan calculated to 73.01% if plugged to your formula = 53573/49152*100 = 108.99%

This is why i say the formula is not correct since Hex DCEC is mathematically smaller than Hex D145, yet the calculated percent value from FORScan shows it as a larger percentage.

 

[ecoboostsho]

I think it is calculated differently between our two ecu's. I will try and post some raw values. The formula seems to work for the Taurus.

Sent from my XT1060 using Tapatalk

 

[ecoboostsho]

Has anyone else tried the octane adjust? Can you post your results?

Sent from my XT1060 using Tapatalk

 

[ecoboostsho]

Those that are interested in the Learned Octane Adjust,

the readings in HEX and the result converted to % are:

DCEC = 54.81%

D145 = 73.01%

but i can't figure out the maths behind it. HEX converted to Decimal will make DCEC > D145 but the % result intepreted is the opposite...

If you look up a few threads we've got it figure out I believe on Page 8.  On my car if I flash a new tune in it the LROA starts at 0 and after a long pull in 3rd and 4th at WOT jumps to 100% and then on my car it has slowly backed down to 75% over time.  I'm guessing I could use a little more octane but it is still on the positive side...

Hi Ecoboost, i have tried your formula  ((256*A)+B)/49152*100) but not getting the same result as what FORScan is showing.

For example:

Hex DCEC which FORScan calculated to 54.81% if plugged to your formula = 56556/49152*100 = 115.06%

Hex D145 which FORScan calculated to 73.01% if plugged to your formula = 53573/49152*100 = 108.99%

This is why i say the formula is not correct since Hex DCEC is mathematically smaller than Hex D145, yet the calculated percent value from FORScan shows it as a larger percentage.

Okay - given the two data points you've given I did a little math and the equation you should be using is (not 100% positive here but give it a shot).

((256*A)+B)*(-0.0000610124)+3.998717499

Yes I went crazy with the precision after the decimal points...and note that is multiplying a negative number NOT multiplying and then minus.  It's just Y=mX+B format based on the points provided assuming I calculated it correctly.

Weirdly enough this formula and the one I figured out for the Taurus are not as far off as they might appear.  If you calculate out 100% in this formula it equates to roughly 49152 but yours has a negative slope so smaller values mean larger numbers (which is what you noted).

Try this and see if it works.  It's getting late here and my math may be off...the only other option is that your car is using the -1 to +1 referenced elsewhere and those values provided are actually signed binary numbers...but my brain hurts thinking about it right now so try this first.

 

[ShoBoat]

Only two remain from my original wish list....namely EGT and transmission gear indicator. Looks like one of those might be on this list- transmission gear engaged. Quite a list indeed!  Thank you!

Ill See if I can pull the PID from Forscan.

Here are the PIDs for the TPMS

LF 228131
RF 228141
RR 228151
LR 228161

I get a response from the car but the equations are not working at all. Any help with this one would be great!

Sorry it doesn't seem like EGT is possible on the Taurus. Not found in FORScan.

But I found this one

Transfer Case Temperature

PID 22070D

I am using the formula from the transmission temp on page one and it's not quite right. It's really close but not quite there.


Sent from my iPhone using Tapatalk

 

[millinnium]

Those that are interested in the Learned Octane Adjust,

the readings in HEX and the result converted to % are:

DCEC = 54.81%

D145 = 73.01%

but i can't figure out the maths behind it. HEX converted to Decimal will make DCEC > D145 but the % result intepreted is the opposite...

If you look up a few threads we've got it figure out I believe on Page 8.  On my car if I flash a new tune in it the LROA starts at 0 and after a long pull in 3rd and 4th at WOT jumps to 100% and then on my car it has slowly backed down to 75% over time.  I'm guessing I could use a little more octane but it is still on the positive side...

Hi Ecoboost, i have tried your formula  ((256*A)+B)/49152*100) but not getting the same result as what FORScan is showing.

For example:

Hex DCEC which FORScan calculated to 54.81% if plugged to your formula = 56556/49152*100 = 115.06%

Hex D145 which FORScan calculated to 73.01% if plugged to your formula = 53573/49152*100 = 108.99%

This is why i say the formula is not correct since Hex DCEC is mathematically smaller than Hex D145, yet the calculated percent value from FORScan shows it as a larger percentage.

Okay - given the two data points you've given I did a little math and the equation you should be using is (not 100% positive here but give it a shot).

((256*A)+B)*(-0.0000610124)+3.998717499

Yes I went crazy with the precision after the decimal points...and note that is multiplying a negative number NOT multiplying and then minus.  It's just Y=mX+B format based on the points provided assuming I calculated it correctly.

Weirdly enough this formula and the one I figured out for the Taurus are not as far off as they might appear.  If you calculate out 100% in this formula it equates to roughly 49152 but yours has a negative slope so smaller values mean larger numbers (which is what you noted).

Try this and see if it works.  It's getting late here and my math may be off...the only other option is that your car is using the -1 to +1 referenced elsewhere and those values provided are actually signed binary numbers...but my brain hurts thinking about it right now so try this first.

((256*A)+B)*(-0.0000610124)+3.998717499 EQUATION IS ACCURATE. Thank you and superb work

 

[millinnium]

New PID Found:

Need equation figured out though.

1FA4 = -5.75A

Battery Current BATT CUR 224090 ((signed(A)*256)+b)/4 -600 600 Amp 726

I will have to see if I can get that PID on my car.  We can get 100's more of these pretty easily (I am just using a serial sniffer and watching the CAN bus using a Scan tool) the tricky part is always the equation.  If you can get me two points and two hex values we can calculate a potential formula assuming it is a linear response. 

i.e. if you know 1FA4 is -5.75 then just get me another value pair and we can plug it in to a basic line/slope equation and try it out.

1FA4 = -5.75A
1FA3 = -5.81A
1F5F = -10.06A

Equation is: (((A*256)+B)/16)-511.7

 

[ecoboostsho]

New PID Found:

Need equation figured out though.

1FA4 = -5.75A

Battery Current BATT CUR 224090 ((signed(A)*256)+b)/4 -600 600 Amp 726

I will have to see if I can get that PID on my car.  We can get 100's more of these pretty easily (I am just using a serial sniffer and watching the CAN bus using a Scan tool) the tricky part is always the equation.  If you can get me two points and two hex values we can calculate a potential formula assuming it is a linear response. 

i.e. if you know 1FA4 is -5.75 then just get me another value pair and we can plug it in to a basic line/slope equation and try it out.

1FA4 = -5.75A
1FA3 = -5.81A
1F5F = -10.06A

Equation is: (((A*256)+B)/16)-511.7

Cool...I still haven't tried this one out yet...although I should have.  Just replaced my battery yesterday!

 

[ecoboostsho]

Transfer Case Temperature

PID 22070D

I am using the formula from the transmission temp on page one and it's not quite right. It's really close but not quite there.


Sent from my iPhone using Tapatalk

I haven't seen this one yet!  If its really labeled "Transfer Case" I'm assuming that would be the PTU?  I would love to have this.  Then again I keep forgetting you've got a 2013...I wonder if they added that temp on those models with all the PTU failures in the previous years.  Do you know what "module" was responding to this?  PCM/BCM/AWD4x4? etc... You can try and dig up the other formula we "were" using for the transmission...Or if you give me two values from the serial sniffer (the corresponding HEX responses) and the value at the same time in Forscan or another scan tool I can possibly figure out a formula for you if its a linear response to temp.  Anyone with a 2010-2012 you can try to put 761 in the "header" field to get a response from the 4x4 module to see if the temp is in there...or leave it blank for the PCM.

 

[ShoBoat]

It's in the PCM, I'll see if I can get the values tonight. I would be also interested if the pre 2013 have this ability.


Sent from my iPhone using Tapatalk

 

[Larrylu]

I tried to make a gauge based on a formula between 2 PID's. I think my efforts are mostly right. I wanted to replace my 4 air temp readings with 1 that would give the difference between IAT 2 And Ambient. Sort of a 1 gauge Heat Soak reading.  My result is reading the same as my IAT 2 which leads me to believe the problem in the formula is in the Ambient PID. One difference is that the Ambient PID is not a custom PID like the IAT 2. I wonder if this nice function is limited to just custom PID's and might not work with the ones packaged with Torque.

 

[ecoboostsho]

That's possible. I made a custom PID for my previous example. That said I can easily get you the PID for IAT and you can create one with a different long name.

Also the transfer case PID didn't work on my 2011...

Sent from my XT1060 using Tapatalk

 

[Larrylu]

That would be a great test. Too bad about the transfer case....not surprised though. Would have been a great gauge!

 

[ecoboostsho]

Larry - IAT is as follows:

PID: 22F40F
Equation (for degrees F): (A-40)*1.8+32

Name it something like "Intake Air Temperature 1" and give your custom calc PID a shot.  I didn't have time to try it myself. Obviously make sure both your PIDs are in the same units - either degree C or degree F.