Alright so I figured out that my O2 bank 1 sensor 1 won’t read the generic way because it is a wideband, or at least that’s my figuring because I know for a fact that it is a wideband sensor on my 2009 cobalt ss turbo. So in looking for the information I need to write a custom PID for this particular sensor I ran across this data sheet http://service.gm.com/gmspo/mode6/pdf/Bmode6/17%20Bmode6%202008%202.0L_LNF%20Direct%20Injection.pdf which I believe the 1st listing, the one that says normalized, is the particular sensor I need to configure. I’m still a bit foggy on how exactly the information I see in that spreadsheet translates into what I’m putting into the fields in the app. Anybody help a newb out?

I also have a Cobalt SS (2008) and the KR doesn’t seem to read right. It stays constant at 14.6 which makes no sense to me. Have you been able to get an accurate reading? Are the PIDs created in a similar fashion to say, HPTuners? If so I’m thinking we can get useful info off their site if necessary.

I mainly want to be able to see KR, short term fuel trims and long term fuels trims. So far the only one that appears to work right is LTFT.

Quote from gahammerle on March 3, 2011, 17:00
Quote from Tom on March 3, 2011, 15:59
I also have a Cobalt SS (2008) and the KR doesn’t seem to read right. It stays constant at 14.6 which makes no sense to me. Have you been able to get an accurate reading? Are the PIDs created in a similar fashion to say, HPTuners? If so I’m thinking we can get useful info off their site if necessary.

That’s what KR reads on my 2010 Camaro. I’m guessing it really is battery voltage.

That’s what I get for KR as well. Still haven’t tested that sensor yet. I will in about 10 minutes.

Oh and I figured out that it was crashing because you must use whole integers lol

Pardon me if is a dumb question, but is there a way to see what hex to use for certain PIDs? Would it be the same across multiple platforms? i.e. the hex to pull KR in HPtuners would be the same as the hex used in Torque?

Well the PID in HP tuners for that sensor is 6160, wondering if that’s a decimal number though as I could not get that number to work and forgot about trying to convert it to hex, which would be 18 10. Doubt that’s it though. I’ll mess with it later.

I wonder if this is because the turbo Cobalts use the Bosch ECU. Possible that the PIDs are completely different? I meant to test this on my mom’s ’06 2.2 Cobalt this weekend to see if it read any additional PIDs, but forgot.

Is there any way of asking the ECU what addresses it uses?

So the latest update has an a new PID for what looks like our widerange sensor, but not sure. It only reads in mV, though. Have you had a chance to play with it?

I also noticed that STFT and LTFT are fully functional now, which is a huge benefit. If we can get a good reading on O2 and KR I’ll be set!

You already did, but I’ll thank you again! Great find.

Knock I haven’t figured out, its manufacture specific and doesn’t enumerate like a normal PID does. I don’t even know how to send the proper command to query the ecu for it’s eOBD information. Might spend a small amount of money and get the other app for android with the GM extension to see if that’ll get me knock and try to decrypt it from there. Depending on the refund policy for that app I’ll hopefully get my money back.