Sending a Job to the Bench: Automated Transposition From Your Own Portal

There is a step in every experienced shop’s day that is pure mechanics. The thinking is done — the same car, the same calibration, work you finished months ago and can point at. What is left is opening WinOLS, finding the old project, importing the changes onto the new read, exporting, checking. Twenty minutes of moving something you already own from one file to another.

Transposition, not tuning

The industry word for this is transposition, and it is worth being precise about what it is, because it gets sold as something grander than it is. It does not invent a calibration. It takes edits that exist in one file and puts them in the right places in another read of the same ECU.

Whether that works depends entirely on what you are willing to call “the same”. Measured across 167 real pairs of original and delivered files: grouped loosely by ECU family, the edits land at the right addresses about 16% of the time. That number is not a failure of the method — it is the method correctly telling you that an EDC17 in a van and an EDC17 in an estate car share a chip, not a program.

Group the same files by their actual calibration and the same measurement reads 96%.

The gap between those two numbers is the entire subject. Identity comes first. Get the grouping right and transposition is close to a solved problem; get it wrong and it is a random number generator with a progress bar.

What the portal actually does

Once your portal can ask your own archive what it holds, the next question asks itself: if the work is in there, can the bench do the transfer without anyone walking across the workshop?

On a paired machine it can. You press a button on the request. Your machine collects the original and the order over its own signed channel. A Lua automation script drives WinOLS — your licence, your installation, your archive — to choose a donor, import its changes, export a binary and run its checks. The result comes back and attaches itself to the request with the verification sitting next to it.

Then it stops.

The stop is the feature

Nothing reaches the customer automatically. The file arrives in the portal with its checks and waits for a person to read them and click Deliver. There is no setting to remove that click, and there will not be one.

This is not caution for its own sake. An automated bench is a machine that produces confident-looking output, and confident-looking output is exactly what you must not ship unread. The value is in removing the twenty minutes of mechanical work, not in removing the person who knows what a bad export looks like.

The order travels with the job

Here is the failure that is easy to miss and expensive to find. A bench robot left to its own judgement picks the best donor version it can find. But “best” is its opinion, not the customer’s order. A Stage 1 request can come back as Stage 1 plus a DPF delete, fully validated, technically excellent, and completely wrong — and nothing in the file says so.

So the modifications on the request travel with the job as an instruction. A donor whose changes are not exactly the set that was ordered is refused rather than substituted. When it refuses it says what was ordered and what was available, which is a far more useful sentence than a generic failure, because it tells you whether the problem is your archive or your request.

Where the boundaries are

WinOLS and the Lua script that drives it run on your machine, under your own WinOLS licence, on a local port that never faces the internet. The paired relay is the only thing on that computer with a channel to your portal, and it is the only thing that talks to it. The original goes there because you asked for it, and discarding a result removes the file from that machine and the job from the portal — customer binaries do not quietly accumulate on somebody’s workstation.

Work on a bench takes minutes, so the button returns immediately and the request tells you where the job is: waiting, running, finished with its verification, or refused in the tool’s own words with the job reference on that machine so the log there can be read. Nothing in the portal sits blocked while a machine thinks.

Who this is for

Shops that already run WinOLS on a dedicated machine, with a real archive behind it. If your projects live on one workstation and the same calibrations keep returning, this removes a genuinely mechanical piece of the day. If you started this year, or you keep almost nothing, there is nothing here for it to work with — the archive is the raw material, and no amount of automation manufactures it.

It is offered on request rather than as a checkbox, because connecting it to an existing bench is a setup conversation, not an install. Tell us what you run and what your archive looks like, and we will tell you honestly what connecting it would involve — including if the answer is that it would not be worth it.

How bench automation works → · Talk to us about it →