Atmel & List Stirring

Jack E. James indyjj at indy.net
Tue Feb 29 15:45:07 GMT 2000


Hi Bernd,

Thanks for posting your letter.
At the risk of incurring EEC and diy_ list ire, I feel that the
intellectual
questioning you've brought up is very interesting, especially when
commercial design becomes more complex with OBD and obfuscated by
design to thwart modifications.  Perhaps the time is approaching for a
controller box that plugs into the EEC harness and is easily
programmed from open architecture software.  Of course this is a lot
like the
diy-efi project, but from an observers standpoint, I believe it (diy)
required to much upfront programming effort, for first you had to become
a
Linux expert, then a Motorola guru.

I would hope for a DOS or Windows based programing approach, so that
discussion would flow more about engine control algorithms and not
Tarring and
Kernaling.

As the prices drop and more attractive silicon for an engine
controllers becomes available, it would seem that there might be an
advantage to
separating cylinders, like two identical 4 cylinder controller's for
a V8.  Two ignition sensors (like Pertronix modules switching resistor
loads to provide position logic) and parallel mass air flow or 2- MAF
units for less air flow loss.  Or one controller for part throttle
and another for full throttle.  Just curious about multiple processors,
having thought about using some of the faster PIC,s for each
cylinder.
Actually have saved an old John Deere tractor motor and mower to try
this on.
Thanks for listening guys, and hope to hear discussion on merits of low
cost, easily programmed, multiple processor use.

Thanks all (please no flames (thats an engine pun))
Jack



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