Speeduino is an open-source engine-management project, available as different hardware boards, processors and firmware versions. Choosing a board means matching its real inputs, outputs, electrical circuits and firmware to the engine; the name Speeduino alone does not establish a common connector pinout. The Speeduino ECU family contains the individual hardware records. See also the official manual and official hardware repository.
Identify the unit first
- Record the manufacturer's name, complete model and printed board revision, processor, connectors, any daughterboards and firmware version. A seller's description alone may not identify an altered or assembled board.
- Obtain the schematic, harness diagram and setup instructions for that exact revision, including any optional internal jumpers or ignition and VR conditioner circuits. Verify whether the pin numbers in documentation describe processor pins, board pads or vehicle harness terminals.
- Check supported processor and firmware build, board layout setting and any special configuration with the supplier. Do not assume a board labelled Speeduino uses the same connector assignments as an official shield.
Examples of hardware families
- Speeduino v0.3: an early widely used Arduino shield with screw-terminal connections. The official v0.3 guide documents configurable options; its Arduino pin table is not a harness connector pinout.
- Speeduino v0.4: another generic shield family. Check the exact revision and its harness diagram and separately connected power supply.
- Dropbear: a complete ECU design, documented in the project hardware repository. Compare the specific V1 and V2 pages and their connector documentation, not just the family name.
- MX-5 NA6 plug-in: a vehicle-specific board; the project guide describes the 1989–95 NA6 application. Confirm engine, factory ECU connector and harness against the vehicle before purchase; plug-in does not imply compatibility with every MX-5.
- Third-party designs include WTMtronics NO2C, UA4C, Ocelot and PnPduino. Confirm the manufacturer's own revision-specific capabilities and firmware support; compatibility with Speeduino does not mean interchangeable wiring.
Engine and electrical requirements
List cylinder count, firing order, port or direct injection, crank and cam trigger patterns, sensor types, injectors, ignition coils and intended auxiliary functions before selecting a board. Check the number and type of independent outputs and the supported injection and ignition modes for the exact combination of processor, firmware and board. The v0.3 guide explicitly excludes direct-injected engines; do not infer direct-injection compatibility for another board without its manufacturer confirming the complete system.
The hardware requirements guide describes how Hall and variable-reluctance trigger signals differ. Some boards require a separate VR conditioner; input wiring, pull-ups, edge selection and signal conditioning depend on the circuit fitted. Confirm the decoder matches the physical trigger wheel and sensor before cranking.
Match the injector's impedance and required current control to the installed drivers. The generic documentation describes high-impedance injector outputs and additional provision for low-impedance injectors; the actual board and driver documentation governs. Logic ignition outputs require compatible igniters or smart coils and must not be connected directly to a high-current passive coil unless the installed hardware is designed for it. Auxiliary outputs likewise require appropriate drivers and relays for their loads. Verify supply fusing, grounds and wiring against the board documentation.
Sensors, communications and support
Confirm MAP range and calibration for the intended pressure, correct coolant and intake-air temperature calibrations and a compatible variable TPS. A wideband oxygen sensor needs its appropriate controller; connect and calibrate the controller output as documented rather than wiring the sensor element to the ECU. The same hardware guide explains sensor and driver requirements.
Arduino Mega, STM32 and Teensy appear in the project's TunerStudio settings guide; firmware support, processor, USB and CAN hardware depend on the actual board. A CAN-capable processor does not establish that the necessary transceiver or firmware functions are installed. Check the supplied harness, enclosure, tuning files, warranty and support availability as part of the choice.
Continue with the Speeduino first-start and installation guide. Technical references: Speeduino manual, engine constants and board layout, and official hardware designs.