CPU and hardware advice sought for EFI

[Igor Dorrestijn]

That is an impressive project, but, if you're going the fancy processor way,
why not get yourself a dedicated engine management chip like the Hitachi
SH7055F or the Infineon Tricore automotive version. Those chips have so many
cool special peripherals you can actually run your engine steady state with
0% processor load.
Your 586 might be very busy trying to fake it is a microcontroller. Not to
mention you might be very busy implementing all these IO functions by hand.
Good luck,

Igor


> Hi All,
>
> I've been pondering this for a while and just thought I'd give in and just
do
> it.  I want a fully managed engine from a single embedded device doing
> everything to run a motor.
>
> Target engine(s):
> Honda 700cc V4 water-cooled from a VF700S Sabre (development)
> Volkswagen 2100cc Type-4 opposed 4, air cooled. (final, ~150 hp target)
>
> I have around 5 years experience doing application level C programming in
a
> desktop environment -- mainly developer tool and scripting language
oriented
> with previous experience in electronic repair and design.  This is my
first
> embedded/real-time device.  Sounds a whole lot more fun than silly
developer
> tools I do by day ;)
>
> A few weeks ago I was playing around with a Real Time Operating System
(RTOS)
> called MicroC/OS-II [ http://www.ucos-ii.com ] from the author's book.
Cool
> stuff, nice book, gosh I hate assembly...  A friend recommended I have a
look at
> QNX's Nutrino kernel [ http://www.qnx.com ].  It seems to be gaining
acceptance
> in automotive appliances.
>
> Designing is research.  `Search` being the predominant part of the word.
Here's
> what I found for a controller:
>
> http://www.tern.com/586e_data.htm
> http://www.tern.com/p50.htm
> http://www.tern.com/flashcore.htm
>
> SRAM is low, but execution code can run out of a flash card.  P-Mode?
cs:ds
> gives me a headache.  The p50 looks sweet with all that I/O.  I think my
> requirements would be the following:
>
> Inputs:
> (2) lo-sample-rate ADC, cylinder head temp. 1 each side.
> (1) lo-sample-rate ADC, oil temp.
> (1) lo-sample-rate ADC, oil pressure.
> (2) high-sample-rate ADC, knock sensors, 1 each side.
> (1) lo-sample-rate ADC, throttle position sensor.
> (2) lo-sample-rate ADC, manifold absolute pressure, 1 each side.
> (2) lo-sample-rate ADC, exhaust O2 sensors, 1 each side.
> (??) crankshaft/camshaft rotational position.
>
> Outputs:
> (4) lo-side DIO, ignition coil amps for direct fire.
> (4) lo-side DIO, injector drivers.
> (2) lo-sample-rate DAC, servos or steppers for the cooling air flaps.
>     (It's a VW engine, remember?)
> (1) serial I/O to the dash for gauges.
>
>
> Could people comment on the above and help me fill in the gaps?  I'm
rather
> overwhelmed, but having fun trying to spec a complete system from what
little I
> can work through.  I'm trying to prototype the FFT routines for the knock
> sensors, now.  Thanks.
> --
> David Gravereaux <davygrvy at pobox.com>
> [species: human; planet: earth,milkyway,alpha sector]
> Please be aware of the 7.5 year ping times when placing a call from alpha
centari
>
> ----- End of forwarded message from owner-diy_efi at 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
>
>


----- End of forwarded message from owner-diy_efi at 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