MyTuningBot is the WinOLS Lua bot that turns your tuning shop into a 24/7 automatic file service. It reads incoming files straight from your portal,
matches them against your own .ols database,
applies the right solutions and ships the tuned file back to the customer typically inside 60s.
MyTuningBot lives on the same PC as your WinOLS installation. A thin local relay listens for tickets from your portal, dispatches them to a Lua script inside WinOLS, and pushes the tuned file straight back. The portal API does the talking. WinOLS does the tuning. You do nothing.
A .bin / .ori / .mod / .zip / .rar / lands in your tuning portal with the tuning options the customer picked.
// portalThe relay polls the ticket-server, locks the file (so two bots can't grab it twice) and pushes the request into WinOLS.
// relayBOT reads your .ols database, runs case-insensitive keyword + exclude rules, finds the right version.
The difference bytes from the matched version are applied to the customer's original, and the ECU checksum is recalculated.
// winolsTuned file uploaded back to the portal, customer notified by email + push, credits/invoice settled automatically.
// portalMost tickets close in under a minute — file in, file out, customer notified. Complex multi-option requests rarely cross the two-minute mark.
The .ols database stays on your machine. The bot only sends the tuned customer file back to the portal — never your maps, never your IP.
If no version matches the request — unusual combo, missing keyword — the bot quietly hands it to your manual queue. Customer never sees an error.
MyTuningBot doesn't decide what's a Stage 1 or a DPF off — you do, in your .ols database.
The bot matches whatever you've labelled (free-form: STAGE1, Stage 1, Stage1 Vmax, DPF EGR…)
and ships it. Out of the box it handles the full menu most shops sell:
Performance map matched by Stage1 keyword, excluding combo versions.
Same matching pattern, separate Lua rules for hardware-required stages.
// hardware tunesDiesel particulate filter removal — works standalone or combined with EGR.
// dieselEGR delete with optional hysteresis ("EGR ISTERESI") and DTC mask.
// dieselSCR shutdown for compatible ECUs — DCU and main-controller variants.
// dieselCode-by-code removal (e.g. P0476, P04XX) or full DTC mask.
Top-speed limiter delete, matched separately so it can be combined.
// petrol / dieselCrackle / decel map matched against your custom version label.
// petrolRev-limit hardcut with selectable RPM, exposed as a tuning option.
// petrol2-step launch with configurable RPM, matched to your stored map.
// petrolO2 sensor removal — pairs with cat-off or pure performance maps.
// petrolCatalytic-converter-off mapping for race / off-road builds.
// petrolIntake-flap and TVA disable, matched by your free-form version name.
// petrolOEM torque-limit removal for performance and tow setups.
// performanceWipe-to-stock matched against your CLEAR versions for rollback tickets.
UNION of keywords across the ticket's main + options — "DPF + EGR" needs both substrings in the same version.
// combosMyTuningBot isn't a recorded keystroke macro that breaks the first time WinOLS pops a dialog. It's a proper bot — a Lua script inside WinOLS, a signed local relay, and a queue-aware ticket server. Here's the surface map.
The bot runs as a Lua script inside WinOLS itself — no screen-scraping, no fragile UI automation. It uses the official Lua API to load projects, query versions and export tuned files.
Point the bot at DB_QT25_VW.ols, DB_QT25_BMW.ols — your own tuning files. The bot iterates versions and matches against the ticket request. Your maps stay on your PC.
Case-insensitive keyword AND exclude rules. Stage 1 matches STAGE1, Stage 1 and Stage1 … but skips Stage1 Vmax unless Vmax was also requested. No prefix-only matching nonsense.
Customer uploads a protected .mmf? The bot decrypts it natively via the MMS API, applies the tune, repairs the checksum (EDC15/16/17, MED9/17, SID807, SIMOS, MEVD17, Magneti Marelli, Delphi, Denso) and re-encrypts it automatically before sending it back. Your customer gets a flashable file in the same format they uploaded.
HMAC-SHA256 signed requests between portal ↔ relay, 5-minute replay window. The bot's PC initiates the connection — no inbound ports, no firewall holes, no exposed services.
The matching rules live in tuning_map.json — keywords and excludes per tuning option, editable in any text editor. Tweak how a new tuning option matches without touching code.
Run one bot per WinOLS PC — diesel team, petrol team, agriculture team. Routing rules on the ticket-server send the right files to the right bot. Each one shows a live heartbeat.
WinOLS hiccup? Lost connection? The ticket isn't lost — the relay retries with backoff, and if the bot stays down past your SLA, the ticket gracefully reroutes to the manual queue.
Every state change — new ticket, bot tuning, delivered, fallback — fires a notification through your portal. Pushover for instant phone alerts. Email for customers. Audit log for everything.
The portal deducts the customer's credits / charges their card / sends them an invoice the moment the file ships. The bot stays focused on tuning. Money is the portal's job.
See every bot, every queue, every in-flight file. Median turnaround, hit rate, fallback rate, per-bot uptime, last 24 h heartbeats. Built into the MyTuningPortal admin.
Test new tuning rules against past tickets before sending to live customers. The bot replays archived tickets in WinOLS, shows you which version it would have picked, no actual delivery.
We're not going to pretend this is rocket science. A skilled tuner can do everything the bot does — just slower, only during office hours, and only one ticket at a time. Here's the math.
| Manual tuner | MyTuningBot | Generic macro recorder | |
|---|---|---|---|
| Average file turnaround | 15 – 120 minutes | ~60 seconds | 3 – 5 minutes |
| Available 24 / 7 | — | requires PC unlocked | |
| Uses your own .ols database | — | ||
| Keyword + exclude matching (combo-aware) | by hand | automatic | prefix only |
| Graceful fallback to humans | n/a | breaks & stops | |
| Parallel files at once | 1 | unlimited (multi-bot) | 1 |
| Survives WinOLS dialog popups | n/a | — | |
| HMAC-signed portal ↔ bot link | n/a | — | |
| Push / email / Pushover alerts | manual | — | |
| Auto credit deduction + invoicing | manual | — | |
| Cost | 1 full-time tuner | €249 / month · unlimited | €20 + your time fixing it |
No tiers. No ticket caps. No surprise overages. €249 per month, everything included unlimited files, multi-bot orchestration, all features, all updates, all support. The same price whether you ship 50 files this month or 5,000.
mapping rules edit how the bot matches your mapsYes — really unlimited, no fine print. Ship 50 files this month or 5,000, the price stays €249. Heavy users who hit 10,000+ files a month sometimes graduate to a dedicated-relay setup (still flat-price, just on its own infrastructure so you don't share the queue), but that conversation is rare and friendly. There is no usage-based billing and no overage fee.
Yes — MyTuningBot is a WinOLS bot. It runs as a software WinOLS installation and uses the official WinOLS Lua API to load projects, query your tuning versions and export tuned files. You need a licensed WinOLS on a Windows PC that stays online while the bot is working. If you don't have WinOLS, talk to us first and we'll help you set it up.
No. Your .ols database — your intellectual property — stays on your PC. The bot only sends the tuned customer file back to your portal. Your maps, your years of work, your competitive edge — they never leave the machine. The portal ↔ relay link is HMAC-SHA256 signed and only carries customer files in both directions.
The bot falls back gracefully. If the keyword + exclude rules don't find a matching version in your .ols database, the ticket is automatically rerouted to your manual queue — exactly as if a customer had submitted a manual-only request. The customer sees "engineer is on it" instead of an error. No lost files, no awkward emails.
This is the part most macro-recorder bots get wrong. Tuners label versions however they want — STAGE1, Stage 1, Stage1 Vmax, Stage1 DPF EGR. From your admin panel you point each tuning option at the right family of versions and tell it which to skip, then the bot does the rest. For combo requests (e.g. Stage 1 + DPF off) the bot combines the rules across every option in the ticket so the cleanest matching version is always picked — no code, no config files, everything from the dashboard.
The ticket isn't lost. The relay retries with exponential backoff. If the bot stays offline past your configured SLA (default: 5 minutes), the ticket gracefully reroutes to your manual queue and the customer gets the same "engineer is on it" message. When WinOLS comes back, the bot resumes the queue automatically.
About 2 hours, done together over WhatsApp screen-share. We install the software on your computer, configure the relay, hook it to your portal, import a starter tuning_map.json, run the first dry-run against archive tickets to make sure matches look sane, and switch it live. You start shipping automated files the same day. There is no setup fee.
Yes. No contract, no minimum term, no cancellation fee. Cancel from the admin panel or by email — the bot keeps running until the end of your current billing period, then we shut it down cleanly. Your .ols database was always on your PC anyway, so there's nothing to "get back".
No slide deck. €249/month, unlimited files, cancel anytime.