bsbllfit7

Hey all, I am trying to tune my car currently and just noticed that whenever there is 1 count of knock, the timing is getting pulled by a degree as well. 2 Counts = 2 degrees and so on. This makes it tough to tune because the counts will go to 1 then back to 0 then back to 1 and so on and so forth. Timing map is very smooth and goes from 9-4 at peak torque then back up to 7 degrees roughly. I am using tephramod v7 with SD so I am not sure if there is a setting within the rom that I need to manipulate. On my old rom it was every 3 counts of knock was a degree of timing. I would like to get back to that methodology.

bsbllfit7

No one has any answers?

LetsGetThisDone

iTrader: (1)

what fuel? how much boost?


4* at peak torque sounds like a lot on pump gas..

bsbllfit7

This is on 92 pump. 25 psi on an fp red at peak torque. I just dont understand why whenever it shows knock its also pulling timing, even if its only .5 counts of knock.

LetsGetThisDone

iTrader: (1)

I've never had to look into that. My rom's have always done what your old one did, which is 3 counts of knock pulls one degree.

bsbllfit7

Exactly, which Im ok with it being a safer alternative, but ive also read that an occasional 1-2 count of knock isnt harming anything.

LetsGetThisDone

iTrader: (1)

No, its really not. 1-2 counts is hard to believe as even being real, especially if its only occasional.

bsbllfit7

No one has any advice as to what to look at within the rom or what could be causing this?

kaj

iTrader: (60)

That's how it works. Knock= reduced timing.

bsbllfit7

but 3 counts of knock usually results in 1 degree timing pull. Not 1 count knock 1 * pulled timing. I have also realized that it is not achieving the timing on the map in the higher rpms even when there is no knock on the log. I'm wondering if this is because I am using the mrfreds 3rd fix for the stutter? I don't think i noticed it prior to that changeover.

kaj

iTrader: (60)

Ooooh. I gotcha. That is weird. Subbed for a fix.

ridenrunwv

Did you change your 2byte to 1byte Load Factor in your tune or in Evoscan?

The timing that you log should follow the timing map in your tune if you are not getting knock. The ECU will interpolate your map though so it isn't a direct jump between cells. So if you're 14 degrees at 7k and 18 at 8k logging you'll be 16 at 7500 for example.

If you do not have matching values in your 2byte to 1byte Load Factor and your Evoscan definition the load you are logging will not correspond to the load in your map though. This can lead to things that appear strange because the load you look at in your log does not match the load in your tune.

bsbllfit7

load factors match up. After some reading I am trying to change bit 10 or timing knockdown on light acceleration.... to 0 instead of 1. This has solved the issue for other people so im hoping it does so for me

ridenrunwv

I would adjust the knock sensor filtering instead so if you ever get bad gas or something and start picking up real knock it will still pull timing for a little extra protection. This and setup your CEL flash on knock will give you some protection and indication of a problem.

bsbllfit7

real knock should still be picked up. However the problem persisted after changing bit 10. Timing does not follow the timing map even after the high octane and low octane maps match each other. Any ideas as to how to get it to match the maps?