MAF BLM based tuning

[Bruce Plecan]

> Trouble is, I don't trust the framing that comes out of the ALDL.  it
almost
> seems as if there is some delay between certain data members.  If my RPM
> delta is 1000 in 3 frames, and some data is 3 frames behind, I am tweaking
> in the complete wrong area!  what I did is tweak DOWN (less advance) in a
> very broad area and I will push them up slowly.

Once you see which way things are going then you can correct for it.  Try it
just using a single display scanner.

> For example, airflow may rise before RPM registers a rise, or knock retard
> may occur a couple clicks BEFORE knock counts.
> Are the items in the datastream prioritized? are some maybe updated every
> other pass? if so that stinks!

Well, all we have to do is the couple hundred of us to tell gm to redo
things to our liking <g>..
Grumpy

>
> ----- Original Message -----
> From: Romans, Mark <romans at starstream.net>
> To: <gmecm at diy-efi.org>
> Sent: Monday, July 17, 2000 9:52 PM
> Subject: Re: MAF BLM based tuning
>
>
> > Dave, when I want to tune I make a run and record it using diacom, and
> then
> > using GMe, print out the spark map.  Then I scroll through the Diacom
run
> > frame by frame, looking at rpm, LV8 and spark retard.  The RPM and LV8
> > should put you at your actual spark as it is on the printed map, then I
>
>
> <snip>
>
> --------------------------------------------------------------------------
--
> To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
> in the body of a message (not the subject) to majordomo at lists.diy-efi.org
>

----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org