Workshop questions.
Careful answers.
ECUSoftLab is built around the work that happens after an ECU read: understanding the file, choosing a supported operation and reviewing the output.
The lab is a process.
ECUSoftLab started in a tuning workshop. The questions were practical: what is in this read, which operation is justified, and how can the result be checked before it goes back to the vehicle?
That workshop-to-workshop approach shapes the software. Support is studied from real ECU reads and compared with known results. Structural validation matters more than a familiar filename. Where a layout or operation cannot be established, refusal is the useful answer.
Proven, precise, server-side and current are working principles—not a promise that every file from a named family will pass. Full reads, partial reads and modified files can have different coverage, and the app must explain those limits.
The same care applies to the customer: keep the original, produce a separate output, keep job history attached to the account, and do not expose firmware, VINs or immobiliser secrets in a public catalogue.
Support develops through analysis of real reads and comparison with known results. The goal is structural validation rather than guessing from a filename.
The catalogue identifies the public ECU families. The actual file determines what can be offered. We do not publish detection internals, offsets or customer data as marketing material.
Server-side, always connected.
The Windows app provides the workspace. Processing rules and support catalogues live on the server, allowing updates without placing ECU engines in the desktop download.