Skip to content

Packaging

Making a change in one ROM is easy. Making the same change in ten ROMs is not. Packaging collects your edits into one file that can be applied to other ROM versions.

Two formats, two purposes

Format Contains Use when
.mtrpack Map names, addresses, scaling and new values Carrying work to other ROM versions
.mtrpatch Map cell patches and optional raw byte patches Repeating the exact same edit

Map packs (.mtrpack)

Export

  1. Go to Project ▸ Export Map Pack.
  2. Select the maps to include.
  3. Save as .mtrpack or as CSV.

Import and apply

  1. Project ▸ Import Map Pack and pick the file.
  2. Review the maps in the list.
  3. Press Apply selected to ROM.

Matching happens in three steps: explicit address, name, then the address stored in the pack. Dimension mismatches and byte-order differences are reported as warnings; you can still apply.

ROM patches (.mtrpatch)

Patches are editable JSON documents. Besides map cell patches they may contain raw byte patches outside map regions.

Careful: raw byte changes (for example ECU-specific checksum/CRC areas) are only correct for the same software version and the same base ROM. Applying them to a different base produces wrong checksums. In that case choose "apply maps only".

Applying

  1. Open the patch with Project ▸ Patch Editor.
  2. Match maps by name and address; a CRC mismatch is a warning, not an error.
  3. Large patches ask you to type APPLY.
  4. A "Before patch: …" version snapshot is offered.
  5. The Patch Results dialog summarises how many maps applied cleanly, with warnings, and which failed.

Map lists (CSV / JSON)

Two different CSV features — do not confuse them:

  • Map list — map names and addresses, also exportable as JSON, useful for lists produced by external tools.
  • CSV data list — plain text export and import of the cells of one map.

Tuning report (HTML)

Project ▸ Tuning Report writes your changes into a readable HTML document: old and new values, map addresses, notes. Practical for a customer handover or your own records.

Other exports

Purpose File
WinOLS project .ols
TunerPro definition .xdf
Map list .csv, .json
Report .html
Theme sharing .mtrtheme

Packaging discipline

  1. Build a pack for one topic ("Stage 1 — low RPM fuel maps").
  2. Write down why each pack exists.
  3. Test on a flashed ROM first, then on the real vehicle.
  4. Keep packs in version control; one day you will need to know which pack you applied and when.