Extra PIDs from with OBDLink app

[ZD3SF]

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.



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:

Name	Module Header	OBD mode	PID	Equation	Unit	Confirmed?
AC High side pressure	ECM	22	22114401	(A*1.83)-14.7	PSI	Data received from ECM and makes sense
Current gear	ECM	22	199A01	A		Data received from ECM and makes sense
Engine oil pressure	ECM	22	147001	A*3.985	PSI	Not working (From @TJBaker57 )
Engine oil temperature	ECM	22	115401	A-40	F	Data received from ECM and makes sense
EVAP?	ECM	22	117001	A/2.55	%	Data received from ECM not sure if it makes sense
Knock retard. Timing advance?	ECM	22	11A601	A*0.0878906	deg	Data received from ECM and makes sense
Misfire count cylinder 1	ECM	22	120501	A	counts	Data received from ECM and makes sense
Misfire count cylinder 2	ECM	22	120601	A	counts	Data received from ECM and makes sense
Misfire count cylinder 3	ECM	22	120701	A	counts	Data received from ECM and makes sense
Misfire count cylinder 4	ECM	22	120801	A	counts	Data received from ECM and makes sense
Misfire count cylinder 5	ECM	22	11EA01	A	counts	Data received from ECM and makes sense
Misfire count cylinder 6	ECM	22	11EB01	A	counts	Data received from ECM and makes sense
Misfire history cylinder 1	ECM	22	120101	(A*256)+B	counts	Count stayed at 0. Possibly not working
Misfire history cylinder 2	ECM	22	120201	(A*256)+B	counts	Count stayed at 0. Possibly not working
Misfire history cylinder 3	ECM	22	120301	(A*256)+B	counts	Count stayed at 0. Possibly not working
Misfire history cylinder 4	ECM	22	120401	(A*256)+B	counts	Count stayed at 0. Possibly not working
Misfire history cylinder 5	ECM	22	11F801	(A*256)+B	counts	Count stayed at 0. Possibly not working
Misfire history cylinder 6	ECM	22	11F901	(A*256)+B	counts	Count stayed at 0. Possibly not working
Oil life remaining	ECM	22	119F01	A*0.392157	%	Data received from ECM and agrees with dash
Outside air temp	ECM	22	116101	A-40	F	Not working
TCC slip speed	ECM	22	199101	(A*256+B)/8	RPM	Data received from ECM and agrees with RPM when stopped
Trans fluid temp	ECM	22	194001	A-40	F	Data received from ECM and makes sense
1-2 shift error	ECM	22	199701	A/40	sec	Data received from ECM and makes sense
2-3 shift error	ECM	22	199801	A/40	sec	Data received from ECM and makes sense
3-4 shift error	ECM	22	199901	A/40	sec	Data received from ECM and makes sense
1-2 shift time	ECM	22	199301	A/40	sec	Data received from ECM and makes sense
2-3 shift time	ECM	22	199401	A/40	sec	Data received from ECM and makes sense
3-4 shift time	ECM	22	199501	A/40	sec	Data received from ECM and makes sense

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

 

[TJBaker57]

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.

 

[ZD3SF]

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]

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

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.

 

[TJBaker57]

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.

 

[TJBaker57]

What is the app you pictured here??

It looks that same as OBD Fusion.

 

[ZD3SF]

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.

 

[TJBaker57]

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.

 

[ZD3SF]

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]

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.