Features of the ECU & TCU file editor

MapEngine does not carry ready-made definitions of every map of every controller. It compares your file with reference patterns and shows filtered proposals, each with a confidence, a status and its dimensions.

You set the AI Similarity threshold yourself. A lower threshold shows more proposals but also less precise matches, so you go through the list, mark each proposal for review and check it in the 2D and 3D preview before you edit anything.

See which controller families are on the list →

A simple change is a few clicks: select the cells, use an increment (Lower, Raise, x10) or type a value. Interpolation and effective copying speed up the routine work.

For harder jobs there are advanced editing functions, including work with local minima and maxima, and a universal search by words or digits that helps you move around the file.

The original (ORI) and your modified file (MOD) are drawn on one graph. Range selection and a live inspector show the values and the size of a change, and a self-adjusting Y axis keeps the data readable.

A smooth 3D engine shows ORI and MOD together, with nodes and editing tools. Rotate the surface, adjust its height and use increments and interpolation to judge and change the shape of a map.

The map table shows physical values, axes and highlighted changes. Edit a selection and compare it with the original without leaving the view.

OFFSET Intelligent Matching lines up compatible reads of the same controller with a fixed offset and gives a preview to verify.

ALIGN handles two files of the same controller whose pieces sit in different places. Slide MOD against ORI, see both traces on one Compare 2D graph and send chosen pieces from ORI into MOD.

Build your own map packs and copy profiles of modified values to other files. Check file and format compatibility before you apply a profile.

The dual HEX view puts ORI and MOD bytes side by side, highlights differences and lets you jump between changes. Search and bookmarks take you back to a chosen area.

Extensive keyboard control noticeably speeds up everyday work.

An auxiliary DTC preview decodes the codes in a file for supported patterns: the code, its name and whether it is active in the file. It analyses the file; it is not a diagnosis of a connected vehicle and it does not write DTC changes. Results need verification.

MapEngine is a native .exe that runs on your computer, not in a browser tab. Editing, the 2D, 3D and HEX views, OFFSET and ALIGN run locally on your own files. Only map recognition uses my server: the selected file is used only for that analysis and deleted once it is done.

Requirements: Windows 10 or 11 (64-bit), at least 8 GB RAM and a display of at least 1600 × 900.

MapEngine edits files. It does not read or program a controller in a vehicle and does not replace a tool for reading and writing. Modified files and their checksums must be checked separately. The program is a general file editor and has no dedicated functions to disable or bypass emission-control, safety or anti-theft systems; the Terms prohibit using it for that purpose.