I know, right

I don't think I've ever done the XML until tonight.

I created a new item in Evoscan and called it VE.

Then went into the xml file under evoscan folder - data settings - Mitsubishi MUTII EFI.

I put RequestID2="01" after RequestID="00". Saved it and reopened evoscan.

 

I'm interested in how you turn out with your sd set up keep us posted ..

 

First thing, Load1byte and your map sensor KPA need to be higher up on the list than this for the formula to work. Here is an example of which items need to be higher on the list than others:

LOAD1byte
JDMmapKPA
VE

Secondly, make sure your 'log reference' name matches whatever is in the formula. The 'log reference' name for when I log my JDM MAP Sensor as KPA is 'JDMMAPkpa' so thats what I put between the brackets (these kind of brackets ---> [ ] ). It doesn't matter that the RequestID is 00 because it won't reference that MUT Table address unless there is a 'x' in the formula.


Just copy/paste the above code into your DataSettings folder/Mitsubishi MUTII EFI XML file in evoscan.

-Jamie

 

I learn something new everyday!

The way I had it wasn't working, it just read 0.

I'll give this a shot in a couple of hours. Thanks!!!!

 

Yeah man!!! I got it logging.

Jamie,

Is it only useful logging with the MAF? I tried it while on SD this morning and it has me up to 122% VE. I suppose this has something to do with my VE settings on the ROM.

 

Nice , i have 144 ve in my set up lol

 

Nice! What does this mean?

 

Not sure. U?

 

You generally will only get accurate VE data when you are accelerating, as decel can throw off the accuracy. If you are logging on a SD patch, the VE should match your VE table if your logging parameters are accurate.

-Jamie

 

Gotcha, I thought thats how it would work as far as the new log parameter matching your map ve on a SD rom. I remember a while back in the beginning of the SD 2.0 thread they said there was no way to log ve, but clearly this would be the way. Maybe they were saying that you cant log the physical ve value the ecu is using via MUT.

for me starting over via maf is something I would be reluctant to do, but the more I work on my SD tune, the more I realize why a MAF is actually better suited for fueling an engine.

10isace post a full screen shot of your logged VE! when it gets done lol

 

With a MAF, it's monitoring the actual air intake so it's calculating a pretty darn accurate VE value...with minor inaccuracies from possible turbulence and boost leaks.

Since we lose the ability to monitor the true VE of the engine with SD, we are forced to 'tell' it what the VE is at each RPM/KPA point. This is extremely hard to do without MAF data since you are basically 'hoping' your injector scaling and latencies are 100% accurate to start with. By using your MAF sensor to your advantage, you can build a full VE table in no time. The first step is to do a 100% thorough tune on the MAF before making the switch, especially getting the fuel trims as dialed in as you can.

On our loaded mustang dyno, I can log the entire VE table with the MAF in about 5 minutes now. After loading the data into my 3D SD rom, when I flash over to SD, it's almost a mirror image tune. On the street this will take more time but you can get enough data in one drive once you know what you are doing.

-Jamie

 

I'm just finishing up my 2nd SD tune. I'll put the MAF on Thursday and log VE.

I have a loaded dyno too. It's a mile long hill near my house. Jk. I wish I had a mustang dyno. I think once I get a shop that'll be my first big investment.

 

I'm definitely going to put the maf back on. I was logging stft on the way home and I'm like-20 in some spots and 9-10 I'm others of my cl area

Just a matter of gettingy damn bov to recirc lol and then I still don't fully understand the process from there but I'm sure ill figure it out

Dyno tech are you cranking out 3d ve tunes on customer cars?

 

Sucks, doesn't it. I'm not that far off, but my LTFT's are -4 low and -7 mid.

I scaled my injectors at WOT. Am I suppose to dial in LTFT's with RPM VE? I've already lowered the latencies about 30%.

 

My ltft was .5 and 8 .....low mid but cruising and idling is part of the story.. I did a neutral rev slowly increasing the revs and that's where **** got haywire

Did you set your wot fuel mapping and adjust strictly ve ?