According to your last statement.... Something higher then what you are running, haha.

I cant seem to find my roms. What do you mean pulling out your car? Why are you in open loop to begin with at that low load?

 

I guess I need to raise my load for closed loop at low RPM even higher. That or throttle position. I'm going open loop when I ease off the clutch to pull out at low RPM. My scaling is messed up still. Cruise is perfect but idle was - 12.5. I was looking at O2 feedback and not low trim when I said idle was within +-2.5.

 

Hm weird...

I would say revert all values and following the following link"
https://www.evolutionm.net/forums/ec...ched-roms.html

 

I don't have a good, working tune to convert from MAF to Speed Density. That would have made this process easier.

I had a tune that was running great but really rich at idle and cruise . A shop made it for me remotely. They forced open loop and did not mess with the injector scaling so I was really wanting to get the injectors scaled properly and let the car run in closed loop.

 

Ahhhh, poop.

I wonder if you were able to take their open loop tune, place it back in, scale the injectors to 800, then scale up the whole VE table to come in align with the wideband. May work. Just thinking of ideas.

 

I'm wondering how accurate it all is now. They got my WOT dialed in very quickly but that seems to be the easy part. I also noticed when first seeing what load I was hitting that the load didn't seem to match up. In my tune they set the 2 byte to 1 byte correction value to 2 and I had the default 1.2 in EvoScan. Tuner said he just goes off airflow and MAP and never messes with it like that anyways.

I've been trying to get the tune dialed in myself since the new cams because I just don't want a tune that I have no idea how to modify because of so many random things that I am confused about.

 

This is why when I tune, I start off a base map. Never work off of someone else's tune. My opinion.

 

I finally did this and got everything dialed in nicely in much less time than I spent messing with what I had before. Does it seem reasonable that S3 cams would have a VE in the 50s at idle? That's the biggest thing that really has me question what I did but it seems to work out great that way.

 

Yeah, I think when I had my S2s it was around 45-50 at idle.

 

Thanks again for your help. I ended up taking commonly posted scaling and latency values and dialing in my VE table using them. I didn't see any other way without having a known good VE table.

 

Doesnt someone have a VE excel sheet table for doing WOT pulls? Or is this my dsm I am thinking about. I totally forget. Made my life a million times easier.

Do run, plug in datalog, it will spit out a new VE table, copy paste, done deal.

 

Sounds pretty cool. I didn't have much trouble with the WOT part but just trying to hit every load and RPM for cruising. I forced open loop and that helped me dial it in better. Still not totally happy with it but I'll fine tune it later on.