More PIDs for Torque App

[AmpOverload]

I might not have the answer today, but I will figure things out soon. Give me a day or two because things are a bit hectic here at the moment.

OK, I've run some tests with GDS2, now using your anonymized (2013) VIN instead of specifying a 2012 vehicle, but still specifying the 'LUJ' engine. The change in model year caused the list of Mode $22 PIDs being queried for the "Engine Data" page to change. It's now this list of 54 PIDs:

$0004, $0005, $0006, $0007, $000B, $000C, $000D, $000E, $000F, $0010,
$001F, $002E, $002F, $0030, $0031, $0033, $0042, $0044, $0046, $1123,
$1124, $1127, $1128, $1130, $1131, $1190, $11C9, $1232, $1233, $12B1,
$12C3, $131F, $136C, $148D, $1523, $2006, $2020, $203F, $205A, $2067,
$2070, $2072, $207E, $20D0, $20D4, $20EE, $2301, $2320, $2321, $247D,
$3201, $328B, $328D, $3298

Here is the information I decoded for each of the 6 PIDs you were interested in:

1. 'Boost Pressure Sensor', Mode $22, PID $3298, formula "(A * 256 + B) / 100" in kPa
2. 'Turbocharger Bypass Solenoid Valve Command', Mode $22, PID $328D, formula "A / 255 * 100" in percent
3. 'Turbocharger Wastegate Solenoid Valve Command', Mode $22, PID $328B, formula "A / 255 * 100" in percent
4. 'Fuel Economy', Mode $22, PID $203F, formula "A / 2" in liters per hour
5. 'BARO' is just the standard Mode $01 PID $33 (defined by SAE J1979). The formula is "A" in kPa.
6. 'EVAP Purge Solenoid Valve Command' is just the standard Mode $01 PID $2E (defined by SAE J1979). The formula is "A / 255 * 100" in percent.

The only thing I ask is that you let us know how well (or poorly) those PIDs work.

Good luck!

 

[buraan]

Here is the information I decoded for each of the 6 PIDs you were interested in:

1. 'Boost Pressure Sensor', Mode $22, PID $3298, formula "(A * 256 + B) / 100" in kPa
2. 'Turbocharger Bypass Solenoid Valve Command', Mode $22, PID $328D, formula "A / 255 * 100" in percent
3. 'Turbocharger Wastegate Solenoid Valve Command', Mode $22, PID $328B, formula "A / 255 * 100" in percent
4. 'Fuel Economy', Mode $22, PID $203F, formula "A / 2" in liters per hour
5. 'BARO' is just the standard Mode $01 PID $33 (defined by SAE J1979). The formula is "A" in kPa.
6. 'EVAP Purge Solenoid Valve Command' is just the standard Mode $01 PID $2E (defined by SAE J1979). The formula is "A / 255 * 100" in percent.

The only thing I ask is that you let us know how well (or poorly) those PIDs work.

Good luck!

Hello,
I had to take a ride anyway so I plugged in my favourite ELM327 tool. The results:

• Boost Pressure Sensor - works, values seems to be ok
• Turbocharger Bypass Solenoid Valve Command: works
• Turbocharger Wastegate Solenoid Valve Command: works, it's either 0% or 100% (makes sense)
• Fuel Economy: works, the problem is the resolution; obviously it's 0.5 liters per hour. E.g. if the dash shows 0.7 liters, Torque still shows 0.5. But it works.
• BARO: Nope. It constantly shows 190kPa, should be ~100 kPa. Maybe I added it wrongly? I added custom pid '010033'
• EVAP Purge Solenoid Valve Command: I'm not sure. I also added '01002e', it shows always 74.5% but when I stop the engine I know from experience that the Evap valve is closed, so it should be 0% or 100%, it depends.

Here is the csv list so far:

"Name", "ShortName", "ModeAndPID", "Equation", "Min Value", "Max Value", "Units", "Header", "startDiagnostic", "stopDiagnostic", "scale","minimumRefreshDelayMillis"
"[A14NET] Barometric pressure","BARO","0x010033","A",0,100,"kPa","","","",1,0
"[A14NET] Boost Pressure Sensor","Boost","0x223298","((A*256)+B)/100",0,656,"kPa","","","",1,0
"[A14NET] EVAP Purge Solenoid Valve Command","EVAP","0x01002e","(A/255)*100",0,100,"%","","","",1,0
"[A14NET] Fuel Economy","Fuel","0x22203f","A/2",0,100,"L/h","","","",1,0
"[A14NET] Turbo Wastegate Solenoid Valve Command","Wastegate","0x22328b","(A/255)*100",0,100,"","","","",1,0
"[A14NET] Turbocharger Bypass Solenoid Valve Command","Bypass","0x22328d","(A/255)*100",0,100,"%","","","",1,0

 

