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

Two jobs come up again and again once a file is in WinOLS: checking exactly what changed between two files, and re-using the work from an older project on a new read of a similar ECU. WinOLS has dedicated functions for both. This guide shows how to compare two ECU files in WinOLS with the Differences window and reference versions, and how to import changes from an older project with the Import changes assistant, using the menus and shortcuts described in EVC’s own manual.

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

Diagram of comparing files in WinOLS: the Original and a version feed the Differences window (Ctrl+U), with navigation keys E, V, N, L, the Select reference version dialog and connected windows with an address offset
Comparing the Original with a version in WinOLS (simplified educational diagram, original illustration)

Before you start

Part 1: compare the Original with a version

EVC describes the basic idea on the product page: the original of every project is stored permanently, changes are stored as versions, and changes are displayed in colour, with the option to restore original values at any time (source). To compare a second file with the stock read, import it into the same project so it becomes a version. The manual explains that a file dropped onto an open project window is imported as a version of that project (source).

Step 1: open the Differences window

Use View > Differences or the keyboard shortcut Ctrl+U. According to the manual, this dialog shows the differences (up to 2000) from the original to the current version of the window, and its buttons let you edit the values in the list (source, sections 7.13 and 11.2). Useful details from the same sections:

Step 2: jump from difference to difference

For a quick walk through a file, the View menu has four navigation commands with single-key shortcuts: E (first difference), V (previous), N (next) and L (last). The manual notes two rules that keep this fast on large files: if several differences are directly behind each other, the function stops only at the first one, and in the hexdump it stops only at the first difference inside a map (source, sections 7.14 to 7.17). So a whole changed map counts as one stop, and you then inspect the map itself.

Step 3: change what counts as “original” when you need to

Sometimes you want to compare two versions with each other, not with the stock read, for example “Stage 1 v1” against “Stage 1 v2”. The dialog Select reference version (View menu) handles this. The manual explains that several functions use an “original version” as reference, that by default this is the version read from the ECU, and that you may choose any other version of the current or another project instead. You can also set the kind of comparison for the visual display (for example a minimum difference before a cell is marked as changed) and enter an offset if the data in one project has moved compared with the other (source, section 7.18).

Step 4: compare two different projects side by side

To compare files that live in two separate projects, use Connect windows (View menu, Ctrl+2 in the shortcut list). The manual describes that when two windows are connected, scrolling one scrolls the other in the same way, and the other window is used as the “reference version”, meaning its data temporarily acts as the original for the current window (source, sections 2.12 and 7.19). If the data is not at the same address in both files, set the address offset: type it in, use the “Automatic” button to let WinOLS look for a similar area in the other project, use the +/- buttons, or take it from the two cursor positions.

Part 2: import changes from an older project

When a new car arrives with a software version similar to a project you already did, there is no need to redo every map by hand. EVC’s product page sums it up as “Accept changes”: copy the best changes from old projects, with maps recognised automatically even if they moved to a different position (source). The manual’s section 2.12 lists several ways to bring data across (Import similar project, Import changes, Reference version with connected windows, Import maps, Map packs, Scripts, AutoUpdate/AutoImport) and calls Import changes the simplest one (source).

Diagram of the WinOLS Import changes assistant: an open source project and the current target project, automatic and manual mode, and three steps covering source selection with tolerance, map selection as relative difference or absolute, and changes outside maps
Import changes from an older WinOLS project (simplified educational diagram, original illustration)

Step 1: open both projects

Create the new project from the stock read of the new car first, then open the older, already modified project as well. The manual is explicit that only projects which are currently open can be selected as the source, and that the current project is always the target (source, section 4.12.11).

Step 2: start the assistant

With the new project active, choose Project > Ex- & Import > Import changes (Ctrl+Alt+I). The manual describes two modes (source):

Step 3: work through the three pages of the automatic mode

  1. Choose the source project. If it has many maps, you can show only maps that were changed in the source to speed things up. You can also enter a tolerance so the assistant accepts small differences when searching the maps in the target, at the cost of a slower search.
  2. Select the maps to import. Choose whether to import the maps (structure) and/or the changed data in them. The manual explains that changes are normally transferred as a difference (the difference between original and version), and that you can choose to transfer the data absolute instead.
  3. Changes outside maps. Bytes changed in the source but not inside a map can also be recognised and imported. EVC calls this “only the second best method”, because changes in maps are safer when the areas and data organisation are known. Changes to checksums and patch blocks are skipped automatically.

(All three steps: source, section 4.12.11.)

Step 4: check the result before anything is written

Common mistakes

Prefer to send the file instead?

If you would rather not compare and transfer files yourself, upload your original read to ECU File Market with the vehicle, engine, ECU hardware and software numbers, the tool and read method, the stage you want and any hardware already changed. Credit prices are shown 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 28 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) →