Scanner/datalogger that reads enhanced PIDs

Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.

chrisbh17

Senior Member
Joined
Oct 12, 2017
Posts
6,691
Reaction score
7,473
Ram Year
2017
Engine
Hemi 5.7
Anyone know of an inexpensive scanner/datalogger than can read "enhanced" PIDs?

Specifically trying to find out if my engine is pinging (backstory: Im hearing a slight tinny noise under light load around 2K RPM....could be rattling shield or pinging, cant tell for sure), so I would need to be able to see the STKR and LTKR (short term and long term Knock Retard) values.

Thanks in advance.

-Chris
 

Rampant

Senior Member
Joined
May 21, 2016
Posts
1,895
Reaction score
1,834
Location
NJ
Ram Year
2016
Engine
392 Hemi
Anyone know of an inexpensive scanner/datalogger than can read "enhanced" PIDs?

Specifically trying to find out if my engine is pinging (backstory: Im hearing a slight tinny noise under light load around 2K RPM....could be rattling shield or pinging, cant tell for sure), so I would need to be able to see the STKR and LTKR (short term and long term Knock Retard) values.

Thanks in advance.

-Chris

I think the least expensive would be the Torque Pro App. As long as you have an Android device and an OBD2 bluetooth adapter, you can pretty much get any PID available. If not, you could buy any $50 Android tablet, the OBD2 bluetooth adaptor, and the app all for under $100. I've used it for 8 yrs or so now on many different cars and it is impressive for the cost to say the least. Here's a short vid on how to get PIDs with the app. It just so happens the PIDs you are looking for are the first ones he pulls up in the vid. Hope this helps!
 
OP
OP
C

chrisbh17

Senior Member
Joined
Oct 12, 2017
Posts
6,691
Reaction score
7,473
Ram Year
2017
Engine
Hemi 5.7
Thanks.

I actually do have Torque pro and a bluetooth OBD adapter. The issue is that I cant find the PID value for Chrysler/Mopar/RAM knock sensor. Im guessing its not the same as GM (which is the one in the vid you linked to).

Which is why I was hoping to find an actual scan tool that could already read the extended PIDs that seem to be manufacturer-specific.

I know the AutoEnginuity can do it, Diablo, HP Tuners, etc. But I didnt want to spend that kind of $$$ just for data logging purposes (I dont plan on tuning the truck, just curious if its knocking or just rattling)
 

Tach_tech

Senior Member
Joined
Jun 1, 2014
Posts
3,307
Reaction score
3,555
Ram Year
2017
Engine
5.7L HEMI
There is no long/short term values for knock retard on your truck.
 
OP
OP
C

chrisbh17

Senior Member
Joined
Oct 12, 2017
Posts
6,691
Reaction score
7,473
Ram Year
2017
Engine
Hemi 5.7
Really? So it doesnt do anything with values from knock sensors? Or is there just no way to see them?

Seems odd.
 

Tach_tech

Senior Member
Joined
Jun 1, 2014
Posts
3,307
Reaction score
3,555
Ram Year
2017
Engine
5.7L HEMI
There will be knock retard/spark advance/base spark, but there is no long/short term values for knock retard like there is fuel trims.
 
OP
OP
C

chrisbh17

Senior Member
Joined
Oct 12, 2017
Posts
6,691
Reaction score
7,473
Ram Year
2017
Engine
Hemi 5.7
There will be knock retard/spark advance/base spark, but there is no long/short term values for knock retard like there is fuel trims.

Good info, thanks!

I can read "timing advance degrees" but still cant find base spark or knock retard. Again Im assuming they are extended PIDs.

Just for the heck of it I logged a trip around town and saw some negative values for timing advance, but they seem to correspond to slowing down, backing out of the throttle, etc. Still not sure if Im getting engine "pinging" or just a rattling noise. There doesnt seem to be any negative values for timing advance at the RPMs I think I hear pinging, so its possible Im just hearing things or something is rattling at the magic 2000 RPM range.
 

Tach_tech

Senior Member
Joined
Jun 1, 2014
Posts
3,307
Reaction score
3,555
Ram Year
2017
Engine
5.7L HEMI
It’s really hit or miss which scanners will show certain pids. For example the factory wi tech does not show any short/long term knock retard data, even though it exists. However my diablosport t2 does.
 

danielmid

Senior Member
Supporting Member
Joined
Mar 23, 2018
Posts
1,491
Reaction score
2,647
Location
Southeast WI
Ram Year
2015 Sport 4x4
Engine
Hemi 5.7
HAHA ! you rock homie! let us know if it works out ......
Idled for a minute while walking the dog in the rain, only one value did anything other than sit at a constant value.

And it only changed with some throttle. I'll run a log driving to work tomorrow on this one PID and see if it does anything other than bounce between the two values.

Screenshot_20221110-184730.png
 

danielmid

Senior Member
Supporting Member
Joined
Mar 23, 2018
Posts
1,491
Reaction score
2,647
Location
Southeast WI
Ram Year
2015 Sport 4x4
Engine
Hemi 5.7
Look a page back, I showed the PID values that come up for "knock"
 

danielmid

Senior Member
Supporting Member
Joined
Mar 23, 2018
Posts
1,491
Reaction score
2,647
Location
Southeast WI
Ram Year
2015 Sport 4x4
Engine
Hemi 5.7
Have you logged the knock sensor voltage at all?
Not yet, I'll try and throw that on the log tomorrow also.

Also just for some semblance of data, my tank is a roughly 50/50 mix of 89 E10 and 91 E0 right now, not tuned.
 

danielmid

Senior Member
Supporting Member
Joined
Mar 23, 2018
Posts
1,491
Reaction score
2,647
Location
Southeast WI
Ram Year
2015 Sport 4x4
Engine
Hemi 5.7
Not yet, I'll try and throw that on the log tomorrow also.

Also just for some semblance of data, my tank is a roughly 50/50 mix of 89 E10 and 91 E0 right now, not tuned.

Well the logging didn't work in OBDLink like I thought, graphing was showing the knock sensor #1 and #2 voltage, engine speed, and the knock sensor from above. Saved the drive to work, exported the log, and it contains time/lat/long/vehicle speed. That's all. So I'm going to try and find these sensors in Torque Pro and see if the logs there work better.

(Lat/long had accurate values, I wiped them for the screenshot, and filtered the stopped at 0 mph times out)
1668185798165.png
 

danielmid

Senior Member
Supporting Member
Joined
Mar 23, 2018
Posts
1,491
Reaction score
2,647
Location
Southeast WI
Ram Year
2015 Sport 4x4
Engine
Hemi 5.7
Well the logging didn't work in OBDLink like I thought, graphing was showing the knock sensor #1 and #2 voltage, engine speed, and the knock sensor from above. Saved the drive to work, exported the log, and it contains time/lat/long/vehicle speed. That's all. So I'm going to try and find these sensors in Torque Pro and see if the logs there work better.

(Lat/long had accurate values, I wiped them for the screenshot, and filtered the stopped at 0 mph times out)
View attachment 506658
Well I made no progress. I can't find the same PIDs in TorquePro to log them there, and no matter what I do in OBDLink the log only dumps out time/lat/long/speed.
 
Top