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

WinOLS can already re-apply known changes with its built-in scripts, but some jobs need more: checking every incoming file the same way, reading project properties, correcting checksums and exporting a result without clicking through menus. For that, EVC sells an optional plugin called “External Control”, which brings the LUA programming language into WinOLS. This guide explains what the WinOLS LUA plugin is, what you need, how to start a script and how a simple, safe script is built. Every fact comes from EVC’s own public LUA manual and product pages, linked at the end.

Facts checked on 2 November 2026 in EVC’s “External Control for WinOLS” manual (as of 27.10.2026) and on evc.de. Function names and options can change with plugin updates, so EVC’s current manual always takes priority over this page. New to WinOLS? Start with our guides to creating a project and to map packs and built-in scripts.

Diagram of the WinOLS External Control LUA plugin: requirements (registered WinOLS, registered OLS530 plugin, programming knowledge), difference to built-in winolsskript scripts, three ways to start a script and the security warning
WinOLS LUA plugin: requirements and how a script starts (simplified educational diagram, original illustration)

What the External Control (LUA) plugin is

EVC describes External Control as a plugin that lets you control many WinOLS functions through scripts, so that repetitive data processing steps can be automated. To do this, the plugin brings a complete programming language with it: LUA, an existing language that was integrated into WinOLS (source). The manual documents the WinOLS functions that LUA can call; for the language itself EVC refers to the official LUA homepage (source, source).

EVC’s product page gives three application examples: reading and writing individual bytes in a project, applying changes to each incoming file depending on the Bosch number and sending the result by mail, and the fact that the WinOLS online checksum search is itself written in LUA (source). Scripts can be applied on demand to the current project, or run permanently and process incoming files (source).

Not the same as WinOLS scripts. EVC points out that External Control has nothing to do with the script functions already built into WinOLS (*.winolsskript files) and that it is “a lot more powerful” (source). The two can still work together: a LUA script can import a WinOLSScript file into the current project with projectImport (source).

What you need

EVC offers the manual and sample programs for download on the LUA product page, and from WinOLS 5.70 / OLS530 3.005 there is a separate LUA debugger (source).

Step by step: starting a LUA script

EVC lists three ways to start a LUA script (source):

  1. As a start parameter. Pass the complete path and file name of the script when starting WinOLS. This needs WinOLS to be closed: if WinOLS is already running, the start is ignored and the script runs in the open WinOLS if possible.
  2. Drag and drop into the WinOLS frame window. Drop the .lua file onto the main window.
  3. Drag and drop into a project window. The target project then becomes the default project (the “context”) for the script.

Understand the context. Many functions work on the current WinOLS state. projectSave, for example, only saves the project that is currently selected. EVC compares LUA for WinOLS to a macro recorder that replays keystrokes. If the needed context does not exist (for example projectSave() with no project open), the function fails and returns an error value (source).

Always use full paths. EVC recommends passing file names with the complete path, because WinOLS cannot guarantee the same working directory every time. Inside LUA strings, backslashes must be doubled, for example "c:\\myfiles\\file.bin" (source).

The building blocks of a first script

These functions from EVC’s manual are enough to understand most simple scripts (source):

Eight-step diagram of a typical WinOLS LUA job: project context, projectImport with full paths, change data, search and apply checksums, check projectStatChecksums equals 0, save a new version, export, log and close before quitting
A typical WinOLS LUA job step by step (simplified educational diagram, original illustration)

Example: check checksums, save a version and export

The short script below is our own example, written only with functions and syntax documented in EVC’s manual (source). Drop it into a project window that already contains your modified version. It runs the checksum search and calculation, stops if the status is not 0, and otherwise saves a new version and exports a binary next to a folder you choose.

-- Example only: test on a copy of a project first
Log("Checksum check started");
sw = projectGetProperty(ePrjPropEcuSoftwareversion);
projectSearchChecksums();
projectApplyChecksums();
status = projectStatChecksums();
if (status == 0) then
  projectSave(TRUE, "Checked by LUA", "Software "..sw);
  projectExport("C:\\ols_out\\[ImportFilename|file]_checked.bin", eFiletypeBinary);
  Log("Checksums OK, file exported");
else
  MessageBox("Checksum status "..status.." - file NOT exported", MB_ICONWARNING);
end

Notes on the example: [ImportFilename|file] is a placeholder documented by EVC that uses the import file name, with “file” as the fallback when it is not available (source). Checksum correction in WinOLS needs the right registered checksum module for the ECU; our guide to checksum correction with plugins (F2) explains this.

Running scripts on a server: EVC’s recommendations

Safety rules before you automate anything

Common problems

How to send your file to ecufilemarket.com for tuning

Not every workshop wants to write and maintain its own scripts. If you would rather have the tuning file prepared for you, upload your original read to ECU File Market:

  1. Export the untouched original from WinOLS (or send the file exactly as your reading tool saved it).
  2. Open the upload page, attach the file and add the vehicle, engine, ECU hardware and software numbers, the tool and read method you used and the stage you want.
  3. Check the credit cost on our pricing page before you submit.
  4. 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 2 November 2026)

WinOLS is a registered trademark of EVC electronic GmbH; LUA and all other 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. Names are used only to describe compatibility and workflow. Use only genuine, licensed software and plugins.

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) →