Planner

ECU Pinout Planner

Describe the build, get the I/O tally, shortlist the ECU, plan the pins. Free, in-browser, nothing stored.

Loading planner…

Component / wire	Needs	ECU pin	Native label	Signal type	Notes & flags

Guided build

Which ECU can actually run your engine?

Answer a few short questions about your engine – or start from one of 59 swap presets – and the planner works out every input and output your build needs, ranks all 49 ECUs by what they can really do, and lays it out pin by pin.

Planning aid only

Verify every pin against the manufacturer’s manual and confirm with your tuner before wiring – a wrong pin can destroy an ECU or a sensor.

Derived I/O counts, capability supersets, reassignability, add-on specs and 5V/ground fan-out budgets are interpretations/estimates; anything shown as “unverified”, “estimate” or a source gap is not confirmed.

steps, in order

ECUs ranked

engine presets

add-on modules

Start from your engine

BMW

Ford

GM

Honda

Mazda

Nissan

Subaru

Toyota

Picking one fills the steps it can state for certain, and tells you plainly what it could not.

Describe the engine

Short steps – cylinders and layout, fuel, ignition, cams, sensors, actuators. One question at a time.

See the I/O it needs

Injector and ignition drivers, triggers, analog inputs, and the 5V and ground load – derived, not guessed.

Get the pin sheet

Every ECU ranked valid, needs-a-module or won't fit, then the connection sheet pin by pin.

The planner runs entirely in your browser. Nothing you type is sent anywhere, and nothing is saved between visits; export or print your sheet before you close the tab. If a pin looks wrong for your ECU, tell us which one; the profiles are transcribed from manufacturer manuals and corrections are welcome.

Always verify against the manufacturer’s manual and your tuner before wiring.

How the planner gets from an engine to a pin sheet, where the pinout data comes from, and the other questions people ask: read the FAQ.

Guides

What the planner is doing, on paper

The same framework the tool runs, written out: define the build, read the spec sheet for types rather than counts, then tally the I/O before you shop.

Guide 01 · Choose & select

All guides