Unified rusEFI firmware runs on a wide array of boards with stm32f4 and stm32f7 microcontrollers. We also have Kinetis and Cypress prototypes.

As of May 2021 microRusEFI and Proteus are sold as ECU development boards. See Mission-Statement

Board Features Connectors/Misc. Info Released in Maximum recommended engine
Hellen +knock detection
+VR
+Wideband Controller
Not an ECU, but a collection of modules that can be used to design an ECU. 2020 Board-specific
Proteus + rusEFI if you have lots of hardware or cylinders
+ 4 layer PCB, 135mm x 82.5mm
+ 16 low-side outputs, limited to 3 amps each (injectors, relays, check engine light, etc)
+ 12x ignition outputs (or general purpose 5v, 100mA push-pull)
+ Dual electronic throttles
+ 4x High-side 12v drivers, 1 amp each
+ 4 thermistor analog inputs (2.7k pull up resistor)
+ 12 General purpose analog inputs
+ Dual VR sensors (crank position, wheel speed)
+knock detection
+ 6 digital inputs (hall cam/crank position, wheel speed, clutch/brake switch, etc)
TE Ampseal connectors: 2x 35 pin, 1x 23 pin
rusEFI's most fully-featured shield
IP68 waterproof case
2020 12 cylinder, dual electronic throttles
microRusEFI + Available fully assembled!
+ about 10 analog inputs
+ One VR/Hall input channel for crank sensor
+ One Hall input channel for crank sensor
+ 4 injector output channels
+ 4 logic level coil control channels (external igniters could be needed for some coils)
48-pin connector
On-board DBW
USB, CAN
open source hardware
2019 4 cylinder, single electronic throttle
Prometheus + on-board wide band controller.
+ compact 4-layer PCB smaller than 93 x 100 mm
+ on-board power supply
+ knock sensor chip
+ stepper motor IAC controller chip
+ stepper motor IAC controller chip
+ onboard 4-channel "smart" protected ignition drivers
+ bluetooth module
+ supports two packages of on-board stm32 chips
no on-board connector (wired)
SD card, USB/TTL, CAN
2017 4 cylinder. No plans to offer assembled units.
Frankenso retired + Most customizable board
+ larger 154x152mm 4-layer board requires a Medium Box shipping rate
+ on-board power supply
+ 20x4 LCD screen
+ joystick
+ works both with external brain boards and on-board stm32 chip
+ knock sensor chip
+ used Denso OEM cases available
on-board 64 pin connector
SD card, USB/TTL, CAN
open source hardware
2014 Flexible - probably 8 cylinder max recommended
Frankenstein retired + Simplest rusEFI board
+ our smaller two-layer board
+ Small Box shipping rate
+ low price
- external 5v power supply required
- external brain board required
no on-board connector (wired)
SD card, USB/TTL, CAN
open source hardware
2014 Flexible - probably 8 cylinder max recommended. No plans to offer assembled units.

Q: How to select a board?

A: History shows that fully assembled boards are the safest way to start. History shows that 80% of the kits are never assembled. As of March 2020 we have many microRusEFI in stock and very remaining old stock assembled Frankenso. New fabrication of the assembled Frankenso board is currently not planned.

Q: What else matters?

A: Types and total count of crank and camshaft positions sensors is the next important question. microRusEFI unfortunately only supports one VR shaft input maximum with two inputs total.

Frankenso supports up to 2 VR or 2 Hall shaft position sensors. Prometheus supports TBD. Proteus supports TBD.

Q: why stm32?

A: selecting-open-source-ecu-microcontroller

Q: This is all very cool but you guys do not have a Plug&Play for my Trabant. I think I will go and make a new rusEFI board just for my Trabant!

A: At rusEFI we love cool new projects, but we are a really small team and only have so much time to work on rusEFI.
We already have lots of different hardware configurations and we would suggest using one of the existing wire in versions.
Nobody is stopping you from making your own board, but we cannot guarantee any support for that board or assistance with building it.
If you proceed then please consider making a P&P adapter board design based on Hellen, Proteus, or microRusEFI.

Q: What EDA are you guys using for your open source hardware?

A: rusEFI preference at the moment is KiCad 5. A few legacy pieces are still using KiCad 4. While many EDAs have many cool features KiCad gives rusEFI uniformity and consistency.

See also https://github.com/rusefi/rusefi/tree/master/hardware

Q: What pin do I use for tachometer output?

A: There is no single right answer. It really depends on what kind of electrical signal is your tachometer expecting. Is it low-side driven? +5v logic signal driven? +12v logic signal driven?

Q: What are these four status LEDs close to main processor?

A: Many rusEFI boards have four status LEDs. All four LEDs blink on start-up just to confirm life.

Blue Communication LED which is expected to blink at 50% duty cycle during normal board operation. If USB communication cable is connected Blue LED starts to blink faster.

Red CRITICAL (previously known as FATAL) error means you have a CRITICAL error, engine operation is not possible with CRITICAL error.

Green LED on many rusEFI boards is RUNNING. Off if engine is stopped, blinks if engine is cranking, solid if engine is running.

Q: what about many other LEDs which seem to be blinking in sync with injectors or coils?

A: Following Frankenso tradition, Injector LEDs are RED. Ignition LED are blue, power LED are green.

Q: Why mini/micro/type C on MRE?

A: USB choice dictated by price and availability. If it changes MRE page will note.