I am looking for hints, clues, ideas, for building a good process to use the MAF calibration feature in 2.0...
The stuff I am looking for would be like:
1. DFCO.... disabled during MAF calibration logging (to get rid of false lean readings).
2. ?
3. ?
Any help from our testers would be appreciated
2007 CTS-V LS2
http://www.ls1tech.com/forums/showth...77#post3553077
same as before 2.0...just easier now
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
and as I stated in a post in that thread
you can tune MAF with Wideband error %(my personal Favorite)
With STFT/LTFT (for if you dont have a wideband)
and by PID for Dynamic Airflow in g/sec (metric)(Red Supras worksheet in a PID form)
-Scott -
i wonder how close it comes out with stft/ltft method as compared to the w/b method...have you ever tested it?
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
yes..I use the LTFT/STFT method all teh time when Iam doing e-mail tuning with somebody without a wideband....
works great...
they still have to go get WOT tuned...but it gets everything else correct. they can also disable PE and purposely run it a litle rich and do full on and change PE multiplier to be 1.131 and it gets it pretty close..though I tell them it is at their own risk because of fuel mixtures being only 14.7 at high load high rpm.....I usually suggest they take it on a downhill run to ease the load a little and to watch the Knock and let off immediately if they see any....
you basically go about it with the same caution as you would for tuning boost.
but it works if you are staying in closed loop and keeping the MAF working
It has been more accurate for correcting the MAF when you plan on using the stock o2's
I have tune many MAF's using LTFT
and remeber if you dont recalibrate the switching points of teh o2's then its going to do what is already programed in the VCM so its going to be accurate to the o2's where a wide band is accurate to real A/F
-Scott -
Just for a little fuel on the fire....
How about this...
I create a histogram logging LTFT vs. MAF Hz and then make adjustments to the MAF calibration based on the results (assuming my VE is spot on).
OR should I disable LTFT and use STFT???
(DFCO disabled?)
2007 CTS-V LS2
you should use LTFT + STFT if you are going to do it that way
www.audiohelix.com/file
just a small collection of histograms and PID's
I have made a few more and need to add them...but this list everything works
-Scott -
Originally Posted by soundengineer
How do you feel about this approach? I am seeing that my front O2 sensors do not always agree with my WB....
2007 CTS-V LS2
It works well...but always better with a wideband...
I prefer to use AFR error% and tune with a wideband..then try o compensate the o2 switch points so that everything lines up with my wideband
but it works well using LTFT+STFT if you dont have a wideband
-Scott -
I have a WB, but after getting the VE spot-on (compete SD tune) and then calibrating the MAF Hz to the WB AFR % error, my logs show LTFTs disagreeing with my supposed perfect ("0"tune. Not by much (4-5ish) and only in very low TP% (18 and less). I know, maybe I am splitting hairs at this point of accuracy.
Give me the short version of changing O2 switching points...
2007 CTS-V LS2
Quick question...
When I import your MAF calibration LTFT+STFT .hst file and then open Histogram 1 in the config window I get an "<unsupported parameter>" for the top Plot Value PID:....
Is there another script I need also???
***UPDATE***
I found it, had to creat a User Defined Custom PID
2007 CTS-V LS2
did you read the print in the description...
Needs Custom PID [SENS.114]+[SENS.116]
meaning you need to create a custom PID and just copy and paste
[SENS.114]+[SENS.116]
into it...
use % in the unit box
I almost always end up having to correct the Low side of the MAF table with this methid too
-Scott -
Reply With Quote