Skip to content
@capoworks

Capoworks

Capoworks ECU and related projects

Capoworks

Capoworks ECU is an independent open-source engine-control project focused on new features, experimental control strategies, and application-specific development.

The project provides a place to explore fuel models, ignition scheduling, signal processing, and hardware integration, giving developers and tuners room to investigate ideas and adapt the firmware to specific engines. Experimental options are identified explicitly, with their operating requirements, limitations, and validation status documented.

On-Demand Firmware Builder · Firmware & Source Code · Wiki & Documentation · Recent changes

On-Demand Firmware Builder

Use the Capoworks on-demand firmware builder to create a matching firmware image and TunerStudio INI without a local toolchain. Select a supported board, choose opt-in modules and table dimensions, then sign in or create an account to request the build. Once complete, download the firmware image and generated TunerStudio INI together. Each user can submit six build requests per day. See the On-Demand Firmware Build documentation for details.

Tune Independently. Blend Freely.

Capoworks preserves independent Speed Density and Alpha-N calibrations while you adjust their blend using the RPM/TPS or measured-MAP blend-authority table. The Blended fuel strategy combines the independently calculated air masses and applies common corrections once.

Blend authority has defined endpoints: at the default 0%, Speed Density is selected, and at 100%, Alpha-N is selected. Intermediate values blend the two calculated air masses.

VE Analyze can calibrate the Speed Density or Alpha-N model in a Blended configuration only when authority is uniformly 0% or 100% throughout the qualified tuning session. Follow the VE Analyze guide for sample-qualification requirements. Air-mass model migration guidance is documented in Airmass Models and Migration.

Fuel-control features also include:

  • Separate 16×16 per-cylinder trim maps for Speed Density and Alpha-N.
  • Independent load-coordinate selection for control functions and protections.
  • Qualified VE Analyze sessions to exclude unsuitable operating conditions.

Ignition and Idle Control

Optional, opt-in rolling idle-RPM feedback supports idle-air and idle ignition correction.

Two ignition strategies provide additional timing options:

  • Cycle Profile uses tooth-history information to calculate ignition-event timing.
  • Time Budget plans coil charging and spark against a specific TDC occurrence.

Both ignition strategy selectors default to Legacy; Cycle Profile and Time Budget are opt-in alternatives. Their use depends on supported trigger geometry, cam synchronization, and ignition configuration; full requirements are documented in the wiki.

Event-lifecycle handling and per-output software dwell limits improve control across stops, failed starts, and restarts.

Workshop, Sensors, and Hardware

  • Service / Workshop flood clear: maintains injection cut during cranking and temporary transitions into running RPM, releasing it when the accelerator is released.
  • Hella OPS+T support: combined oil pressure and temperature acquisition, with fault and timeout diagnostics.
  • Board-enforced TunerStudio settings: protects parameters fixed by the hardware configuration.
  • Configuration integrity: ordered flash access and verified backups.
  • DC/ETB actuator handling: inhibits outputs during configuration burns and invalid control conditions.
  • Hardware and logging improvements: Core8 error-LED routing, configurable MC33816 SPI, independent USB mass storage, and corrected MLG data offsets.

Supported Hardware and Processors

Listed configurations require the exact board revision and matching build; supported features and validation vary.

Hardware group Board configurations and sources
Core8 / Core48 Core8 config, Core48 config
Atlas / Polygonus Atlas config, Atlas hardware guide, Polygonus Universal112 base guide. Atlas is a modular processor brain module that pairs with a base board; Polygonus Universal112 is one such base board. Each assembly needs its matching pinout and build.
Proteus Proteus F4/F7/H7 configs, hardware guide
microRusEFI F4/F7 configs, hardware guide
Hellen / AlphaX Selected Hellen and AlphaX configurations, not all generations
Frankenso Legacy Frankenso config
Discovery / Nucleo F407 Discovery, F429 Nucleo, F767 Nucleo, and H743 Nucleo development targets
Processor family Capoworks target class Concrete target examples
STM32F4 Arm Cortex-M4 F407 (Discovery), F429 (Nucleo, Proteus F4)
STM32F7 Arm Cortex-M7 F767 (Nucleo)
STM32H7 Arm Cortex-M7 H743 (Atlas, Nucleo)

These targets follow the firmware processor mapping and do not imply support for every chip, memory size, package, or pinout in a family.

Custom Hardware and Future Ports

Custom carrier boards and OEM harness adapters are welcome development opportunities, together with tailored I/O, driver, and CAN support or additional MCU variants and families. Each needs board integration or HAL/driver porting, followed by appropriate bench and engine validation.

Newer hardware designs outside the listed targets need individual assessment. Discovery and Nucleo development boards need appropriate power protection, signal conditioning, and actuator drivers. To discuss requirements early, open a GitHub issue with the MCU, schematics, I/O counts, connectors, and peripheral requirements.

Compatibility and Validation

The feature set has been validated on a Rotax V990, as reported by the project owner. Hardware support remains specific to the board, wiring, trigger arrangement, and feature configuration.

Experimental ignition strategies retain their experimental status. Firmware updates may require calibration migration: use the matching INI and follow the wiki.

Origins and Acknowledgements

Capoworks derives from FOME, which derives from rusEFI.

We thank both projects’ developers, contributors, and communities for the engineering, knowledge, and tools that made Capoworks possible. Our work includes original changes and adapted upstream contributions, with provenance preserved in Git history.

Hardware and documentation provenance, including the Polygonus Universal112 source, is recorded in the Capoworks wiki at Credits and Sources. Firmware and dependencies retain their respective licenses and notices.

Documentation derives from FOME Wiki under CC BY-SA 4.0.

Capoworks is independent and is not officially endorsed or supported by FOME or rusEFI.

Popular repositories Loading

  1. capoworks-ecu capoworks-ecu Public

    Forked from gdiciocco/fome-fw

    Capoworks ECU

    C 1

  2. capoworks-ecu-docs capoworks-ecu-docs Public

    Forked from FOME-Tech/wiki

    Capoworks ECU documentation, derived from the FOME Wiki (CC BY-SA 4.0)

    Python

  3. .github .github Public

    Capoworks GitHub organization profile

Repositories

Showing 3 of 3 repositories

People

This organization has no public members. You must be a member to see who’s a part of this organization.

Top languages

Loading…

Most used topics

Loading…