Extra PIDs from with OBDLink app

zaid3ssaf

Original poster
Member
Jan 1, 2020
151
Midwest
I've been playing around with my OBDLink MX+ and I wrote down some PIDs for 2002 oldsmobile bravada. I think most should work on any 2002-? 4.2L I6 vehicles. Personally, I find the OBDLink app very aesthetically pleasing and OBDLink MX+ could communicate with all of the modules.

1624115272613.png 1624115454013.png 1624115475659.png

Some of the codes I've tested and data that made sense was received. Other PIDs, data was received but didn't make sense or did not receive data at all. Here are the codes:

NameModule HeaderOBD modePIDEquationUnitConfirmed?
AC High side pressureECM2222114401(A*1.83)-14.7PSIData received from ECM and makes sense
Current gearECM22199A01AData received from ECM and makes sense
Engine oil pressureECM22147001A*3.985PSINot working (From @TJBaker57 )
Engine oil temperatureECM22115401A-40FData received from ECM and makes sense
EVAP?ECM22117001A/2.55%Data received from ECM not sure if it makes sense
Knock retard. Timing advance?ECM2211A601A*0.0878906degData received from ECM and makes sense
Misfire count cylinder 1ECM22120501AcountsData received from ECM and makes sense
Misfire count cylinder 2ECM22120601AcountsData received from ECM and makes sense
Misfire count cylinder 3ECM22120701AcountsData received from ECM and makes sense
Misfire count cylinder 4ECM22120801AcountsData received from ECM and makes sense
Misfire count cylinder 5ECM2211EA01AcountsData received from ECM and makes sense
Misfire count cylinder 6ECM2211EB01AcountsData received from ECM and makes sense
Misfire history cylinder 1ECM22120101(A*256)+BcountsCount stayed at 0. Possibly not working
Misfire history cylinder 2ECM22120201(A*256)+BcountsCount stayed at 0. Possibly not working
Misfire history cylinder 3ECM22120301(A*256)+BcountsCount stayed at 0. Possibly not working
Misfire history cylinder 4ECM22120401(A*256)+BcountsCount stayed at 0. Possibly not working
Misfire history cylinder 5ECM2211F801(A*256)+BcountsCount stayed at 0. Possibly not working
Misfire history cylinder 6ECM2211F901(A*256)+BcountsCount stayed at 0. Possibly not working
Oil life remainingECM22119F01A*0.392157%Data received from ECM and agrees with dash
Outside air tempECM22116101A-40FNot working
TCC slip speedECM22199101(A*256+B)/8RPMData received from ECM and agrees with RPM when stopped
Trans fluid tempECM22194001A-40FData received from ECM and makes sense
1-2 shift errorECM22199701A/40secData received from ECM and makes sense
2-3 shift errorECM22199801A/40secData received from ECM and makes sense
3-4 shift errorECM22199901A/40secData received from ECM and makes sense
1-2 shift timeECM22199301A/40secData received from ECM and makes sense
2-3 shift timeECM22199401A/40secData received from ECM and makes sense
3-4 shift timeECM22199501A/40secData received from ECM and makes sense

1624115786548.png 1624115819052.png

I think our trucks report all units in imperial then the software translates them to metric. I'm not sure so please correct me

1624115727613.png 1624115872939.png
 
Last edited:

TJBaker57

Member
Aug 16, 2015
2,907
Colorado
Here is a quick note about the Outside Air Temperature.

Your table pictured lists the module as "ECM" but the ambient air temperature sensor is not connected to the ECM. That sensor is connected to the HVAC module. And even if we were to change the PID definition in our app(s) we still cannot gain access to that data as the HVAC module does not support requesting data by PID number.

The same holds true for several other control modules such as the TCCM, and EBCM. So even in cases where I have the correct PID for a data point I still cannot get that data using apps like Torque Pro, OBD Fusion, Car Scanner, and others because the service 22 is not offered by those modules.
 

zaid3ssaf

Original poster
Member
Jan 1, 2020
151
Midwest
That makes sense. I couldn't request anything from ECBM either. I could only read DTCs from these modules. There were other PIDs for ABS sensors but nothing was returned from them either.
 

TJBaker57

Member
Aug 16, 2015
2,907
Colorado
I thin our trucks report all units in imperial then the software translates them to metric. I'm not sure so please correct me


Well considered yourself corrected then :wink:

The vehicle controllers report all data in International units. Most pressures (maybe all) are in kPa, Temperatures are in Celsius, force is Newton-Metres, and so on.

The apps we use usually will handle the conversions if we configure them to do. so.
 
Last edited:
  • Like
Reactions: zaid3ssaf

TJBaker57

Member
Aug 16, 2015
2,907
Colorado
That makes sense. I couldn't request anything from ECBM either. I could only read DTCs from these modules. There were other PIDs for ABS sensors but nothing was returned from them either.


There are some PIDs in Torque Pro that claim to get wheel speeds from ABS but they are bogus. While in Torque Pro they appear to show individual wheel speeds thay are in fact intercepting vehicle speed data.
 

zaid3ssaf

Original poster
Member
Jan 1, 2020
151
Midwest
The app is OBDLink which is the same as OBD fusion but its locked (and optimized) to work with OBDLink products. OBD fusion works with any dongle.
 
  • Like
Reactions: TJBaker57

TJBaker57

Member
Aug 16, 2015
2,907
Colorado
While I am at it....

The oil pressure PID will not work for any 4.2 LL8 because it has no oil pressure sensor, instead only an oil pressure switch only offering ON-OFF operation.

And the oil temperature and level sensor was only on the 2002 model year engines.
 

zaid3ssaf

Original poster
Member
Jan 1, 2020
151
Midwest
While I am at it....

The oil pressure PID will not work for any 4.2 LL8 because it has no oil pressure sensor, instead only an oil pressure switch only offering ON-OFF operation.
That's correct. I know its all made up numbers but I was just hoping it would match the lies the gauge cluster displays.
 

TJBaker57

Member
Aug 16, 2015
2,907
Colorado
That's correct. I know its all made up numbers but I was just hoping it would match the lies the gauge cluster displays.


That can only be done in Torque Pro as of this writing. Even there I think it was never intended to work this way. I get the data not by requesting a PID at all but rather putting a request out on the serial data stream using not a physical node address but a functionally addressed message using informations gleaned from SAE-J2178


I have emailed with the OBD Link folks about it but it seems extremely unlikely that any future update might enable it as the app was never intended to be used in that manner. Plus I may be the only user to have attempted such a thing.
 

Forum Statistics

Threads
23,399
Posts
638,837
Members
18,614
Latest member
dakis

Members Online