Knock sum anomalies

[burgers22]

I have at long last got to to some tuning. During these runs I've noticed that ECU+ is showing rather a lot MUT knock sums and these knocks, even when over 3 don't cause the stock ECU to pull timing, something I've never previously seen. I had a MUT knock of 5 at 6400 on a WOT run at 17PSI with no timing pull, the timing map has 8 for this load cell.

The above is not the only odd piece of data, I'm getting lots of 1 and 2 counts even on vacume, in a previously very low knock tune. I'm guessing ECU+ is using MUT request 26h. Anyone else seeing anything strange?

MB

[honki24]

I'm finding anywhere from similar to less knock than I did with mituslogger... lol and that's at 25psi, 3ish degrees timing and 13ish AFR.

(my car is still in shambles, the tune is way off)

[burgers22]

Thanks, the odd thing here is the stock ECU is not pulling timing as I'd expect, usualy you'd see 2 deg for a knock count for every 3 counts.

Having MUT logging and map tracing are really nice, I'm alos getting into the idea of meth injection and switchable maps.....

MB

[burgers22]

I've come to the conclusion, that I'm seeing more knock activity because the ECU+ has a logging rate much greater than the other MUTII loggers out there. So another big + for ECU+
MB

[honki24]

Now that I've gotten into my tune more I agree. I see little 1 and 2 spikes all the time. I do see knock sums w/o timing pulls but they are very breif. I love looking at all of this in graph form... so much easier than when I'm tuning someone else's car w/ mitsulogger and excel.... blah. I'd agree that ECU+ seems to log much faster than other loggers, which is ususally good. Now if we could get an adjustable smoothing factor for choppy graphs (like AFR, boost) the small negatives of super-fast logging would dissapear too.

EDIT:
I'm seeing an average of 1 data entry every .04 seconds with ECU+
I'm seeing an average of 1 data entry every .11 seconds with mitsulogger

ECU+ is clearly over twice as fast.

Double Edit:
5000rpm = 2500 combustions per minute = 150,000 combustions per second (A combustion is happening every 0.00000667 seconds)
At 0.11 second intervals you are skipping 16500 combustions
At 0.04 second intervals you are skipping 6000 combustions

With a logger like Mitsulogger or Evoscan you lose information on an extra 10,000 combustions per data entry at 5K RPM.

Triple edit:
infinite loop of doom: http://forums.evolutionm.net/showthread ... ost5287357

[rogersmith]

One small mistake I think you made Honki.

2500 combustions/min = 41.67 combustions per second

So with ECU+ at 25 samples/sec you miss at most 1 combustion a second if my calculation is correct.

[honki24]

lol, true. multiplied when I sould have divided... Suppose that's what happens when you leave college and go out into the "real world" lol... you start sucking.

[burgers22]

Hi

Yep, I've pretty much come the the same conclusion, that the greater resolution available with ECU+ is why I am seeing more knock, especially at part throttle.

MB