I am almost certain the Log reference matches in the formula. I remember doing a copy and paste from the GMmapKPA log profile, but I will double check just to make sure.

 

Allright. Pulled up EVOscan and looked at the format of the formula. I did match the log referance from both load 1 bite and the GM 3 bar MAP. I tried logging VE again and i still get nothing. Starting to look like i may have to do this the hard way and use an exell formula.

 

I'm pretty sure you still have spaces in your log ref

I think he's saying that regardless of matching the log ref can't have spaces in it

 

Make it GM_KPA

 

And if you add the word "load" to the log reference by make it "GM_KPA_LOAD", you can switch the map tracer load axis to read KPA. It makes it easier to kinda transfer over your log results to the VE table.

I have out in a request to banish to allow us to select the 3D VE table in Evoscan MapTracer to speed things up a bit so hopefully he can do that.

I also asked if he can make some of the log filters more user adjustable. He has one that filters out data below 80% throttle but it would be great if we could pick the throttle position and whether its above/below that value. That would help filter out the decel/fuel cut variances.
-Jamie

 

Jamie

Thanks for this tip. This has been so helpful in tuning Map VE for both 2D and 3D SD.

 

I will give both of those suggestions a shot tomorrow and see what I get. Thanks.

 

Alright, car was down for a couple of weeks because it was running extremely lean (so lean that my car wouldn't even idle... at all). Thought it was a MAF issue but turned out to be a ROM issue. Although I still think I am having either a ECU problem or a MAF issue. I will be swapping from the DSM MAF to an EVO8 MAF as soon as the new MAF gets here in the mail to see if it fixes my issue.

Any way... I have a question about logging VE with the formula that was provided (which I did finally get to work). I have been looking at a few of the VE tables I found on the forums... Is it common to be logging 95-99% VE at idle? What other factors could be affecting the VE calculations while logging? I did swap over to a 3D SD ROM for a day just to see what it would take to get the car to idle correctly. Just to get it to idle I had to change all of the VE values in the target map area to 114% just to get it to idle in the 14.7ish range while locked in open loop (I used the OL throttle, OL load and OL min temp to lock in open loop). Now I know I over built the motor for what I wanted but I doubt I did THAT good of a port and polish.

 

Ol is not a good indicator. You need to monitor stft and adjust ve to get stft inline .

 

I locked the ECU in OL to get a good estimate on where to start. I figured it would be a little less time spent that waiting for the STFT to max out at +25% and the car to lean out, then make a change the VE table and start the process over again. Even having the VE table at 114% in the load/low idle area the ECU was still adding 5% +-3% fuel when in OL. Also if it helps I have 660 injectors scaled at 583 for the moment which might change when I get the EVO8 MAF installed.

 

In my experience open loop ve does not equal closed loop correctness. That's all. stft is immediate it shouldn't take a minute to get there and if its off by 25% add 25% ve . Once you see it going way off over compensate big changes make big results.That's my suggestion ideally use dtt formula for ve. Careful to not include tps decreasing data.

 

I am unable to replicate this in EvoScan. I do i arrange my panel #1 to look like yours?

 

I always find the answer after i ask the question......smh.

 

What do you place in the mut req Id table to get the ve calc formula to work?