Lack of I/O on the Palm makes it pretty much unfeasible for anything but a monitor or
command input device for an engine management system. PICs and 8051's may barely be
able to keep up with the task if you're REAL clever with the code. The 68332 is a
good option (TPU is a BIG help!), HC11's OK also. See
http://www.diy-efi.org for more info, and check out the EFI332 project. I did
schematics for the current EFI332 design, so email off list if you have other
questions.
Bill
Josh Criswold wrote:
>
> Last night I was wondering about the feasibility of
> using a PDA as the "brains" for a vehicle engine
> management system. I don't know much about the
> hardware of the various Palm OS PDAs, but I do know
> C(2+) and Java and that there are compilers (though
> limited) for both of these languages on the Palm OS.
> The question I can't answer is will a compiled C
> program be fast enough with PDA hardware? Also, is
> the I/O fast enough?
>
> The PDA would have to receive signal between 1 and
> 9kHz (representing RPM), determine the frequency, look
> up the frequency on a table correlating the input
> frequency and output frequency, and output a frequency
> up to .6kHz probably 15 time/sec. Simultaneously, it
> would receive a voltage representing throttle
> position, and look up the input frequency and throttle
> position on a table correlating these with a pulse
> width and frequency up to .6kHz.
>
> There would be no need to access the display.
>
> Power is not a problem b/c the PDA would be hardwired.
>
>
> Some signal conditioning would be performed by
> circuits outside the PDA.
>
> So, feasible?
>
> Josh
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
