WinOLS Automated Bot Project

First, install the Python file monitoring library: (Windows run CMD)

1. 1. Go to the official Python website and download the latest installer for Windows (e.g., Python 3.11 or 3.12).
   2. Run the downloaded installer.
   3. Crucial: Check the box at the bottom that says “Add python.exe to PATH” before clicking Install Now . If you miss this step, your command prompt won’t recognize Python commands.
   4. Once completed, close the installer.

1. 1. Open the Windows Command Prompt (press the Win key, type cmd , and hit Enter).
   2. Type or paste the following command and press Enter:
      
      cmd

      "pip install watchdog"
      

   3. Wait for the terminal to show a message like Successfully installed watchdog-x.x.x .

mkdir C:\Tuning\Input_Folder
mkdir C:\Tuning\WinOLS_Staging
mkdir C:\Tuning\Output_Folder

Step 4: Save and Run the Python Script

1. 1. Open Notepad (or any text editor) and copy the Python script provided in the earlier response.
   2. Save the file inside C:\Tuning\ and name it folder_watcher.py (make sure it doesn’t end in .txt ).
   3. To run it, open your Command Prompt and type:
      
      cmd

      python C:\Tuning\folder_watcher.py
      

   4. You will see a terminal message saying 🤖 WINOLS HYBRID BOT: STANDING BY... . Keep this window open.

1. 1. Open your WinOLS software.
   2. Ensure you have the OLS530 (Lua Scripting) plugin installed and licensed via EVC.
   3. Open the Lua script editor context inside WinOLS, paste the Lua script provided earlier, and save it as bot_daemon.lua .
   4. Run the Lua script within WinOLS so it begins monitoring the staging folder.

The Python script (tested and working)

folder_watcher

1. The Drop: You manually decrypt a file and drag it into C:\Tuning\Input_Folder .
2. The Python Trap: The script instantly catches the file, waits 1 second to ensure it is fully written to the disk, and moves it to C:\Tuning\WinOLS_Staging\current_job.bin .
3. The WinOLS Consumption: Inside your open WinOLS software, your active background Lua script (which you have programmed to loop or use ReadDirectory() on C:\Tuning\WinOLS_Staging ) notices current_job.bin .
4. The Automation: The Lua script imports it, finds the matching .ols database map, patches it, calculates the checksums, and exports it to your outputs.
5. The Cleanup: Crucially, your Lua script must execute os.remove("C:\\Tuning\\WinOLS_Staging\\current_job.bin") at the very end of its execution block. This leaves the folder empty, signaling to Python that WinOLS is ready for the next file.

• Press Ctrl + C on your keyboard.
• The script will instantly stop tracking your folders and display [🛑 STOPPING] Folder watcher shutting down safely.
• You can now safely close the Command Prompt window.

Now the bit i struggle on!

WinOLS Internal Automation Script (bot_daemon.lua )

• Native Scope Integration: Methods like projectFindSimilarProjectsSql() , projectImportChanges() , and projectApplyChecksums() belong entirely to EVC’s Lua internal plugin framework. They target native operations that avoid manipulating menus or reading windows.
• Project Reference Execution: WinOLS relies heavily on identifying reference indexes. When you run projectImportChanges(master_id) , WinOLS looks up the specified database file path locally, computes the exact geometric difference maps between its original read and its tuned state, and scales/pastes those byte-offsets directly onto your newly opened file.
• The Error Fallback: If matched_project_id == 0 , the script bypasses modifying anything, safely purges current_job.bin from staging, and resets. Your file remains untuned, signaling to you that manual map building is required for that specific software version.

• The script runs an infinite loop that checks your staging folder (C:\Tuning\WinOLS_Staging\ ) every 1 second.
• It is looking for the exact file name current_job.bin (which your Python script creates when you drop a file in).
• It sleeps between checks so it doesn’t max out your computer’s CPU.

• The moment it detects current_job.bin , it automatically imports that binary file into WinOLS as a fresh project.
• It programmatically reads the file’s internal metadata—specifically digging out the ECU Hardware Number and ECU Software Number .

• It uses WinOLS’s internal database engine (projectFindSimilarProjectsSql() ) to search through all of your local saved .ols files.
• It loops through the results to find an existing project file that matches the exact same Software Number as the file you just dropped in. This ensures it only copies maps meant for that specific engine control unit.

• Once it finds your matching master project file in your database, it uses a native WinOLS command (projectImportChanges() ).
• This command calculates the exact difference bytes (the maps you changed, such as ignition, boost, or rail pressure) between your master’s stock version and its tuned version.
• It then pastes those exact map modifications onto the new customer file.

• Because changing bytes breaks the file’s internal security matrix, the script triggers WinOLS’s native checksum blocks (projectApplyChecksums() ) to recalculate and fix the file so it is safe to flash.
• It appends a timestamp and the software number to create a unique filename (e.g., Tuned_1037350123_20261103.bin ).
• It exports this finalized file into your Output_Folder .

• It closes the newly created project within WinOLS so your software doesn’t get cluttered with hundreds of open projects.
• Finally, it deletes current_job.bin from the staging folder . Deleting this file tells your Python script that WinOLS has successfully finished its job and is ready for you to drag and drop the next file.

The Lua script here bot_daemon install into your Lua directory and run it direct from WinOLS Window>Lua

Comment/help below