Get in touch

In development · Windows

Edit ECU maps in real units.

A desktop editor for ECU calibration files. Open a .bin dump, define its maps or import them from a TunerPro XDF, and edit them as tables, graphs and 3D surfaces. The file you opened is never written.

Get in touch See what it does
StoiK Editor with a 20 × 16 ignition map open, in degrees of crank angle against engine speed and air mass per stroke. Cells are shaded from blue for low values to red for high ones, and a 5 × 5 block that was just changed is marked.

The original stays untouched

Edits go to a working copy. The file you opened is never written: the first save is always Save As.

Every edit can be undone

Byte edits and changes to map definitions share one undo stack.

The length never changes

Bytes are overwritten, never inserted or deleted, so map and checksum offsets stay where they were.

One .exe, no GPU

The interface is drawn on the CPU, so it doesn't depend on a graphics card.

Features

From raw bytes to maps you can read

One window holds the hex view, your maps, their graphs and the file you're comparing against.

Hex view

Every byte, in any data type

Show the data as signed or unsigned 8, 16 and 32-bit values or as 32-bit floats, little- or big-endian, in hex or decimal. The Values panel reads the byte under the cursor in every type at once.

  • A graph of the whole file, where structured data stands out from the rest
  • Find hex values as the view shows them, with ? for any cell, or text in any letter case
  • Defined maps shaded in the hex view and named beside their bytes
The hex view with the bytes of two ignition maps shaded and their names beside them, and below it a graph of that stretch of the file in which each map is a shaded band of its own.

Maps

Maps in real units, not raw bytes

Select bytes in the hex view and make a map from them, or import a TunerPro XDF with its tables, constants, flags, axes and math. Each map shows its values in its own units, shaded by value.

  • Values, curves and maps, with axes stored in the file, computed or listed
  • Line graphs, and a 3D view of the values, the original or both
  • A fit check lists imported maps that don't fit the file
A 16 × 12 intake cam timing map in degrees of crank angle, against engine speed and air mass per stroke, with its 3D surface below the table.

Editing

Change a whole region in one step

Set, add or change by a percentage across a selection. Smooth it, interpolate across rows and columns, or apply a formula of your own: you see the result before anything changes, and undo it in one step after.

  • Formulas take X for each cell and any named parameters, and are kept for every file
  • Values are rounded and clamped to what the data type holds; cells held at a limit are marked
  • If rounding makes a change more than a quarter bigger or smaller than asked, you're told
  • Axis values can be edited too, with a warning when an axis is shared
The New formula dialog over the ignition map: a formula named Retard at load, X - retard, with retard set to 1.5, and a preview of the 36 selected cells changing from 28.5 … 35.6 to 27.0 … 34.1.

Compare

See exactly what differs

Compare your file with another one: which maps differ and by how much, and which bytes changed outside any map. Two maps of the same size can be compared too, such as bank 1 against bank 2.

  • Maps that differ are listed with their largest change
  • Δ and Δ % show each cell's difference from the original or from the other file
Comparing with a second file: 5 maps differ, each listed with how many cells changed and the largest change in degrees of crank angle, and 3 bytes differ outside any map.

Screenshots

A closer look

The find bar searching the file's text for 43X001, with the 3 matches shaded in the hex view and in the text beside it.
Find text or hex values. Every match is shaded and counted.
A 256-point curve in kg/h against voltage, with its line graph below the table.
A curve in kg/h and its graph against voltage.
The hex view at 32 bytes per row, with each map's bytes shaded and the maps named beside their rows.
32 bytes per row, with every map's bytes shaded and named.

Saving

Saving, carefully

Projects

Ctrl+S saves the working copy and the project together. A project keeps the original, checked by its SHA-256, the working copy, the imported definition with only your changes, and the maps you made. What was open when you closed opens again at start, with its tabs where they were.

Checksums aren't corrected yet

Checksum correction is planned, starting with byte and word sums and CRC32 over set ranges. Until it's in, every save says the checksums weren't corrected, so nobody flashes a file thinking they were. Cryptographic signatures will be reported as "can't be corrected here", never as valid.

Formats

What it works with

Now

  • Raw .bin dumps
  • TunerPro XDF in XML: tables, constants, flags, axes and math
  • Maps you define yourself from a selection

Planned

  • A2L import
  • Checksum correction
  • Copying map changes to another file
  • Copy and paste with Excel
  • Exporting definitions as XDF

Not in version 1

  • Reading or writing the ECU: that stays with your flashing tool
  • WinOLS formats, which aren't public
  • Binary XDF, Intel HEX and S-record
  • Automatic map detection
  • Correcting cryptographic signatures
  • Linux and macOS

Pricing

One plan, by the month

With version 1 comes a free demo: try everything there first, and subscribe when you need to save.

StoiK Editor

€20/ month

Prices exclude VAT, which is added at checkout where it applies.

  • A license for one computer at a time
  • Every update while the subscription runs
  • Cancel any time: the license works until the end of the period you paid for
  • Moving to a new computer: write to us and the license moves with you
Subscribe

Subscriptions open with version 1. Checkout, invoices and VAT are handled by our payment provider, the merchant of record named at checkout. See the terms of use and the refund and cancellation policy.

Demo

Coming with version 1: the full app with one thing held back, saving the working copy. You'll be able to open your files, define and import maps, edit, compare and look at the graphs. If it does what you need, you subscribe and keep working in the same window.

FAQ

Questions

Does it read or write the ECU?

No, it edits files. Reading and writing the ECU stays with your flashing tool.

Which ECUs does it work with?

Any whose maps you know or can import. Nothing is assumed about the ECU: each map's data type and byte order come from its definition.

Are checksums corrected when I save?

Not yet. Until checksum correction is in, every save says the checksums weren't corrected.

Can it open WinOLS or A2L files?

WinOLS formats aren't public, so no. A2L import is planned; TunerPro XDF in XML works now.

What happens to the file I open?

Nothing. Edits go to a working copy. The first save is Save As to a new file, and later saves overwrite that one. A saved file always has the original's length.

What does it run on?

Windows. It's a single .exe that draws its interface on the CPU, so it doesn't depend on a graphics card.

How much does it cost?

€20 a month, plus VAT where it applies, once version 1 is out. Its demo will be free and do everything except save. See Pricing.

Can I get a refund?

You can cancel at any time and keep using the app until the end of the paid period. If it doesn't work on your computer and we can't fix it, ask within 14 days of a payment and that payment is refunded. The refund and cancellation policy has the details.

When can I get it?

It's in development. Get in touch to hear when there's a version to try.

Hear when it's ready

StoiK is in development. Send an email to ask a question or to hear when there's a version to try.

contact@stoikeditor.app