First stab at following a tuning recipe

I finally finished up the installation on Monday.  I have everything cleverly hidden...unless you open up the glove box.  I have the AFX control "box" mounted in there so that i can see it when the glove box is open.  I have enough loose wire in there for it that i can move it up onto the dash right in front of my face if I feel the need...although, to be honest, I dont think I ever will.  I may dive back in this weekend and pull that loose wire back so that it isn't filling the glove box up and it has a cleaner appearance.

I managed to run the ODBII cable for the HPTuners box through the dash of the car, which was a real pain in the ass.  I de-coupled the ODBII port on the car and have the cable zip tied such that it and the connector to the car are mounted flush with the bottom of the dash...no more smacking my legs with it.  Plus, you can unplug it and still have access to the connector if/when the car needs to spend some quality time at the shop.  I haven't done anything about semi-permanent mounting for the box yet.  I am concerned about leaving it plugged into the car 24x7 since I think that the ODBII port may always be powered (flat battery).  I'll have to test that out and rig a switch to power the HPTuners box on and off if my assumption is right.

So Tuesday morning I get all excited and try to follow SD VE and MAF Tuning Instructions rev3.pdf.  I got an Open Loop Speed Density (OLSD) tune set up based on what came stock on the car.  I multiplied my VE (Volumetric efficiency...basically a lookup between RPM and manifold pressure to figure out the rough mass of air going through the engine) tables by about 15%, per the instructions since the Vararam intake should increase airflow.  I threw it on the car, fired it up and it ran!  Granted, I have a "Service Engine Soon" message at all times now, but going back to stock should cure that (once I have proper VE and MAF tables to copy into it).

Over lunch and after work I was all excited, logging data after the car warmed up.  I needed to lower the VE table a lot, which I did.  Went back out Wednesday morning and it was raining HARD...like 40mph max on the highway hard.  According to that log, the VE values that I had almost dialed in were off quite a bit, so I ignored the log (due to the weather) and went out over lunch.

I was driving down Shawnee Mission Parkway trying to get a good fill of data for the VE table and I took the RPM up higher than I had before (ideally, I would like to tune VE to redline before tuning MAF, even though I dont need VE to be right over about 4400rpm since MAF should fully take over by that point).  I was about to turn around and I pushed it a little high..then bam.  Reduced Engine Power mode.  it was running SO rich in that mode that the wideband was pegged at 9AFR (which is the minimum value that it will register).  I pulled it over and shut it down.  The log showed no knock or anything, so I fired it back up and it was good as gold again.

The conclusion that I made from this is that I really needed to start over.  My initial assumption to just bump the whole table 15% was WAY off.  Enough so that at higher cylinder pressures (high load/rpm), I wasn't comfortable getting into non-adjusted parts of the table for fear of breaking something.  I compared the stock VE table with the one that I had been adjusting it the amount of change was a little varied, as it should be, but the average change appeared to be 5%, so I took the stock VE table, multiplied everything by 1.05 and put that into my SD tune.  I am MUCH more comfortable with that.

I threw the new tune on the car and drove it home last night.  The log showed some changes, but it wasn't a huge amount.  Mostly 5% or less for AFR error % (which is what I am using to adjust the VE table).  I reduced the max change in any cell to 10%, which only affected a couple.

I put that on the car this morning and took a log on the way to work.  I hit a few more cells again so those new areas still need a relatively major (comparatively) adjustment, but for the region that I updated last night, the new AFR % error is almost entirely under 2%, which is fantastic.  I am going to flash the PCM again and do a little driving over "lunch" to see how it looks.

One follow up note is that after looking at my min, max, and count values, I feel like I need to do some manual data massaging before blindly throwing a change at the VE table.  There are clearly values that need to be omitted.  The filter in HPTuners does a good job of getting most of it, but some slips through at either the leading or trailing end of transitions.