<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.3013.2600" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV> </DIV>
<DIV><FONT size=2>> <BR>> The idea is to get open BL as close to 128 as
possible. The accepted<BR>> range from GM is 128+/-10, so your
calibration is still too rich, even<BR>> though the O2 is able to correct
it.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2><STRONG><EM>It's better in the areas I've been playing with,
just haven't found the right tables for the area I'm having the problem
with.<BR>> <BR></EM></STRONG>> You realize that as far as the ECM is
concerned, it is hitting<BR>> 14.7:1. Without the feedback from the O2
sensor, it just calculates<BR>> fuel delivery based on the numbers in the
prom.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2><STRONG><EM>That's what I'm figuring. Somewhere theres a table
telling this thing to put in x amount of fuel so it cam be at y AFR. If I can
find out where this setting is I can fudge the figures it thinks it's at so it's
"realworld" AFR is where it's supposed to be.</EM></STRONG></FONT></DIV>
<DIV><STRONG><EM><FONT size=2>So far I've only burned a couple chips checking
this out, I just thought maybe someone knew of a table I was missing. I just
started using the non-closed loop chip to help in my tuning and that's when the
idle became more of a priority. What used to be just a rich condition until
feed-back kicked in is now my full time idle condition since it never leaves
open loop. It's funny, before I was just concentraiting on the non idle areas,
and went to the open loop idea to help narrow that down faster. Now since doing
that I'm more focused on the idle area.<BR></FONT></EM></STRONG></DIV>
<DIV><FONT size=2><STRONG><EM>Kevin R</EM></STRONG></DIV></FONT></BODY></HTML>