There are a couple things that can come into play with DBW. REMOVE fuel from this table actually helps. Running camtool is THE tool to use to find and fix the off idle flat spot thing. Remember this... the blade inside of the TB is driven by a servo motor and NOT just from the throttle either. It is all run from the ecm. OK so far?
The ECM can make the blade do weird chit. Of idle flats are usually caused by the throttle plate waving itself. It is really weird to watch this! You twist the throttle, the ECM starts to open the blade upon that command, but then AE wants it a certain amount of rich, and will close the blade while you are twisting the grip! Then it will stop and go WHOA and open the blade again. When you watch, you can see where the blade actually flutters open and close.
The cam tool can show this phenom. While running cam tool.... you goose the throttle a little bit and watch the data points. You can use Datamaster for this also.
I don't have any pics, but what you want up is TPS, MAP, and RPM. On a well set throttle, those three will make like Teepees and each will be inside of itself and not touching each other. WIth flutter, its easy to see, because they WILL touch each other or the tops of the Teepees become flat.
I usually remove the AC and LOOK for it, anymore. I use the progressivity tables and AE to fix this. Oh... and maxed out progressivity tables will AGGRAVATE this condition, not help.
This is what Buckeye is talking about...
The IVO found in the analyzer matches the IVO tool about 50% of the time. Depending on the build and the kPa at idle and just off idle.
The blip technique will not assist you in setting the IVC, sorry. Luckily there are only three set points. 3 is the most widely used, 2 is used about 30% of the time. If you have a HOT build then you may get to use 1, doubt it though.
The blip technique is for throttle response, immediate throttle response, without lag or stumble. It's not in the manual. It's not something that a person can put down as an instructive diagram or discussion. One must understand the proper table use which gives you a "feel" for what's going on with the motor.
Bob is spot on... most people "increase" by nature. Such as, if two aspirin are good, three is better. Not true when dealing with Delphi tables. Less can be more.
This must be done after several VTune sessions under 3500 RPM's or it will NOT work.
The tables I use for this while working with the blip and IVC are:
ARF/Lambda
AE
EGR
Timing at idle
Throttle Blade Control
Fine tuning of this I may use, but not always in addition to the above is:
Spark Temperature Correction
Closed Throttle Spark
Idle Spark Control Gain
Idle Spark Control Max
Visual representations include:
Throttle marking @ 10% and 20% with painters tape
Throttle body butterfly opening
The rest is "feel"
Once you have the data and sharp/equal blip points on the graph you must VTune again.
Now, not everyone will go this far and you really don't have to get this deep in tuning your motor but if you have stumble at off idle then you may want to use the same approach.
Bad blip between 10 and 20% quick throttle blip...
Good blip between 10 and 20% quick throttle blip...