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

Finding a block of data that looks like a map is only half the job in WinOLS. Until the map has the right size, start address, data format, axes and a factor/offset, the numbers on screen are raw stored values that are hard to judge and easy to change in the wrong place. This guide shows how to define a map in EVC WinOLS: the map properties, dimensions, data organisation, factor and offset, and the axis definition, step by step. Menu names, fields and shortcuts are taken from EVC’s own public WinOLS 5.94 manual, linked at the end.

Checked on 3 November 2026 against the WinOLS 5.94 manual on evc.de and EVC’s product and download pages. EVC lists WinOLS 5.96 (29.10.2026) as the current version and the 5.94 manual as the current manual, so small differences in newer builds are possible. EVC’s own documentation always takes priority over this page (source, source).

Diagram of the WinOLS map properties dialog grouped into four parts: name, description, unit and id; start address, rows and columns and mirror; values, byte order, sign, skip bytes and organization; factor and offset, formula, reciprocal and precision, plus the axis data source options
WinOLS map properties: what each field group does (simplified educational diagram, original illustration)

Before you start

If you are new to the idea of axes and scaling in general, our explainer on ECU maps, axes, interpolation and factors gives the background without any tool-specific steps.

Step 1: set the view so the data reads like a map

EVC’s manual describes starting a manual search by setting the view parameters: 8, 16 or 32 bit and the byte order HiLo or LoHi. You then adjust the number of columns (hotkeys M and W) until the rows line up, and move the origin left or right with Ctrl + cursor left/right so the map starts at the left of the hexdump. Ctrl+B (“View > Optimize value range”) helps when the bar display shows nothing useful (source).

The byte order is what EVC calls the data organisation: the least significant byte can be stored first, or the most significant byte can be first, also known as Intel or Motorola storage. The command is not available for 8-bit data (source). A wrong byte order is one of the quickest ways to get a map that looks like noise.

Step 2: turn the selection into a map

  1. Select the map data as a consecutive rectangle in the hexdump. The size of the selection should match the size of the later map (source).
  2. Press K (“Selection > Selection -> Map”). A new map window opens (source).
  3. The assistant “View > Support map selection” can optimise a selection for you (columns, start), but EVC warns you should still make sure no data that does not belong to the map is included (source).

You can also create a map by typing its parameters: press K anywhere in the hexdump, with no selection or a 1×1 selection, and WinOLS creates a map at that address and opens “Properties: Window” so you can enter name, size and the rest by hand. If you have just copied map properties, those are applied instead (source). EVC notes that “Insert new Map” in the Edit menu is rarely used, because converting a selection is easier (source).

Step 3: open the map properties (Alt+Enter)

With the map window active, open “Edit > Properties: Window” (Alt+Enter) (source). The first sheet holds the core definition. The fields that matter most, in EVC’s terms (source):

Step 4: set factor and offset so you see physical values

WinOLS uses factor and offset to show physical values. The formula is Displayed value = Value x Factor + Offset (source). As a purely arithmetical example (not taken from any ECU): a stored value of 1250 with factor 0.1 and offset -40 is displayed as 85.

Once factor and offset are set, edit in the values you want to see. EVC’s manual says that when using factor/offset you should always enter the value you later want to see, not the stored eprom value; WinOLS converts it for you (source).

Four-step diagram of defining a map in WinOLS: set the view and byte order, select the data and press K, open the properties with Alt+Enter, define the axes; with a factor and offset arithmetic example and a checklist before editing
Defining a map in WinOLS step by step (simplified educational diagram, original illustration)

Step 5: define the axes

Each axis needs the same care as the map body. The key setting is the Data source, which defines where the axis data comes from (source):

Give each axis its own description, unit, factor and offset so that, for example, a speed or load axis shows readable steps. In a map window you can click the axis description, or the upper left corner of the map, to change the unit, factor, offset or description of the axis or of the map data quickly (source). For vertical maps, where each data row starts with its Y-axis value, EVC’s recipe is: set rows/columns to the map data only, put the start address on the first data cell, set the line skip bytes to 2 (WORD) or 1 (BYTE) and the Y-axis byte skip to 2 x columns (WORD) or 1 x columns (BYTE). Alternatively select only the map data and press K (source).

Two features save time on later projects:

Step 6: check the result before you change anything

How to send your file to ecufilemarket.com for tuning

If you would rather have the calibration done for you, send us the original read:

  1. Read the ECU with your genuine tool and keep the untouched original file safe. Export the original from WinOLS if it lives in a project.
  2. Open our upload page, attach the original read and add the vehicle, engine, ECU hardware and software numbers, the tool and read method, the stage you want and any hardware already changed.
  3. Check the credit cost on our pricing page before you submit.
  4. Most files are returned in less than 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 3 November 2026)

WinOLS is a registered trademark of EVC electronic GmbH; Bosch and all other brand names belong to 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 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) →