AUTO VE killed my NBO2 Help? lots of ?

[warscout2]

:help2: Alright so i was working on my auto ve tune tonight it seemed to be going well i seemed to have a lot of cells filled in and i was done for the night,
This is when the trouble started. After i saved my log i shut down my car and fashed in my old calibrations that worked well before i started the auto ve tunning. After i flashed it in i started the car and the wideband gauge was all over the place and mostly around 10-11 afr :Eyecrazy: . Then i remebered i forgot to plug in my maf so i shut the car off plugged in the maf and tryed agian. so i try to trouble shoot it by reflashing the calabration and looking at the maf. Then as i was loging it went to ol-fault on the fuel status and the afr looked my sane so i drove home slowly.

1. did i hurt anything running at a 9.9 afr?
2. what happend to make my car do this (how do i fix)?
3. did i get any usefull log on my auto ve try.
4. was my auto ve tune you problume?

Also i would like every one to take a look at my auto ve log but its 1.3 meg and it says i can not attach it.

I know there is a lot of crap here but i need all you smart peoples help.
You all have already tought me so much and i thank you all. :master:

[purrvert]

Don't know what you are adjusting VE with, you are not logging the Base Efficiency Numerator1 LC-1.

[joecar]

In the scantool you can highlight any part of the log that is garbage and delete it, or you can highlight any part that is good and crop out everything else... (hover your cursor over the last 2 buttons in the toolbar at the bottom of the scantool);

when done, save log as a new filename, and if it's under 1MB you can post it.

[joecar]

I had to manually enable BEN_LC11 from the PIDs tab...

You want to log H02S11 and HO2S21 to see what the NBO's are doing...

[warscout2]

I have the log from when I was doing the auto ve log that has the ben factor I will try and edit it so I can upload it.

[warscout2]

ok so i had to zip the file becouse most of it is usfull so here it is tell me what you all think

[joecar]

ok so i had to zip the file becouse most of it is usfull so here it is tell me what you all thinkIs this the log of when it was all good...?

[warscout2]

This is the log(auto ve log1) from during the auto ve tuning process. right before i flashed my car back to my standard tune(back up 2002 formula with 2000 tables 062007.tun).

[warscout2]

ok so i reflashed my car to the AutoVE tune and it seemed to do good. Now i also loging nbo2 sen's to see if they have goon bad can everyone look at my log and my new AutoVE tune with then BEN from my first autoVE log.

[joecar]

You have closed loop trims disabled, so the NBO2 will not switch...
And the MAF mode is still failed, so the MAF sensor will not do anything...

Your NBO voltages coincide with your WBO voltages, so the NBO's are still working
(...remember that NBO high means rich and WBO low means rich...).

You latest VE table looks good, when you log from this table do your BEN's get very close to 1.0...?

[warscout2]

With the new log i can not seem to get the cells that are lower do i have to be in a higher gear to get the lower cells?

And i also tryed to use the BEN factors on the autove 2nd set and it just lowered the ve tables even more i dont se why it didnt just leave the cells i had already logged alone?

[joecar]

You mean the low MAP columns... these cells should be hit with closed throttle deceleration...
if they aren't hit, there could be an air leak (not enough vacuum).

On each iteration the BEN's should converge on 1.0 (which leaves those cells alone)...
if they don't then something is wrong.

[warscout2]

so i found what was one of my major problems. I had ben logging and my ben MAP was wroung because i had one of the parameters set in metric and the other in imperial. No need to say this really messes with the logs and the data. if your map looks backwards this might be your problem.

[joecar]

Ah, you found it... :cheers: ...that one has bitten many.