Running 93 octane and see how my car only runs 1* even though I have 2* set for peak boost

 

from what i can tell in your logs, you are running the 1 and not 2 at peak torque because the car is showing 1 knock count starting just before you hit peak torque, so it is pulling a degree of timing.

on my car, i found that the "conservative map" that came on the car was running so rich with so little timing it was causing knock, as i increased peak timing to 4-5 degrees i erased the knock completely.

also, are you doing say 3 pulls back to back? typically if you get 1 count like that it will go away in a second/third pull.

are you running a bigger fmic or stock?

 

Stock fmic, that knock is sporadic but even when no Knock it only hits 1* also I do back to back.

 

use evo scan to do a map trace and hover over the cell you have marked as peak torque, it will tell you the interpolated value and what cells it used.

 

You should be able to run more timing at 5k rpm vs 3.5k rpm whether 5k is where you hit peak torque or not. So, your logic seems solid to me.

 

Also there is an air temp timing trim map that pulls timing depending on what the scaled IAT is at as well...

 

I ran map trace and I think I see the problem. Thanks for the advice but now I could use some more =D My csv files or logs show that I hit 260 load as peak then trail to 240 for 4500-6000rpms then down to 220 load. The map trace shows a different load range. It shows I spike to 280, then fall to 260 for the majority of the range then 240 load after 6000rpms. Why is my csv file load different than my map trace load? According to map trace I've been tuning the wrong load cells hence the inability to have timing be what I set it to.

 

Ah, you've spotted it too. Evoscan's map tracer uses an incorrect system of choosing cells...!

See my own "WTF" thread here. Post 9 on is the good oil on bad map tracing.


I've heard people mentioning importing their logs into Innovate's Logworks... and that Logworks' map tracer does its cell selection better. Not tried it myself, though.


Rich

 

So map trace is wrong and I am actually hitting the load cells in my csv files. It's the heat that may be pulling timing?

 

I'm using the johnbradley mivec map as well. Could too much mivec advance cause knock? I'm thinking of trying the JDM rs mivec map above 240load

 

Hi guys, I´ve been using this virtual dyno program for map tracing:

http://www.dynovision.webspace.virginmedia.com/

It takes a bit to get used to it but has some nice features, specially the map tracing of one or two pulls, makes it very good for comaparing changes.

Cheers,

Ricardo

 

I can't remember, are you stock cams or no? I would say try the JDM map, maybe JB's map is too aggressive for your car.

 

Stock cams

 

I'm frustrated with my part throttle tuning! It seems no matter what I do, I can't get rid of knock at 2500-3500 rpm. This is a good thread, but I didn't find if it's confirmed that this is false knock.
Here is my timing map. I haven't smoothed it yet, but any help would be greatly appreciated!

 

Tom from VRSF and I pretty much decided that it was false knock while we were tuning my car, so we adjusted the knock filters to get rid of it. I still run fairly low timing in that area, and the transition is very smooth. There's a pic of my map in this thread maybe a couple of pages back.

EDIT: found it