When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Didn't work... I tried the 'Alternative' PID, too.
None of the 3 Knock PID's in Toque seemed to do anything. The 11a6 said no data received in OBDLink. Didn't try 125d in OBDLink, but it registered a constant -1 degree in Torque.
The Knock Sensor never moved in the short drive I tested it with.
Do these work on your 0411?
Does this help with IDC?:
IDC is not a scale of x pulsewidth is y duty cycle. It is a calculation. I don't know how you'd set it up in EFI Live, but it's a given custom PID in HP Tuners.
IPW = injector pulse width in ms
RPM = engine speed
IDC = injector duty cycle
So, it turns out that I do get data on these 3 Knock PID's sometimes.
Any idea why it might not be always reporting?
If, for instance, the wire from one or both Knock Sensors had a bad wire, would the data report 'no data'? It seems like it should just report 0.
I don't have any real reason to suspect my wiring, but I guess I'll have to check it now. I'm attaching a couple .csv logs from Torque if anybody would like to look them over and maybe give some feedback.
I guess I should start another thread on this old truck...
one of 2 things. the OBD2 Bluetooth isn't seated in the connector al the way so the contacts aren't touching each other or your OBD2 adapter may be faulty or the OBD2 connector itself may be lose wire somewhere. I notice that if I don't fully plug my adapter in the connector, it'll have error reading/connecting to the pcm
I'd just keep the first one "[GM]Knock Retard(Deg.)" - It seems to be operating normally. A few degrees are pulled when knock is detected, then you can see it decay back to zero. On that note, you might want to use that field to hunt down whatever is causing that knock.
...and I'd just stop logging the other 2 fields "[GM]Knock Retard(Alternative)(Deg.)" and "[GM]Knock sensor active counter(Count)"
Well, during the time that either they just sit at 0 or when one 'gauge' is actually displaying No Data, all the other sensors are reporting fine...Plus, I've never really had any trouble with the OBD2 Port connection.
I guess sitting at 0 is actually what I want, but I'm trying to figure out why I get bunch of timing retard just off throttle...see one of my other threads on this old truck...
I'd just keep the first one "[GM]Knock Retard(Deg.)" - It seems to be operating normally. A few degrees are pulled when knock is detected, then you can see it decay back to zero. On that note, you might want to use that field to hunt down whatever is causing that knock.
...and I'd just stop logging the other 2 fields "[GM]Knock Retard(Alternative)(Deg.)" and "[GM]Knock sensor active counter(Count)"
Sometimes the KR is the one that says No Data while the other 2 ARE reporting data...?
its supposed to read no data most of the time. if the pcm registers KR it'll come up on the scan depending on the type of gauge you have. I have mine with the highest and lowest values along with the current reading.
like computerz said,use the GM knock retard degrees. don't bother with KR Count or the alternative. for the KR degrees, set the max value to 15 and config the display(I use the square shaped ones) to show highest and lowest on there. that way you know what your highest KR registered was as you're not constantly glancing back and forth between the device and the road.
also might as well move the KR degree parameter to a new window and include other parameters such as RPM, throttle %, timing adv, and anything else you may want to add.
08-16-2017, 05:02 PM
PID for Knock on 0411 ECM 
