This guide provides a preparation and checking sequence for a Speeduino installation. It is not a vehicle-specific wiring diagram or a ready-to-run calibration. Board revisions, sensor circuits, firmware and the engine installation vary; use the documentation supplied for the exact combination. Start with hardware and board selection and the Speeduino manual.
1. Document and inspect
- Identify the exact ECU board and revision, processor, firmware, loom and engine. Gather the board schematic, vehicle wiring information, trigger-wheel details, sensor specifications and injector and coil data. Check compatible channel counts and electrical drivers before connecting a load.
- Inspect the loom, fuses, relays, power feeds and engine and sensor grounds. Check connections with power isolated. Do not infer harness pins from Arduino pin numbers or transfer a pinout from another revision.
- Confirm crank and cam sensor type and the conditioner and pull-up arrangement required by the specific input. VR sensors may require a conditioner; signal direction and trigger edge depend on the circuit. Route trigger wiring to limit electrical noise as described in the hardware requirements.
- Check fuel pressure control and for leaks. Ensure the injector drivers, coil igniters and auxiliary output circuits are appropriate for their loads. A logic-level ignition output cannot directly drive a conventional high-current coil unless the particular board has an appropriate driver.
2. Firmware and tuning project
Save any existing tune and record the firmware before changing it. The official firmware guide describes SpeedyLoader for standard Arduino Mega 2560 or Teensy installations; follow the board supplier's process for other hardware. Use a TunerStudio project with the INI definition matching the installed firmware and select the appropriate board layout and processor where required. Firmware changes can alter configuration or require migration; check the release instructions and verify settings afterwards.
Start with a valid base tune appropriate to the firmware and hardware, then configure it for the actual engine. A base tune is a starting point, not evidence of safe fuelling or ignition. The project provides guidance on engine constants and fuel, ignition and AFR tables.
3. Calibrate and check inputs
- Enter verified engine displacement, cylinder count, injector flow and fuel details as required by the installed firmware. Set injector and ignition modes and firing order only from the engine and ECU documentation.
- Calibrate TPS, MAP, coolant and air-temperature sensors and the wideband controller output using the correct manufacturer data. With a cold engine, compare temperature readings with ambient conditions; confirm throttle and pressure readings respond plausibly. See sensor calibration and the sensor requirements.
- Enter the physical crank/cam trigger pattern, sensor edge and trigger angle, following the trigger setup guide. Verify stable cranking RPM and synchronisation using the diagnostic logging available for the firmware. Use a timing light to verify that commanded and actual ignition timing agree; confirm the relevant procedure for the installed ignition system.
4. Before and during first start
Arrange appropriate ventilation, fire precautions and a safe way to stop the engine. Check for fuel leaks and keep clear of moving parts. For initial cranking checks, prevent unintended fuel and spark using a safe method appropriate to the vehicle, then restore them only after the relevant checks. The project properties guide says its hardware-output test should only be enabled when the ECU is not connected to a vehicle.
With a suitable base calibration and monitoring in place, start the engine and check oil pressure promptly, then inspect fuel leaks, coolant temperature, battery voltage and the wideband reading. Stop and investigate abnormal readings, noise, fuel leaks or lost synchronisation. Do not apply significant load before fuel and ignition have been checked and calibrated for the specific engine and fuel. Record a datalog and save each known configuration. Review cranking settings and warm-up settings once the basic mechanical and sensor checks are satisfactory.
Troubleshooting by symptom
- No connection: confirm ECU power, USB/serial port and drivers, selected processor, firmware and matching INI; consult the firmware setup guide.
- No RPM or sync while cranking: check sensor power, ground, wiring, air gap, conditioner, trigger pattern and edge. Inspect the trigger log and look for signal noise rather than compensating blindly with filters. See trigger setup.
- RPM is present but it will not start: confirm commanded versus measured timing, firing order, fuel supply, injector and ignition wiring, sensor calibrations and suitable starting settings. Check each against the actual hardware before changing the tune.
- Runs poorly or cuts out: review logs for sync loss, power or ground interruptions, implausible sensor readings and fuel-pressure or ignition faults. A wideband reading or automated VE adjustment alone cannot establish correct ignition timing or mechanical health.
Further references: Speeduino tuning guide, acceleration enrichment, and EFI Analytics log analysis guide. Apply model-specific instructions where they differ from general guidance.