I hope that I am not missing the obvious, but I can not seem to find the knock count in my datalogging on Tunerpro RT. Hopefully someone will be able to point me in the right direction.

thanks,

 

Knock Count is in the ALDL values Tab
last section title "-=Spark, etc=-

 

I still don't see it. I only see a line item "Knock Retard" with a value in units. Is that the count?

thanks,

 

Knock Retard (a much more useable value to the user) is expressed in degrees of retard being applied as a result of filtered knock counts.

 

I think that not all ALDL streams support knock counts.

What ECM and code are you using?

 

Thanks for the help on this. Using Datamaster it does show knock counts, but I mainly use Tunerpro. The limitations of Knock Retard is that it does not show how many times you hit it. If I have a large number of knock counts then I know I have an issue to deal with. If it only shows knock retard than maybe it only triggered it a couple of times which I would find normal.

I have:
16147060
$85

 

The problem dealing with knock counts is that it's fairly useless information. It's every noise the sensor hears, which means you don't know whether it's real knock or any other noises the engine makes.

It's unfiltered noise. Even the starter will kick up your knock counts. Trust me, knock counts isn't telling you anything useful. Let the system do it's job and filter out non real detonation noises, and display and act upon (knock retard) real detonation.

 

This isn't really correct. Knock counts are what the ECM directly responds to. Counts are from the ESC filter pulling the ESC signal to the ECM low (even with the ESC filter on the MEMCAL).

The ECM will then retard the timing relative to the change in counts. The only time the ECM won't retard the timing from knock counts is when at idle.

Some ECMs don't even report spark advance let alone knock retard. But most (all?) report at least the high byte of the knock counter. Of course this causes confusion as there can be knock, counts, and retard without the ALDL reporting any additional knock counts.

Now looking at the $85 data stream , it shows that both the MSB & LSB of the knock counter are output.

The stream also outputs the SA relative to TDC, and relative to the DRP. Typically the difference between these two values is the base timing and any knock retard. With that you may be able to pull out the knock retard value.

RBob.

 

What are you using for a ADS definition?

I have a friend with a '70 or '71 Olds Cutlass using a 7060.

I have the bin files from a couple MEMCALs he had and the checksum byte indicates that it would be $D8, but after some searching on here, found the indication that $85 could work for an xdf, which it seems to be correct. Do you have a disassembly for this ECM/mask? The xdf I have is very limited in what has been defined and would like to add more to be able to have more ability to fine tune this car.

--==EDIT==--

I think I found the files I need.

 

Six-shooter: I found my $85 XDF on Craig Moates site. Let me know if you have trouble tracking it down.

Thank you all for the info so far. I will continue to dig through this. Every step of the way is a learning oportunity.

 

OK, to build on an old thread I had:
Using TunerPro
During normal driving, idle, cruise, WOT, etc. The Knock Retard counter is ALWAYS reading between 22 and 25 "units". First question is "units" the same as degrees? Second, is this saying that I am driving around with 25 degrees of knock retard? (could I have the wrong knock sensor?)

What is the MSB and LSB of the knock counter?

thanks much,

 

I dont think the retard could be 25 degrees in total? My tune limits to 3 deg yet I have a log of KC events numbering 150. I suspect it pulls timing 1-2-3 during the event and then resets timing. I have been looking at my KC now past month. I cant tell if real or mechanical. I will know after I add 50/50 race fuel. Mine occurs only while acceerating moderately 1.2.3 gears stick. Occurs only 2000-2400 rpm 40-50 map.

Does anyone think 29-30d SA at that area of SA table is too much(10.0/1 CR aluminum heads 92 octane E10)?

 

Mine is not KC events, it is the Knock Retart Counter and is always (from start up to shut down) between 22 and 25 "units". I do not know what "units" is or what it refers to. It certaily does not run like it has that kind of Spart retarding, but I still want to know what the counter is telling me.

 

The knock counter is accumulative. It starts at 0, goes to 65,535, and rolls back over (like an odometer). Any counts that occur before the engine is running is to be ignored. Any counts that occur when the key is shut off is to be ignored.

Note that the counter is actually 2 bytes (MSB & LSB). Many ECMs only put the MSB into the data stream. This is how you can have spark retard but the counts didn't change. And in this case the counter goes from 0 to 255 and back around again. You are only getting 1/256th of the real count.

RBob.

 

My Knock Retard does not respond anything like that. I just went for a short drive of 20 minutes or so and observed the display in TunerPro:
The cell in the dash reads "Knock Retart" bellow that is the measurement, then bellow that it reads "units".
Under most driving and idle conditions the display reads 25.84. This number ONLY changes to 22.50 at what appears to be when I go to WOT (if anything it is more a function of RPM than throttle position). When I back off the throttle it imeadiatly goes back to 25.84.
I shut the motor off for a few minutes then restarted and drove with the exact same results.

 

I'd venture to guess that the .ads file is incorrect.

RBob.