I have done some logging using evoscan before and I have always been able to log knock but only recently it stopped working. I do not have any CELs on. The only thing is when I try to log load, afr, etc I cannot see any knocksum. I looked up the definition for it and it is only listed as "x" Am I missing come sort of calculation of some sort? thanks

 

need help asap please if anyone can help me out...

 

Do you have "Knock Sum" checked inside EvoScan so that it's logged? Does Knock Sum show any values in EvoScan when it's logging? Cause if its not logging in EvoScan's interface it won't be logged to file.

 

ya i have the checkbox checked to log but it doesn't show any values when i do log.

 

Is the request number 26? Also, is it not showing any values at all or it only shows zero?

 

request number is 26 but it doesn't show any formula on how to calculate knocksum... Only shows zero when I am logging

 

this problem is really buggin me now... Wanna mess with some of my afr map but without knowing the knock Im afraid to do so... A faulty knock sensor would throw a CEL right cuz I dont have any lights on...

 

bump really need the help...

 

bought a new knock sensor. Backordered for a week. Guess ill jus swap it out and see if it fixes the prob

 

If you had a bad sensor I'd imagine you'd be throwing a code. But, at this point it seems like the only logical solution. Did you try uninstalling and reinstalling EvoScan and the FTDI USB drivers for the Tactrix cable? Also, what version of EvoScan are you using?

 

evoscan 2.5 the newest version tried reinstalling when i downloaded the newest one. and how do i go about reinstalling the drivers for the tactrix cable?

 

awe crap.... so i changed out the sensor.. checked all the grounds then i had a revalation... Knocksum displays 0 at idle. i was only checking the knocksum values at idle expecting to see knocksum values, stupid me..... Tried a wot pull and guess what.. knocksum read 2 just as its supposed to. thanks everyone for the help though.. haha