[AmpOverload]

Hello,
I had to take a ride anyway so I plugged in my favourite ELM327 tool. The results:

• Boost Pressure Sensor - works, values seems to be ok
• Turbocharger Bypass Solenoid Valve Command: works
• Turbocharger Wastegate Solenoid Valve Command: works, it's either 0% or 100% (makes sense)
• Fuel Economy: works, the problem is the resolution; obviously it's 0.5 liters per hour. E.g. if the dash shows 0.7 liters, Torque still shows 0.5. But it works.
• BARO: Nope. It constantly shows 190kPa, should be ~100 kPa. Maybe I added it wrongly? I added custom pid '010033'
• EVAP Purge Solenoid Valve Command: I'm not sure. I also added '01002e', it shows always 74.5% but when I stop the engine I know from experience that the Evap valve is closed, so it should be 0% or 100%, it depends.

Sorry, I neglected to mention something about Mode $01 versus Mode $22...

Mode $01 PIDs are only 2 (hex) digits. So, for a Mode $01 PID like 'BARO', use a command of "0133" or use the Mode $22 (4-hex-digit) equivalent command of "220033" (and maybe with a trailing "01" since GM sometimes requires that on Mode $22 queries, assuming Torque Pro doesn't add it automatically for you). Same thing for the EVAP Purge PID.

Let us know it if that helps. Good luck!

P.S. I'll take another look at the "Fuel Economy" PID, in case I missed something, like maybe a 2nd byte, to provide higher resolution.

 

[AmpOverload]

P.S. I'll take another look at the "Fuel Economy" PID, in case I missed something, like maybe a 2nd byte, to provide higher resolution.

OK, I just double-checked the "Fuel Economy" PID. Unfortunately, I see no evidence that there is any higher resolution available there (i.e. a 2-byte PID instead of a 1-byte PID). I cannot explain why your dash shows greater resolution.

 

[buraan]

OK, I just double-checked the "Fuel Economy" PID. Unfortunately, I see no evidence that there is any higher resolution available there (i.e. a 2-byte PID instead of a 1-byte PID). I cannot explain why your dash shows greater resolution.

Hello,
never mind, I'll keep it anyway for fun. In the meantime I tested the two standard pids (baro & evap) by correctly enter the pid number - both works! When the Evap valve is closed, the value is 0% (it shows how open the valve).
Thank you very much, these are really useful! Also your method to find the correct pids and calculations works perfectly!

 

[pnwsr6]

Has anyone ever found the PID for the coolant tank level?

 

[TJBaker57]

Has anyone ever found the PID for the coolant tank level?

I would imagine that data will be in a bit-mapped PID. A bit-mapped PID is one where one or more of the individual bits of the response byte (or bytes) represents the status of a given switch or condition.


My 2005 Yukon 5.3 has a coolant tank level switch so I should be able to track that one down.

 

[pnwsr6]

That would be perfect. My I've found when you put a p59 in place of a 411 PCM, for some reason the coolant level sensor is not reported to the cluster of an 01 or 02 truck. I like having that early warning sign even if I have to use torque to get it.

 

[pnwsr6]

I would imagine that data will be in a bit-mapped PID. A bit-mapped PID is one where one or more of the individual bits of the response byte (or bytes) represents the status of a given switch or condition.


My 2005 Yukon 5.3 has a coolant tank level switch so I should be able to track that one down.

That would be perfect. My I've found when you put a p59 in place of a 411 PCM, for some reason the coolant level sensor is not reported to the cluster of an 01 or 02 truck. I like having that early warning sign even if I have to use torque to get it.

 

[TJBaker57]

That would be perfect. My I've found when you put a p59 in place of a 411 PCM, for some reason the coolant level sensor is not reported to the cluster of an 01 or 02 truck. I like having that early warning sign even if I have to use torque to get it.

I looked into this a bit yesterday and discovered that my Yukon does not have that optional sensor. I thought it did.

This means I cannot easily determine what PID holds that data.

 

[pnwsr6]

I looked into this a bit yesterday and discovered that my Yukon does not have that optional sensor. I thought it did.

This means I cannot easily determine what PID holds that data.

That's interesting, I thought that all the truck platforms had the coolant level sensor. That gives me an idea to look at the DTC's a little closer. If it's optional, there might be a way to turn it on. I know as far as wiring,the p59 and 411 are the same for that sensor. It could be as simple as turning on the DTC for that sensor to make it work. I'm going to do a little digging on what I can find.

 

[TJBaker57]

That's interesting, I thought that all the truck platforms had the coolant level sensor. That gives me an idea to look at the DTC's a little closer. If it's optional, there might be a way to turn it on. I know as far as wiring,the p59 and 411 are the same for that sensor. It could be as simple as turning on the DTC for that sensor to make it work. I'm going to do a little digging on what I can find.

OK, I pulled up the "Engine Data 2" menu selection on my Autel AP200 and that is where I see the field for coolant level sensor. But in quotes is a notation that states (if equipped). (The Autel uses precisely the same data as a Tech 2, seen at the actual serial data stream level.) When displaying data from my 05 5.3L the value returns "low" when the reservoir is not low. This is why I believe it is/was an option.

Looking at the reservoir in my Yukon I can find no sensor.

Further, I find conflicting wiring diagrams. One shows a coolant level sensor wired to the PCM but another diagram shows the specific PCM terminal as "not used".

If I decide to do further research on my 5.3 the next step would be to access the pertinent PCM harness connector and see if there is any wiring to said terminal. (from memory I think it was connector 1, pin 30?)

 

[azswiss]

On my 2003 Suburban 5.3L with the P59 the coolant level switch is two-wire, same as the low oil pressure switch. I know it is connected on my truck as the switch is currently faulty and I get the "LOW COOLANT LEVEL" warning at startup. A quick check on charm.li confirms the C1 Pin 30 location for my vehicle.

 

[pnwsr6]

On my 2003 Suburban 5.3L with the P59 the coolant level switch is two-wire, same as the low oil pressure switch. I know it is connected on my truck as the switch is currently faulty and I get the "LOW COOLANT LEVEL" warning at startup. A quick check on charm.li confirms the C1 Pin 30 location for my vehicle.

Do you happen to know what OS your Suburban is running?

 

[azswiss]

OS is 12579405. Screenshot of Cal ID info below.

 

[pnwsr6]

OS is 12579405. Screenshot of Cal ID info below.

View attachment 117223

Excellent, I might be able to turn it on in 7603 now. I have some testing to do when I get home in a few days. Someone on FB gave me some info and if my hunch is right, I'll be able to confirm it on 9405 and then test it on 7603. To me it's a no brainer to have that sensor installed and working if it's available. I'll report back what I find out in a few days and see if it helps @TJBaker57 find the PID.

 

[orz]

Hey all, new here. I have a 2016 Express 3500 with L96 6.0L V8 + 6L90E. The instrument cluster is sparse on this thing so I've gotten an OBDLink MX+ and have been experimenting with various ways to get more gauges on my phone, especially for towing. I've been experimenting with OBDLink's software, Torque Pro, and Car Scanner. Right now I'm leaning toward Car Scanner but I'm still not sure.

I have many of the usual gauges (RPM, ATF Temp, Oil Temp... etc).

However there are two transmission parameters I'd like to get that I don't have.

FWIW, It seems for my van the header must be set to 7E2 to talk to the TCM.

1. Selected gear (range?) when in manual mode.
I have a PID (221951) that can read the gear selector position (P/N/R/D/M/1). 22194C also seems to give similar info (but with different values. There is also the usual PID (22199A) that tells the transmission's current actual gear. I have also figured out another PID (22197E) where bits 2 and 3 are bit the bit mapped state of the shift up/down buttons (1=pressed, 0=not pressed) but as of yet I haven't figured out anything that shows the user selected range. Would like to be able to have a clear indicator/warning when I have chosen a gear that van doesn't want to use, which usually means I have selected the wrong gear, which can sometimes have undesirable results (eg if I've left it in too low of a gear, there can be an abrupt, high RPM downshift when I reach an RPM that the TCU *does* accept for the chosen gear.).

This is information available in the DIC (it says M1, M2, etc) so it must be in there somewhere- but I can't find it. Besides, the current gear (M1, M2 etc) can be hidden by persistent nuisance warnings (My van currently has "Park Assist Off" because the previous owner put in an aftermarket radio without a chime retention harness).

2. A clear measure of the TCC lockup state. My other vehicle is a Toyota, and there is a very simple PID for Torque Converter Lock that reads 1 when it's locked and 0 when it isn't. I do understand there is a PID for TCC slip speed, but just because slip is low doesn't mean it's truly locked. Further up this thread somebody mentioned PID 221970 for the lockup apply solenoid, which sounds promising, but it does not work on my van. In fact when I tried the header of 6C10F1 suggested in the thread, my engine immediately turned off and it wouldn't turn back on until I removed the key. I also tried it with Auto headers as well as the standard 7E2, neither of which works. Wonder if there's anything else I'm missing.

I've scanned the entire 2219xx range and where most transmission-related values seem to live and I can't seem to figure anything particularly helpful.