Will work with just about any single board
 computer.Converts any SBC into a rotary engine EFI system.
 Dual I/O connectors. .025 square pins on .1 centers.
 Standard on most SBC's.
 Screw down terminal blocks on .15 centers.
 Size 2.5 inches by 3.8 inches.

 If I buy I will have to buy 3. Anybody want one?
 Price will be $25 less parts.
 Not done yet. I need to add traces.

 Here is my fav SBC. Very powerful indeed. Can be programed in BASIC.
 About $90. Talks to a PC or tablet  trough the USB.

Paul Lamar

Paul:

Let me clarify how you see this system working ... and let's say I want
to use it in conjunction with my HomeBrewedGlassPanel display

My system so far includes a small PC w/FlatPanel display - else an
Android-type computer -  connected to a data-acquisition board similar
to the 20-port unit I purchased from Digikey.  This should take care of
displaying all the analog signals required for flight instrumentation.

What to do about data-acquisition of digital signals ??? I am not sure
(ie GPS/compass/gyro data).  Some of this might be best gathered from
the OS of an Android-type system, but a multiport digital I/O board for
gathering these data might be required.

It makes sense to me that engine control (EFI/ignition) be handled by a
separate ECU, and if I understand you correctly, the associated PC is
really only needed for programming the the controller-board, and
intermittent display. In other words, one could turn off the associated
PC and the aircraft would still fly.

So what my HomeBrewedGlassPanel display might do is run in an infinite
loop which does the following.

1. On startup (optionally) load current engine operating parameters to
ECU.

 . (optionally) load/verify display parameters for correct display (ie
FieldElevation, BarametricPressure, etc)

2. Initialize Display

3. Start an infinite loop to:
 . Poll analog ports. If any data has changed, update appropriate
   displayed image.

 . Poll digital port(s).  If digital data has changed, update
   appropriate displayed image

 .Poll ECU. ... and do something  ???

4. Check for pilot input ... configuration changes /shutdown...

End-Of-Loop

Any thoughs ????

I see the need for my GlassPanelDisplay CPU to read 3 different USB
ports.    And I am having trouble reliably reading just one USB port :(

RB


Lets call your computer an EICAS.
Engine indications and crew alerting system.
IMHO that is what you are building.

"Poll ECU. ... and do something"

The only useful things the ECU knows is manifold pressure, RPM,
pulse width and intake air temperature.

To put a manifold pressure sensor on your EICAS cost $10.
Intake Air temp several dollars.
Pulse width one or two dollars per injector using an opto iso.
RPM it depends. If you buy one of Henry's Hong Kong stand alone
tachs $10.

To ask the ECU to send that data out the ECU will need some sort of
software which impacts the amount of time available to do it's
engine control job. Basically the same as car OBD II. It also
complicates the ECU software making it harder to write and
bug fix.

Each different ECU SBC will have to be programed
to support your needs with some sort of standard time period,
connector and protocol. Like the OBD II standard.

IMHO it is best to make the EICAS stand alone and add
the necessary sensors. Another point is; if the ECU fails
to actually get all the injectors to squirt or fire the plugs
at the correct time for what ever reason, hardware failure or software
bug, your system will know it. In other words a complete stand alone
data acq system. Hardware cost 1/100th of what software cost for
low volume devices like this.

Paul Lamar

YOU talked me into it.

RB

I found a dual driver for the injector FET's in an 8 pin dip  which will give
me more room on the Gen purpose EFI I/O pc board for a 5 volt power supply.
One 8 pin dip for two injectors. Buck 30 each.

Here it is.