Still trying to learn, Auto VE

[bmax]

Hey Guys,

After much reading and trying to get used to using this program, I think I have finally logged some usable information.

I am trying to learn the auto VE before I do heads/cam in a few months.

The thing is, I have followed the tutorial and have done the cut/paste into the VE tables and my new data is very different from stock.

Is this normal?

I attached a couple screenshots.

Thanks for your time.

Brad

[hquick]

It always helps if you post up a tune and log.
Makes it alot easier for someone to see if there is anything in particular which looks out of place.

[WeathermanShawn]

It really depends on your goal.

Staying SD or are you going back to using MAF? Closed loop, open loop?

That is a very unusual VE Table. Some of the VE's look like you would be incredibly lean. It is not always easy to hit enough RPM/MAF cells and in adequate numbers on a run. Constructing an accurate VE Table requires a fairly consistent ECT & IAT temperature. Are you attempting to do it on several days?

If you are still basically stock you might just re-work a stock VE Table. Take out a little fuel out low, and add some up high.

I would post some logs and a tune.

[bmax]

Thanks for the quick replies,

Goals for the car as of now is a daily driver, I will be using the maf and going back to closed loop.

I want to have a fun car to drive and rarely will it be raced at the track.
Its also used for road trips now and then.


Ok, tune is stock for the most part, it was touched
up by a shop after I put on headers and LS6 intake.
(turned off codes, etc.)

The only changes I have made were for SD tuning.

I just got the V2 and I have had a lot of trouble
understanding the PIDs and MAPs.

Most of the info I was reading is a little
outdated.

Anyway this is the first time I was able to make the
data somewhat functional.

I just thought the data looked wrong and have not had
the time to get into it further.

This is a fairly short log but at least I can finally
make some sense of how to set up the PIDs and MAPs.
That has been by far the hardest thing to learn with this
so far.

Now that I can see what I need to I will make some better logs.:)

Thanks again,

Brad

[WeathermanShawn]

The PID I do not see is the External Wideband BEN. I see you are logging AFR in two units (AFR & Lamba).

What I do not see is the AFR reciprocal or BEN. That number will the difference between what AFR you are commanding and your actual AFR. And everything must be in the same units when logging (I.E. just choose AFR). Without the BEN you can't paste and multiply back to your VE Table.

Even though in Open Loop your O2 sensor(s) trim is not active, your Logged O2 sensors are pretty flat. Mine do the sine wave function, and yours stay rich all the time. If you see that pattern if you go back to closed-loop, you might want to replace them.

[bmax]

Thanks Shawn,

When I log then open the file the Ben pid has to be selected after I open the file. Don't know why. After that it shows in the map.

I am logging with an LC1 hooked up with the serial cable.

Brad

edit : I am trying another log to check out and the results are looking better, maybe I had some bad data somewhere. Or maybe I'm finally understanding a little more.

Thanks again

[bmax]

Thanks again for your input guys.

I recalculated my wideband and made a couple more logs and they are only 1+% different from my stock VE on a few cells.

So something wasn't right but I'm on the right track now.

Now I need to learn how to interpret the o2 info that Shawn talked about. :cheers::cheers:

Brad

[WeathermanShawn]

If you go back to closed-loop at some point just log the two front 02's and make sure the voltage oscillates from ~.100-.900. Should look like a perfect sine wave. You'll need those working to get your Trims in line.