have some knock questions

on data master whats the difference between knock and knock count? it seems like i have a high number of knock count usually in the 13,000 or more. But in the knock tap is doesnt say anything, and im pretty sure i have it set up to beep when theres knock. At what knock count should i be worried about?
 

MikeRenz

not stock
Re: have some knock questions

knock is current knock. knock count is # data frames that have seen knock (iirc). There is nothing you can do about knock count, as its already occurred. Current knock, if its not known to be false, you should be at least takin your foot off the pedal. :lol:
 
Re: have some knock questions

so is 15,000 knock count bad? If data master doesnt detect knock but there is still a knock count does that mean that there is still knock? Im sorry i dont really understand it yet. Wont DM tell me with some kind of window when is sees knock?
 

Tooky

Serious about performance
Re: have some knock questions

Something worth noting is that DataMaster 3.3.0 (the original version that was widespread several years ago) records the Knock Count in a MUCH different manner than all versions 3.4.1 and beyond. 3.3.0 only increased the Knock Count when "serious" knock occurred. So it was typical to see numbers of 0-3 Knock Count until you had actually knocked. If you saw a knock count of 30, you could generally find it in the datalog.

With the newer versions of DataMaster, the knock count is always in the thousands and becomes useless since you can't easily determine whether or not the engine has been knocking.

To see the knock you should double-click on one of the 4 white graph items on the lower right corner of DataMaster, and change the item to Knock Retard, and then check the graph for spikes in that color.
 

leroy

Donating Member
Re: have some knock questions

Most trucks get quite a few knock counts on startup. After that, they should be pretty quiet.

Some software looks at the MSB, some at the LSB (most significant byte and least significant byte).

I still like to look at the knock counter. That will help identify the frame where the acoustic event occurred. If you look at knock retard, the esc attack and decay rate can be misleading.

Jim
 

Andreas

New member
Re: have some knock questions

leroy said:
Most trucks get quite a few knock counts on startup. After that, they should be pretty quiet.

True, I always have 617 knock counts at start up.
 

hatrik8

Donating Member
Re: have some knock questions

Tooky said:
To see the knock you should double-click on one of the 4 white graph items on the lower right corner of DataMaster, and change the item to Knock Retard, and then check the graph for spikes in that color.

I don't have Knock Retard on my Datamaster v351. I have spark retard? Is that the same.
 

Flyin Ryan

hated cuz he drives fords
Re: have some knock questions

You want to worry about "spark retard" and like previously stated "knock count" is pretty much useless.. Also im not sure what version your using but I know on 3.51 and 3.41 you can't set the program to beep when your receiving knock only peeps when you receive a DTC error or engine code so make sure when your doing runs and if you don't feel like seeing a spark retard (knock) in the lower graph you can get a bigger meter type of display by going to view/knock retard from the top menu which is larger and easier to see imo
 

turbodig

Active member
Re: have some knock questions

blktyphoon said:
on data master whats the difference between knock and knock count? it seems like i have a high number of knock count usually in the 13,000 or more. But in the knock tap is doesnt say anything, and im pretty sure i have it set up to beep when theres knock. At what knock count should i be worried about?


Knock count is the actual hardware count of the knock sensor as it's happening, all the time.

Knock retard is the computer's interpretation of knock count, based on tables that are RPM specific.

Knock count can increment anytime. Knock retard will only occur above ~2k RPM or so, depending on which calibration you're running.

Best thing is to log it, and find out where the counts are increasing. You can graph it over time to pinpoint exactly what's happening.

"Normal" is no counts or knock. If you've got phantom counts, it'd be a good idea to figure out why.
 
Top