foxbat

I've been using Ceddy's 1.20 MAF, I'm suspecting that knock control is not working as it's not pulling any timing when knock is encountered, although in my case the low oct table has significantly lower numbers than high oct.
As an example I had 5 counts of knock at 5000rpm load2byte 240, logged timing was 7, ECU didn't pull any timing, low oct values at the same area are -7s!

Is this a known issue with Ceddy 1.20 ?

Boltz.

iTrader: (42)

Do you have your octane value logged? Is this an Evo VI with a new maf and evo VIII ecu? A knock sum that small shouldn't trigger large changes in your effective timing, but the huge discrepancy between maps makes you wonder.

Do you not have any random logs that shower higher knock count? That would be a helpful place to start since a 5 count here or there isn't necessarily indicative of anything wrong.

todd6027

iTrader: (10)

6 counts of knock will pull timing

foxbat

It's an Evo V, you mean discrepancy between map & log or between hi & lo oct? I lowered low oct values for testing purposes. The max count I had was 5

I just learned that at GM. I believe that setting is through 'Octane update points' under knock control... correct?
I haven't used Ceddy's for some time now & I got worried.