Electrical Interface Overview
The Hardware Circuits pages explain the electrical interface between a Capoworks ECU board and an engine load. They cover the circuit concept, the matching Capoworks software controls, and the checks needed before connecting hardware. They are not universal drop-in schematics: connector pins, protection, driver capability, and firmware support depend on the installed board and revision.
Start with the load and its required current path. Decide whether it needs a high-side, low-side, push-pull, or bridge output, then determine the required flyback or clamp, supply, switching frequency, and protection. Only then choose a board-supported output or input and a Capoworks mode. The firmware pin types distinguish flexible GPIO names from outputs actually routed to a board function, and output modes change logic polarity or open-drain behaviour rather than the power stage itself.
The same separation applies to processors. Capoworks selects an F4, F7, or H7 port through a concrete board build; the MCU family alone does not define connectors or usable peripherals. For every change, confirm the board target, hardware revision, pinout, schematic, and matching firmware definition.
Circuit Pages
- Discrete VR Sensor Inputs
- Highside Driver Circuits
- Lowside Driver Circuits
- High-Low Driver Circuits
- Power Supply and References
- PT2001 Low-Z Driver
- STM32 Compatibility
For a matching installation, use the Atlas or Universal 112 hardware documentation. Pin locations and protection details from one revision must not be transferred to another.