🎁 New account: buy your first 10 credits, get 10 more free.Avg. 25–45 min turnaround · Files written on your original readCreate free account

Before a single map is changed, every WinOLS job starts the same way: the original read from the car is imported into a new project. Get this step right and everything that follows (map search, versions, comparisons, checksums) works as intended. Get it wrong, for example by importing an already modified file as the “original”, and you can end up with wrong comparisons or a checksum module that does not recognise the data. This guide shows how to import an original ECU read and create a project in WinOLS, step by step, using the menus described in EVC’s own manual.

Facts checked on 27 October 2026 in EVC’s public WinOLS manual (version 5.94, dated 10 September 2026) and on the WinOLS product and download pages, linked in the sources at the end. The current WinOLS 5 release listed that day was 5.95. Menu names can change between versions, so check the built-in help of your version too.

Diagram of the WinOLS workflow from an unmodified original read file through Project New and Import file to a project with the Original, vehicle data, automatic map search and colour-marked versions, plus drag and drop rules
From an original read to a WinOLS project (simplified educational diagram, original illustration)

What you need before you start

Step 1: check which file format you have

WinOLS cannot edit external file formats directly. The manual explains that because WinOLS stores a lot of additional information, a file must first be imported into a WinOLS project and later exported (or written) again (source). The import dialog starts with the file format:

If your tool saved an encrypted file (for example a Slave-tool file), it has to go to the person or service that can decrypt it. WinOLS is not a way around a tool’s licensing.

Step 2: create an empty project

Choose Project > New (keyboard: Ctrl+N). According to the manual, this creates an empty project into which data from a file, an EPROM or an ECU can then be read (source). The empty project window lists files from a folder you can choose with the […] button, and WinOLS hides files that are probably not useful, such as images. If you want to open a project you already have, use Open instead of New.

Step 3: import the original read

The manual gives two ways to bring the file in (source):

  1. Drag and drop the file into the empty project window, or
  2. Use Project > Ex- & Import > Import file (Ctrl+I), choose the file format, click OK and select the file.

Watch where you drop a file. The manual explains that a file dropped over an existing project window is imported as a version of that project, while a file dropped on the WinOLS frame window or an empty workspace background becomes a new project (source). Dropping a customer’s stock read onto the wrong open project is a classic way to mix up two cars.

Step 4: understand “Original” and enter the vehicle data

The first data imported into a project is automatically saved as the Original; anything imported after that is a Version. EVC warns that some checksums require the Original to contain the unmodified data from the ECU, and that otherwise a checksum may not be recognised or calculated correctly (source). So:

Diagram of a WinOLS project file containing project properties, the Original, numbered versions with comments, optional version folders and multiple memory elements
Original, versions and elements in a WinOLS project (simplified educational diagram, original illustration)

Step 5: check the project properties

Open the project properties and check the fields that affect your work (source):

Then save the project with Project > Save (Ctrl+S).

Step 6: let the map search run, then create your first version

After a new project is created, WinOLS starts searching for maps automatically after a few seconds; you can see the progress in the status bar, and found maps appear in a “potential maps” folder (source). Our WinOLS calibration editor explainer covers how maps, axes and factors are read once they are found.

Work in versions, never on the Original. EVC describes storing modifications as commented versions, with the original stored permanently, changes shown in colour, multi-level undo and the option to restore original values at any time (source). Give each version a clear name and comment (for example “Stage 1 draft” or “after log review”), and use version folders if you want to keep the list organised; the manual notes that folders only affect the display (source).

Checksums and export: the last steps

Common mistakes

Prefer to send the file instead?

If you would rather not build the project yourself, upload your original read to ECU File Market with the vehicle, engine, ECU hardware and software numbers, the tool and the read method, the stage you want and any hardware already changed. Credits per ECU tier are listed on our pricing page, and most files are returned in under one hour during support hours. Checksum correction, where needed, is a paid extra.

Good practice: only work on vehicles you own or are authorised to work on, keep the original file for the life of the car, and keep all emission control systems fitted and working. This guide does not cover removing or disabling DPF, EGR, SCR/AdBlue or any other emission equipment.

Sources (checked 27 October 2026)

WinOLS is a registered trademark of EVC electronic. Other product and company names are trademarks of their respective owners. ECU File Market is an independent tuning file service and is not affiliated with, endorsed by or sponsored by EVC electronic. Names are used only to describe compatibility and workflow. Use only genuine, licensed tools and software.

Leave a Reply

Your email address will not be published. Required fields are marked *

⚡ New Free Workshop Resource: Hybrid & EV Powertrain Engineering & ECU Diagnostics Training (8 Free PDF Manuals) →