I must be blind, but which gauge is the HPOP one? I have the CSV loaded and the Ford list added in Torque but do not see HPOP????

Maybe not enough coffee yet this AM

 

Yup, to early in the AM. ICP is it. Just a different name.

 

For a long time I would get some goofy readings for boost/egp. I always assumed it was some error related to the fact that I'm using some PLX adapters and Torque needs to switch between PLX mode and OBD mode.


I never understood why it was just these two pids that caused a problem....


Today, Boost and egp were off all the time - by a LOT. Baro, MAP and EBP were all fine.


I think I found my issue. At least it seems to have revived a good reading for Boost and EGP for the time being. I had these configured:


#FTE_Barometer,"BARO","221442","((A*256)+B)*0.0362 5",10,15,"PSI","C410F1"
#FTE_Manifold Gauge Pressure,"Boost","221440","(((A*256)+B)*0.03625)-[221442]",0.0,30.0,PSI,"Auto"
#FTE_Exhaust Gauge Pressure,"EGP","221445","(((A*256)+B)*0.03625)-[221442]",0.0,30.0,"PSI","Auto"
#FTE_Altitude,"Alt","221442","(14.7-(((A*256)+B)*0.03625))*2143",0,10000,"ft.",C410F1

Note that BARO and Alt both have PID 221442.

Boost and EGP both reference that PID.

I **think** that torque got confused and didn't know if it should be reading BARO or Alt for the Boost and EGP formulas. I guessing that for some reason it would mostly using BARO but then switched to mostly use Alt - making the readings be a huge negative number.

So, just a heads up, if your using formulas and referencing PIDs multiple PIDS with different formulas might mess things up.


[edit]
And a question. Has the difference between using [pid] and val{Long Name} been discussed/tested.

Found this reference when poking around:

[pid]: Refers to the pid number of a sensor.
val{Long Name}: Refers to another equation using its long name.

[/edit]

[edit2]
This seems to work:

Name,"ShortName","ModeAndPID","Equation","Min Value","Max Value","Units","Header"
#FTE_Manifold Absolute Pressure,"MAP","221440","((A*256)+B)*0.03625",0,45 ,"PSI","Auto"
#FTE_Exhaust Back Pressure (Absolute),"EBP","221445","((A*256)+B)*0.03625",0. 0,55.0,PSI,"Auto"
#FTE_Turbo PressureB,"TPD",,"val{#FTE_Exhaust Back Pressure (Absolute)}-val{#FTE_Manifold Absolute Pressure}",0,30,"PSI","Auto"

[/edit2]

 

If you have more than one PID of the same long name and number active at the same time, things do get weird - particularly if you reference that PID in another gauge.

The number goes with the long name. Think if it as an address, because that's precisely what it is. It's akin to everybody in a neighborhood speaking a different dialect of one language. You are telling Torque "Go to 123 Main street and ask Mr. Carl Jones how old he is." If you go to 124 Main street... or if you go to 123 Main street and talk to Cal Jones, you may not get an answer - or it may be confusing gibberish. In a computer... the result can be as benign as a gauge with erroneous or no data, or as severe as a lock-up and an engine stall.

 

Yes, but I would take that one step further. Since the PID number can be used in multiple places (for example #FTE_Barometer,"BARO","221442" and #FTE_Altitude,"Alt","221442") that it's always better to use the long name, where you can vs the PID.

If I use [221442] in a formula Torque Pro must guess as to what to use. Should it use BARO or Alt? The PID doesn't give enough info.

If I use val{#FTE_Barometer} my intention is crystal clear. I want BARO.


Make sense?

 

But wouldn't one of the above definitions be wrong? Two definitions for the same PID number? I think that's what Rich is saying. No matter what you call it, there's only one address and only one variable.

 

Thanks this makes a ton of sense and may have been part of my problems I was having when I first started to figure this out.

 

Maybe, I don't think so.


These both use PID 221442 but apply different formulas to get different results:

#FTE_Barometer,"BARO","221442","((A*256)+B)*0.0362 5",10,15,"PSI","C410F1"
#FTE_Altitude,"Alt","221442","(14.7-(((A*256)+B)*0.03625))*2143",0,10000,"ft.",C410F1


I think that we (FTE) also have our own version of formulas that may overlap with the set provided by torque pro. We use a different long name to set them apart.

Here's an example (0x2211b8):

"#FTE_Torque Converter Slip","Slip","0x2211b8","((A*256)+B)/4",0,1000,"RPM","Auto","","",1
"Torque converter slip","TCSlip","0x2211b8","((A*256)+B)*0.6103",0,5 00,"rpm","Auto","","",1


Torque also does it with its provided formulas(0x223987):

"ABS Wheel Speed 1","ABS W1","0x223987","A",0,100,"km/h","ABS","","",1
"ABS Wheel Speed 2","ABS W2","0x223987","B",0,100,"km/h","ABS","","",1
"ABS Wheel Speed 3","ABS W3","0x223987","C",0,100,"km/h","ABS","","",1
"ABS Wheel Speed 4","ABS W4","0x223987","D",0,100,"km/h","ABS","","",1

 

I have never been able to change the long name with the PID number on my 2000 without a malfunction. I see a lot of PIDs for what looks like something other than my era of truck in those examples, so I can't speak to those. The malfunction wouldn't be a Torque Pro problem, it's a PCM problem.

Torque does not create the environment for the data we want, we have to know what is available in the PCM or ECU - and call on that. The example of the ABS is akin to "Once you are at 123 Main street, tell me the square footage in the kitchen, the den, the living room, and the bedroom." The A, B, C, D are like sub-addresses.

 

All the PIDS with #FTE should be familiar. They are from this web site. the #FTE at the front just makes them go to the top of the list and keeps them group together - easier to find and select.

The others are what you would get from Torque if you were to export the entire existing PID set. I believe the only ones that are not for our truck are the ABS ones. That was just to show that torque does in fact utilize the same PID for different.

I don't try to monitor the PIDS that are not associated with out truck.

Just to be clear, do you overwrite the torque pro PIDS when they diverge from what you believe to be correct?

For example:

FTE has this:
"#FTE_Torque Converter Slip","Slip","0x2211b8","((A*256)+B)/4",0,1000,"RPM","Auto","","",1

While torque has this:
"Torque converter slip","TCSlip","0x2211b8","((A*256)+B)*0.6103",0,5 00,"rpm","Auto","","",1


When you import your value do you give a long name of Torque converter slip so that you overwrite the one supplied by torque, or do you use a slightly different long name?

 

My reference to "my era of truck"... I have not used the 0x prefix in my Superduty 7.3L, so I suspected it was from an OBS 7.3L or a 6.0. Both of which would have a different PCM and different behavior.

 

The 0x prefix is just what you get when you export the pid set from torque.

 

Ah... I never tried that. Maybe the 0x prefix helps with overriding the long name duplication glitch I experience... or maybe it's just my version of PCM.

 

I solved my challenge i believe with the custom PIDS. I wasn't able to leave the header blank, I had to insert the CF40F1 in order to make it work. I don't know if I didn't read correctly that this had to be done or had just missed it, but now they seem to be working!

 

Having said all that I now can't enter EOT PID as it say's there is already a PID with that name, however, there isn't.