Before the next read.
Clear expectations for file processing, account access and supported reads.
Will the app change my original file?
No. Processing produces a separate output. Keep an untouched original and validate any file before programming.
Does a supported ECU mean every read can be edited?
No. The server validates the actual file. Read format, software version and available regions can change which operations are offered. Recognition may be available without editing.
Can I use OBD or calibration-only reads?
Some supported workflows accept these reads. A family listing alone does not prove that your particular partial read contains everything an operation needs. The app reports unsupported inputs.
Do I need an original for checksum correction?
Some workflows require an untouched reference, while others support correction without one. Follow the detected requirement in the checksum workspace.
Can I use another PC?
Each PC you use is registered to your account with its own device key. You can see registered PCs in your account. PC access rules for your plan are shown in your account. Virtual machines are not supported.
Where do my files go?
ECU processing takes place on the server. New job originals are archived privately; generated outputs remain downloadable for seven days. Shared content can remain in storage when another legitimate reference needs it. Uploaded files may be retained and studied to improve ECU analysis and repair services as part of using ECUSoftLab. See Terms and Privacy.
How do subscriptions and credits work?
Your shared profile shows activated modules, expiry dates and actual service-credit balances when your account has them. Contact support about access options.
What if the result looks wrong?
Stop before programming. Keep the original and the output, use the job feedback control and contact support with the job number and error details. Do not post passwords, identity secrets or customer files publicly.
Still have a question?
Tell us what you are trying to do.