C/L WB/WOT OEM ECUs...

nacelp nacelp at bright.net
Sat Apr 8 14:30:13 GMT 2000


All I see there is Accleration Enrichment.  I may be spacing it, but just
done't see it

You are clear (?) that you'll have to have the EGOR output voltages for O2v
swing over, and under the O2 cross over reference settings in the ecm.  By
example.

The WB is Looking for a average of what would be a .8v normal O2 voltage.
The ecm needs to see a signal that swings over about .6, and drops below .3v
as something that it understands,  I don't think it will understand a fixed
.2v other then to set a code. You might want need to introduce a tach
reference pulse into the EGOR before your done with things.  Just so there
is some easy to see O2 variations, (ie easy for the computer to see, and
maintain a sample rate that it likes).

Note 2:
We know the ecm needs to shoot for a 14.7 for the EPA.  So we also know what
14.7 is for EGOR. Then using those numbers we can set the kluge to generate
a over/under O2 signal for the ecm to get that.  Meaning right output based
on EGORs voltage.  This is what you've already mentioned, just a converter
to run a oem ecm, with EGOR.  The big advantage I see here is that for none
cat applications, can trash the 14.7 and go for min fuel consumption.  With
that info., generate a DC based on the under/over voltages the ecm will
like, and then it will do the AFR calc..  That is the trick for EGOR as I
see things,

While some of the above may seem odd, it's stuff that came to light on the
ecm bench.  The ref pulse tach made some early O2 feedback testing even
possible when, I'd been fighting code 13-44-45s.  I've sleep since then so
bear with me about this is how I remember it.

Just ya gotz to start somewhere.
Grumpy

> Oh yah, it's in there. Run CalCom, load the demo file (you have to load
> the demo file, or otherwise, those tables aren't visible), then look at
> the "VE or Fuel" screen/button. You'll see tables/maps for all three.
> >Yes, that can be done code wise, but I was offering an alternative for
those
> >without hac'd ecm applications, and those that don't care to don't wan to
do
> >much prom editing.
> Yeah, when I said flag/column in the tables, I meant in the CAL tables.
> >Course this is all theory till we get things up and running <<<GG>>>....
> >Just need to get a EGOR to use forra while
> Patience, they'll be available soon; then you can play to your heart's
> content. But we have to have some inkling of what is possible, in order
> to prepare the proper App Notes for switch-type O2 simulation. That's
> why I'm bird-dog'ing this topic now. It's hard to figure out for all OEM
> ECUs what's required to "pretend I'm your switch-type O2 sensor". So I'm
> interested in preparing instructions for the most common and most
> promising OEM ECUs; hoping those will be the GM ecms.
> Gar


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




More information about the Diy_efi mailing list