Mitsu.kid.02

iTrader: (3)

Oh ok haha i need to add alot more fuel then, im at 12.3 AFR but im not getting any knock, only after 4,300k because i never pulled timing up top yet. So ill set it so its about 11.3 to start and ill do the steps you mentioned above

Mitsu.kid.02

iTrader: (3)

I was reading through a post that steven made about the low and high octane timing maps, On the Evo ECU ROM that im using do i use the high octane map for power and edit the low octane map to control knock? Say im getting 4 counts of knock at 3,500 RPM at 120 load. My timing on the high octane map it 7 and on the low octane map its 2. Do i pull timing on the low octane map and change it to 1 degree (pull timing one degree every 3 knock) right?

HornstarBU

iTrader: (7)

The high octane map should be "knock-free" throughout the entire WOT pass, and then the low-octane map should be just a few degrees lower all over the map. When you get knock, I think it merges the 2 values together (more knock, and it goes closer to the low octane number), so that low octane map is used when the engine has "problems". You want it running as smooth and knock free under optimal conditions, and then under less than optimal conditions that low octane map will help correct . Those sorts of conditions are like, bad gas or water in the gas, problems with injectors, hot day, like, everything that could possibly go wrong, those values allow for a margin of error.

Do this to sort of learn, compare the value in the high octane map, the low octane map, and the actual timing you had at that specific spot in your log. I'm betting with no knock, you're at the high octane value, with some knock, you're between the 2 values (of hi and low), and then when you knock like 10...probably the low value. Let me know if that is the case, I'm curious.

Mitsu.kid.02

iTrader: (3)

Ok cool, thanks for that clarification. So basically, to my understanding now, the car should run on only the high octane map, then when it gets a knock, for an example, it starts to calculate how many degrees it should pull back based on the value of the low octane map right? So when it see's knock it takes the high octane map value, and the low octane map value and pulls timing based on the values between both the maps, not just the low octane, thats why its important to make both the low & high octane maps smooth to work together? Am i understanding this correctly??



As you can see, in the screen print, starting at 100 load (where boost starts to occur) at 2750 (near where turbo starts spooling) The difference between the high & low octane maps is that there 5 values apart, all the way through. Now say at 3500 i experience 8 counts of knock at 125 load, High octane value is, 7, low octane value is 2, still 5 values apart. Now what i dont fully understand is, do i change the value in the low octane map to say "0" and keep the high octane map to "7" and since the margine between the high and low octane values are now further apart, the calculation value should also drop timing more when knock occurs, know what i mean? Or do i change both the high and low octane values, for example change the high octane value "7" to "6" and change the low octane value "2" to "1"? See what im saying?

Green_Bandit

iTrader: (25)

Ok, so im going through this thread now. Learning what I can and Im coming on my first issues. A few light pulls around town im coming into some knock. At least thats what the ecu is trying to tell me. I dont think it is because of the light load and low rpms.

Somebody mind looking at these and let me know if this is what phantom knock looks like? If its real knock the knock voltage should be near the amount of knock if graphed right?

Also im trying to log my wide band through evoscan but the values look off for the column WBO2. Is there a formula that I have to change to get the values correct or should they already be applied?

Thanks for looking

jakermeister

iTrader: (11)

I'm a noob at reading loggs, but is green bandits car knocking between the switch from open and closed loops???

AnabolicEVO

iTrader: (4)

This is just the info I needed to read. That's OP for this great thread. Respect.

dangtheheo

iTrader: (1)

This was a great read... watching the evolution of the OP I wish there was more - I want to see how far he got.

I'll be starting this adventure soon too.