EcuPrime Studio: ECU file inspection tools in the browser

EcuPrime Studio is a file inspection screen that runs in the browser: it opens your ECU file, shows the bytes, compares them with the original and tracks what you change. This article describes the tools that are in the screen today. Nothing unwritten or unmeasured is described.

Where it opens

Studio opens after you sign in; there is no access without a session. An administrator can switch the screen off, and while it is off it is not served to customers. The general presentation of the software, with screenshots, lives on a separate page: the chiptuning software page.

Command palette

Ctrl+K opens the command palette. The palette searches the tools of the screen by name. Command names are kept in four languages and the search works both in your own language and with the Turkish name, so typing the name of the job is usually shorter than walking through menus.

Byte-level editing

Source switch: the same screen moves between the modified file, the original, and the difference between the two.

Undo and redo: only the previous and next state of the changed range is stored, the whole file is not copied. Undo stays fluid on large files as well.

Difference navigation: N and V jump to the next and previous change. Navigation continues from where you clicked instead of returning to the top of the list. The first and last difference are one key away.

View: the number of columns per row can be raised and lowered; crosshair, physical view and point view are separate tools.

Search and interpretation

Search works with a wildcard mask and on numeric types: one byte, two bytes, four-byte integer and four-byte floating point, with little and big byte order as separate options. An inspector panel shows the selected bytes read as different types, so you see the same four bytes side by side as unsigned integer, signed integer and float.

Segment compare

You can compare a selected region against another file, or return only that region to its original state. The compare window also hosts loading a version and transferring changes, on the same screen.

ECU identity and ready solutions

The ECU identity resolver inside Studio is the same engine the coding screen uses. The two screens do not report a different identity for the same file. The ready-solutions list is read from the pool; no invented row is added to fill a shelf. The whole catalogue is on the ECU list page.

Checksum tab

Checksum runs as a separate tab from inside Studio and is never chained into delivery on its own: you start the correction. The flow has its own article.

Export

Studio exports the modified file and puts a patch report of your changes next to it, as JSON. The report records what changed at which offset, so the same change can be read back later.

Language

The screen runs in four languages: Turkish, English, German and French. The palette title, the palette commands and the map finder labels are translated as well.

We state the limit plainly

Studio is an inspection and editing screen; it does not tell you that the bytes you wrote are correct. Every change is your decision, checksum correction is a separate step, and a file opening in the tool does not mean it will run in the unit. If you prefer the automatic flow, see the chiptuning file service page.