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

As of 2024 we are selling five universal ECUs. See Mission-Statement

2024 universal hardware matrix

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

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 May 2022 we have microRusEFI and Proteus in stock. New fabrication of the assembled Frankenso board is currently not planned.

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.

A: selecting-open-source-ecu-microcontroller

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. See also https://github.com/rusefi/rusefi/wiki/Custom-Firmware

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

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

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?

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.

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

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

A: FAQ Why No Self Assembly

A: So that log file names could be current time stamp. That functionality is the only reason for battery holder, that functionality is broken for a couple of years now.