How ECU Definitions Work

On its own a BIN is unreadable. A definition is the key: it describes where each map and setting lives in that binary and how to interpret the raw numbers. MotoEditor's engine reads definitions in the widely used TunerPro XDF format.

What a definition contains

For every table or scalar, the definition records:

• Address — where in the BIN the data starts
• Size and shape — rows, columns, byte width
• Axes — the RPM/load breakpoints that label each cell
• Scaling — the equation that turns stored bytes into real units (e.g. degrees, ms, AFR)

Some entries aren't tunable numbers at all — version, hardware and serial strings are stored as ASCII text and displayed as characters rather than values.

Why it must match the firmware

Because a definition points at specific addresses, it only makes sense against the firmware it was authored for. Point it at a different firmware version and you'd be reading — or worse, writing — the wrong bytes. That's why definitions are tied to a firmware signature, and why the library is organised by manufacturer, model, year and ECU.

Verified definitions

Every definition in MotoEditor has been checked against real firmware so the maps land where they should. You can browse the whole library for free; an active plan unlocks the editor itself.

A good definition is the difference between confident tuning and guesswork.