DIY_EFI Digest V5 #177

[Diehl, Jeffrey]

Wow!  I thought I was the only one who had heard of a '186!  They were used
in the Tandy 2000 computers in the 80's.  Unlike the rest of the x86 series,
they have their own interrupt controller, btw.  

Yes, 68K assembly code is very easy.  Nice chip.  I'm hoping to stick w/ C
though.  Because that's what I know best.  Well, perl would be nice.... ;^)

Anybody doing EFI work for an import engine?  I'm interested in modding a
Toyota MR-2.

Finally, my car has to pass emissions.  What kind of reaction does a DIY EFI
get from the smog testers?

TIA,
Mike Diehl,
MR-2, '87na

-----Original Message-----
From: Hunt David [mailto:huntd at tce.com]
Sent: May 09, 2000 4:21 PM
To: 'diy_efi at diy-efi.org'
Subject: RE: DIY_EFI Digest V5 #177


Mike, I agree with you.  I was thinking of laying out a '186 board and
setting it up so that I would work with the Borland development system,
especially the remote debugger, to program the card.  Then a laptop with a
serial link would be all that's needed.  

Have you looked at the group that's using a Motorola processor? I think
they're using a cross-assembler and Mot assembly is quite simple.  I'm
getting ready to look at them to find out if connector similarity would be
useful.  Does anyone know where to source the connectors for standard engine
controllers, say a '747 type controller?  It would be nice just to plug into
a GM wiring harness.

I believe that the timing is handled by measuring the time after a an event.
Lets say you want to fire a plug at 20 degrees before a cylinder.  You start
a timer from the centerline of the last cylinder and time.  You know the
timer value because you know the time between pulses.  Anyone correct me if
I'm wrong.

Reply to 

Mailto:dh at bamainc

dh


Date: Mon, 8 May 2000 10:51:04 -0600
From: "Diehl, Jeffrey" <jdiehl at sandia.gov>
Subject: RE: Old 486 Board for ECU? Why?

So how are you getting these free samples?

I tend to agree with this architecture, but this is a religious argument.
Instead of arguing about architecture, it's more useful to us newbies if we
constrain our discussion to the "how" and "why" of EFI.  I'm here to learn.
On of the things I'm interested in is knowing about any novel applications
for an DIY EFI.  The limited slip feature sounded so cool, for example!

My rationale for wanting to use the PC architecture is that by simply
re-writing a few lines of code, which I can do in my sleep, I can completely
change the way my car would respond.  Maybe I improve it.  Maybe it won't
start.  Either way, I learn.  Now if I had to program a microcontroller in a
foreign assembler language, I might not be so eager to reprogram and
experiment.  Just my $.02

So, what are people doing for crank angel sensors?  I've thought about
counting teeth on my flywheel.  The problem is that I only have 106 teeth.
If I used to detectors, I could come up with 318 "events."  This gets me a
1.1 deg. resolution, and it might float a bit inside this range.  Any better
ideas would be most welcome.

Thanx,
Mike Diehl,
MR-2, '87na
----------------------------------------------------------------------------
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

----------------------------------------------------------------------------
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