Old 486 Board for ECU? Why?

[Diehl, Jeffrey]

Oh, I thought you had come upon technical trouble.  Good to hear that this
approach, so far, is viable.  ;^)  It is a long way to go to get the where
we're going, but I'm a much better programmer, than electronics engineer.  I
can do logic design, but prefer to code.  Besides, this is a learning
project as much as a "performance" project.  I can revise my software to
take advantage of my growing experience.

BTW, I teach Linux.  If you run into linux related trouble, lemme know.

Man, I can't wait to try some of this.  Anyone care to suggest good reading
material?  How about parts catalogs?

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

-----Original Message-----
From: Frederic Breitwieser [mailto:frederic at xephic.dynip.com]
Sent: May 04, 2000 12:05 PM
To: 'diy_efi at diy-efi.org'
Subject: RE: Old 486 Board for ECU? Why?


That's pretty much what I've done.

Read certain memory locations for sensor values 0-255, write values to make
things happen.  The card fires injectors and ignition events on its own,
based on the electromotive crank wheel that spins with the engine, with a
predetermined delay based on what values are pre-set in certain memory
locations.  The PC can write to these memory locations, and the "default"
value upon card boot up is barely enough to idle the engine.  Its a simple
75LS75 (I think) latch, that has a simple set of dipswitches behind it for
idling.  Of course, once the PC is booted, it can override anything. 

>turn off most of the services, and modules.  Link it staticly with
>everything you will need.

Yeah, sendmail is not necessary.  Though, I'm running it this point because
I'm learning Linux.  Too much stuff to learn.

>facing.  You mentioned that it will idle, but that's about it.  Are you
>able to make corrections quickly enough?

It idles, and that's it, simply because I'm not done with the project yet.
The card idles the engine based on default values that I set with dip
switches, and I have written 0 lines of code to change anything.  So, all it
can do is idle.  The card by itself, makes no decisions.  It simply says "I
have been told (by a latched default value) to give this much fuel and this
much spark".  And it does.  Blindly.  The PC doesn't update values as of
yet, no code.  I lost the dyno at this specific point in the project.

>If you are trying to use 4 displays in graphics mode with svgalib, you
>try to write a middleware function which will put a dot on your 2x2
>"virtual" display.  Then build from there.  This shouldn't be too bad.  

Just need to circuitry between the PC and the panels :) This is where I am
stuck on that portion of the project.  Lower priority at this point than the
EFI code.

Both lower priority than finding the water pump pulley :)

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