BEFORE YOU UPLOAD

Prepare your ORI file
for a WinOLS MapPack.

Choose the correct ECU or TCU read, check its format and provide the identification details for your request.

Original ORI uploadsBy ECTMAPPACKPublished Updated

Start with the read you will use.

A useful MapPack starts with the correct file. Upload the ECU or TCU file for which you need map definitions. If you have several reads from the same vehicle, select the one you intend to use in WinOLS.

Upload an original, unmodified ORI file. Keep its reading-tool details so you can identify it later. If you only have a modified file or cannot confirm which read is original, contact support before creating the request.

Different read types can contain different data, even for the same ECU. A flash read, calibration read, virtual read or backup may have a different size or layout. Include the read type if your tool identifies it.

Preserve the exact uploaded file.

Keep an unchanged local copy before uploading the file or importing definitions. Keep its identification details and request information alongside it.

Do not trim, pad, merge or otherwise alter the selected file merely to make its size resemble another read. A matching vehicle name or ECU family alone does not establish compatibility.

A new name does not convert a file.

Renaming a container or unsupported format to .bin does not turn it into a binary ECU read. If you are unsure what your tool exported, check its description or contact support before submitting.

Use the original binary read.

Upload an uncompressed original ORI file, up to 64 MB. Use a file type accepted by the current upload form. Common binary-read names include .bin, .ori, .org and .original; the contents must still be the original read.

ZIP and RAR archives are not accepted. Extract an archive locally and identify the correct original binary before uploading.

An accepted extension does not guarantee a supported layout or an available MapPack. A filename alone also does not prove that a file is unmodified. Check what your reading tool exported, and contact support if you are unsure.

Provide the details that belong to this file.

The request form requires a file and all six information fields:

FieldWhat to provide
BrandThe vehicle manufacturer.
ModelThe vehicle model.
PlatformThe platform or generation information you can verify.
ECU / TCUThe control unit identification.
Software numberThe software identifier associated with this file.
NotesRelevant context, including the reading tool, read method and how you identified the original read.

Use information from the vehicle, reading tool or existing project. Do not copy identifiers from a similar vehicle or guess a software number. If required information is unavailable, contact support before submitting.

The optional Detect ECU / software button reads identifiers from the selected file and offers editable suggestions. Review them before use. Detection alone does not create a request or charge a credit.

Check the ORI, then review the completed map list.

  1. Check the selected original.

    Confirm the filename, format and size. Keep the unchanged file for the WinOLS project.

  2. Review all identification fields.

    Confirm that the ECU, software and notes describe the selected read, then create your MapPack request. An eligible credit balance is required to submit a request.

  3. Follow the request in your workspace.

    The portal checks completed MapPacks. An exact-file result may be available immediately; other files need processing or review. Coverage varies by ECU, software and read layout.

  4. Open Free Preview before unlocking.

    When ready, select Preview map list. Browse names, categories and dimensions for free before deciding to unlock the download. Previewing does not use a credit.

Keep your unchanged uploaded ORI until you have imported and checked the result. It remains the reference for the MapPack.

Use the JSON with the matching project.

After checking Free Preview, download the completed result. One credit is charged on the first download; repeat downloads for the same request use the existing entitlement. Extract the ZIP and use the MapPack JSON with the WinOLS project based on your exact uploaded ORI.

Do not assume another software version or read layout will fit. The documented WinOLS examples show what organised definitions can look like; they are examples, not a guarantee for another file.

Review the imported definitions and any available axes, units and scaling before calibration work. Follow the WinOLS 5 JSON import guide for the import steps, or read what a WinOLS MapPack contains.

A few checks before you start.

Can I upload a modified file?

Please upload the original, unmodified ORI file. If you only have a modified file or cannot identify the original, contact support before submitting a request.

Can I upload ZIP or RAR archives?

No. Upload the correct uncompressed original ORI file in an accepted format, within the 64 MB limit.

Does changing the extension make a file compatible?

No. The contents and layout determine compatibility; changing the name does not convert the file.

Can I use the JSON with another read from the same ECU?

Do not assume it will fit. Use the exact uploaded file as the basis of the WinOLS project and check the imported definitions.

Upload requirements checked against the portal on 9 November 2026. ECTMAPPACK is an independent service; WinOLS is a trademark of its owner.

YOUR FILE, READY TO UPLOAD

Prepare your MapPack request.

Have your file and its identification details ready before you begin.

Upload your original ORI