Knock Retard Scanner Update : VCM Suite Beta 3.7.951+

[Eric@HPTuners]

Reporting Knock on Ford has been confusing in the past.

Our Knock Retard parameter shows positive value to be actual knock retard, and a negative value being the PCM adding timing over what is being commanded. I made it report this way so that the default scanner config with knock retard would show properly in VCM Scanner graphs and dashboard.

Today we created a new parameter, "Knock Correction" that reports the same data as Knock Retard, but the output is scaled so that a positive value is adding timing, and a negative value is pulling timing (from knock). This new parameter will not be selected in the default configs or show on the charts unless you add it.

This change makes the global and individual cylinder modes of knock control report values the same way.

I hope this clears up any confusion.

[GHuggins]

Thank You Eric... Makes tuning on Fords for those of us who don't tune them daily a little easier to remember

[Jn2]

Reporting Knock on Ford has been confusing in the past.

Our Knock Retard parameter shows positive value to be actual knock retard, and a negative value being the PCM adding timing over what is being commanded. I made it report this way so that the default scanner config with knock retard would show properly in VCM Scanner graphs and dashboard.

Today we created a new parameter, "Knock Correction" that reports the same data as Knock Retard, but the output is scaled so that a positive value is adding timing, and a negative value is pulling timing (from knock). This new parameter will not be selected in the default configs or show on the charts unless you add it.

This change makes the global and individual cylinder modes of knock control report values the same way.

I hope this clears up any confusion.

so "Knock correction" is it's own PID and as long as i don't pick it to log in channels, my KR will still work like normal right? (-) being timing added and (+) being timing pulled?

Can we still log both knock correction and Knock retard to make sure it adds up, say correction shows +3, than KR should show -3

[Braden@HPTuners]

so "Knock correction" is it's own PID and as long as i don't pick it to log in channels, my KR will still work like normal right? (-) being timing added and (+) being timing pulled?

Can we still log both knock correction and Knock retard to make sure it adds up, say correction shows +3, than KR should show -3

Yes, both parameters are available to log at the same time.

[Ortiz]

so "Knock correction" is it's own PID and as long as i don't pick it to log in channels, my KR will still work like normal right? (-) being timing added and (+) being timing pulled?

Can we still log both knock correction and Knock retard to make sure it adds up, say correction shows +3, than KR should show -3

You can log both at the same time and confirm it through the OAR as well.

[Ben Charles]

Very nice....
Use to tuning GM, always tripped me out initially ha

[Yagermeister]

Reporting Knock on Ford has been confusing in the past.

Our Knock Retard parameter shows positive value to be actual knock retard, and a negative value being the PCM adding timing over what is being commanded. I made it report this way so that the default scanner config with knock retard would show properly in VCM Scanner graphs and dashboard.

Today we created a new parameter, "Knock Correction" that reports the same data as Knock Retard, but the output is scaled so that a positive value is adding timing, and a negative value is pulling timing (from knock). This new parameter will not be selected in the default configs or show on the charts unless you add it.

This change makes the global and individual cylinder modes of knock control report values the same way.

I hope this clears up any confusion.

Is this new parameter only for Copperhead and up or is it also for the 2010 GT500 which received knock sensors as well? If the knock correction parameter is also for it is it simply reverse like the knock retard currently is?

[Steven@HPTuners]

Is this new parameter only for Copperhead and up or is it also for the 2010 GT500 which received knock sensors as well? If the knock correction parameter is also for it is it simply reverse like the knock retard currently is?

It will show up on any Ford vehicle that reports the parameter we call Knock Retard. Basically that parameter will be available to be selected as both "Knock Retard" which is consistent with how "Retard" is interpreted (positive = retard, negative = advance), and "Knock Correction" which is additive and how Ford actually uses the parameter (positive = advance, negative = retard).

[Yagermeister]

It will show up on any Ford vehicle that reports the parameter we call Knock Retard. Basically that parameter will be available to be selected as both "Knock Retard" which is consistent with how "Retard" is interpreted (positive = retard, negative = advance), and "Knock Correction" which is additive and how Ford actually uses the parameter (positive = advance, negative = retard).

Steven I was under the impression that when Eric made the changes regarding how knock is interpreted in this post (https://www.hptuners.com/forum/showt...Positive+knock) that he made the change only for Copperhead and Tricore meaning the Spanish Oak ecu's interpret opposite like so:

Copperhead and Tricore Processors
positive value = KNOCK
negative value = PCM Adding timing

Spanish Oak and older Processors
positive value = PCM Adding timing
negative value = KNOCK

A. is the above correct?
B. is the new parameter (Knock Correction) simply opposite whichever way your ecu reads Knock Retard. Would that be correct?

[Steven@HPTuners]

Steven I was under the impression that when Eric made the changes regarding how knock is interpreted in this post (https://www.hptuners.com/forum/showt...Positive+knock) that he made the change only for Copperhead and Tricore meaning the Spanish Oak ecu's interpret opposite like so:

Copperhead and Tricore Processors
positive value = KNOCK
negative value = PCM Adding timing

Spanish Oak and older Processors
positive value = PCM Adding timing
negative value = KNOCK

A. is the above correct?
B. is the new parameter (Knock Correction) simply opposite whichever way your ecu reads Knock Retard. Would that be correct?

Ah okay, this is something I misunderstood when you asked. I see what you're asking now.

The idea is to make them all the same. The older Oak processors reported Knock Retard as you're saying. We're updating these to rename Knock Retard to Knock Correction to be consistent.
The goal is so that anything reporting "Knock Retard", +Retard/-Advance, "Knock Correction", +Advance/-Retard

The Oak processors will have this update in a soon-coming Beta, but yes, at this point "Knock Retard" for the Oak and older work that way.

This confusion is part of why we're updating all of these to be consistent.

[Yagermeister]

Ah okay, this is something I misunderstood when you asked. I see what you're asking now.

The idea is to make them all the same. The older Oak processors reported Knock Retard as you're saying. We're updating these to rename Knock Retard to Knock Correction to be consistent.
The goal is so that anything reporting "Knock Retard", +Retard/-Advance, "Knock Correction", +Advance/-Retard

The Oak processors will have this update in a soon-coming Beta, but yes, at this point "Knock Retard" for the Oak and older work that way.

This confusion is part of why we're updating all of these to be consistent.

Thank you Steven for the clarification!

[dan_t]

Trying to scan an 04 F150 3v 5.4 - MPVI2 and VCM software 4

The only Knock PID's I can find are Sensor Voltage 1 & 2. Is there anything else I can search for?