Well Kyle
I'll say I gotta agree with Greg on the meters t curve being important
I looked at your sig closely and did not see an after market meter
so you should be fairly close with the OEM curve with just a tiny
tweec here and there to compensate for your particular combo
Ensure you return to stock fuel pressure and fine tune your inj
values by using your K values. EA will explain all the details
After all the above has been done ...
Your CL tune should be fairly close
You talk of
1) surge/buck at idle & cruise
2) cold starts changing over a period of time after pcm reset
For 1 ... you may find it goes away after your efforts to make your
CL tune as it should be.
If not ... surge & buck can be caused by over rich mixtures or spark
values being too high for light load conditions
FUEL
The over rich mixture is most not likely gonna be a prob if you tune
as indicated above because your K values are gonna be used to
make things as they should be ... thus ... if you started with things
being too fat ... you will have taken the steps to fix it
SPARK
Look at your data logs to determine where or when your surge/buck
occurs. Then match it up to the load on your spark table and dial
the values back a bit. This is one of those things you just have to
play around with to see what your combo likes or does not like
As for 2 ... this is an indication of the adaptive at work over a
period of time. Since you got a surge ... you are most likely
lean and the adaptive has made things fatter to the point
the cold start up has gotten to be too rich
As said above ... your first efforts will most likely .........
make this issue go away
Greg gave you the basics on spark settings
I usually kill my altitude table as well
but
I've tuned with both methods and have found both work well
however
I'm a bit lazy and just don't wanna keep up with two tables
Paul gave you the info on egr
As for your scalar ... spark_min_for_tip-in_retard
You can make it null and void if you match the value in that scalar
with the max value of spark you have chosen to use in the highest
load row of the base spark table
In a nutshell my Stangnet Friend
Do the basics of tuning first (Closed Loop) and a good bit of those
irritating
issues will become a thing of the past
Grady