Knock Learn Factor PID and formula? (Using Torque PRO, OBDLink MX)

[DarthZL1]

Using Torque Android App with OBDLink MX dongle.

Does anybody know what the PID and Formula is for Knock Learn Factor? Would greatly appreciate it.

Thanks...

[ytown87]

Id like to know as well. Just got the same stuff for mine last week. Its pretty fun to play with.

[danvillekidd]

I do not know about knock learn factor, I don't see one with that name. I do know that the knock retard and knock sensor active counter do work, or at least I had values for both last month when I was on a road course. The counter only had dashes, until an actual value showed. Disclaimer: I am still learning this myself.

[DarthZL1]

Originally Posted by danvillekidd

I do not know about knock learn factor, I don't see one with that name. I do know that the knock retard and knock sensor active counter do work, or at least I had values for both last month when I was on a road course. The counter only had dashes, until an actual value showed. Disclaimer: I am still learning this myself.

Actually the Knock Sensor Active Counter would be nice to have as well... do you still have the PID and formula for it? On my '14, it's always blank (not recognized as a valid PID).

The Knock Learn Factor is pretty interesting. Trying to fully understand it myself. It has something to do with both the knock sensor and the fuel tables. I won't try to explain it, as I would do a terrible job. Just trying to find more information about it.

[danvillekidd]

I am pretty sure that it was the same way for mine, as I didn't think it was working and deleted it before reading the logs from my track day. It was the standard pid from the scan. It may be that it doesn't send any info until it has something to send. The log showed dashes for the value until near the end when it changed to a 1.

[thahemp]

Knock learn factor sounds like burst knock. Burst knock shows up as KR in logs, but instead of being triggered by the knock sensors, it is the ECM predicting when knock might occur and retarding timing. I don't have HPT open in front of me right now, but there are tables you can zero out to eliminate burst knock completely.

[danvillekidd]

Reprogramming would be fine for someone who has a tune, some of us are just "looking". We are using the Torque App and looking for info on how to log this with it.

[DarthZL1]

Originally Posted by thahemp

Knock learn factor sounds like burst knock. Burst knock shows up as KR in logs, but instead of being triggered by the knock sensors, it is the ECM predicting when knock might occur and retarding timing. I don't have HPT open in front of me right now, but there are tables you can zero out to eliminate burst knock completely.

It does sound the same, but it seems to be recorded by others as "different". Thanks so much for the info, as well.

Before I try to tune anything (obviously I can't with what I have), I'd just like to log and understand it a bit better.

I tried using the Torque Scan plugin to get all the PIDs, but that takes literally forever, and my hour commute isn't long enough. I wish it had a PAUSE feature. Granted I'd just have a list of numeric PIDs, then, but it's a start.

Originally Posted by danvillekidd

Reprogramming would be fine for someone who has a tune, some of us are just "looking". We are using the Torque App and looking for info on how to log this with it.

What he said!

[thahemp]

Originally Posted by danvillekidd

Reprogramming would be fine for someone who has a tune, some of us are just "looking". We are using the Torque App and looking for info on how to log this with it.

Originally Posted by DarthZL1

It does sound the same, but it seems to be recorded by others as "different". Thanks so much for the info, as well.

Before I try to tune anything (obviously I can't with what I have), I'd just like to log and understand it a bit better.

I tried using the Torque Scan plugin to get all the PIDs, but that takes literally forever, and my hour commute isn't long enough. I wish it had a PAUSE feature. Granted I'd just have a list of numeric PIDs, then, but it's a start.



What he said!

I use the Torque app too. Not for logging anymore, but for clearing codes.

Can you point me to where you are seeing that they are different? I'm not sure what else it could be besides the burst knock multiplier. And burst knock operates off of other parameters... not fuel. More like IAT, ECT, cylinder air, MAP. I don't see the base burst knock table in HP Tuners. It might not be available.

[DarthZL1]

Sorry I misspoke. When I said fuel table, I was referring to what I've been reading in reference to the low and high octane spark tables. People suggest that the KLF is a multiplier between the two tables. A value of 1 would indicate using "low octane" settings completely, and 0 "high octane" settings. The values in between would be some sort of multiplier between the two.

This is just what I've read so far. I have no idea if it's right. It could very well be the same as burst knock multiplier! Starting to sound like it maybe.

Do you have the PID number and formula for that?

[danvillekidd]

If I remember correctly there is 2 different scans. one never worked, even on a several hour drive. The other did work, but I don't know what all may have been missed. I did get most of what I was looking for, but I don't see a knock learn factor. Would also like to see measured AFR work as well.
Next question is how accurate are the readings if they are not agreeing with the car? At some point I would like to get HPT, but it's not in the budget now.

[DarthZL1]

Originally Posted by danvillekidd

If I remember correctly there is 2 different scans. one never worked, even on a several hour drive. The other did work, but I don't know what all may have been missed. I did get most of what I was looking for, but I don't see a knock learn factor. Would also like to see measured AFR work as well.
Next question is how accurate are the readings if they are not agreeing with the car? At some point I would like to get HPT, but it's not in the budget now.

I'm in the same boat as you dealing with this. I have another scan tool (the one that goes with OBDLink MX), but it only has the generic OBDII PIDs. But, that seems to jive with what Torque is saying. But, as I mentioned in my other post and you confirmed, there seems to be some difference in what the DIC sees (specifically Oil temp), and what Torque sees. I just wish the OBDLink app had the extended GM pids so I could check.

I tried both scans (not at the same time, obviously). Neither finished in my 1 hour commute, even the quick scan. I'll try again, but for me, as soon as the screen orientation changes, I lose the scan. I just need to lock the screen before I do it next time.

[thahemp]

Here's how the burst knock settings look. It's a little more sophisticated than whether it's using the high or low octane spark table. I guess you won't really know what it is until you figure out what PID it is.

[DarthZL1]

Originally Posted by thahemp

Here's how the burst knock settings look. It's a little more sophisticated than whether it's using the high or low octane spark table. I guess you won't really know what it is until you figure out what PID it is.

Thank you for that. That's great! Yeah... starting to think now that the knock burst multiplier might be different than the KLF. But, then again, as you said, I won't know anything until I can actually get the PID and see WHAT it's saying. Also, the formula would be nice as well. If rumor is true, it's a floating point value between 0 and 1.

Also, looks like HPTuner VCM suite is a purchase in the near future. Hope it runs good in a VM! I'm not a huge Windows fan.