7 min read

Virtual Reads and Original File Databases: The Risks Tuners Take, and the Rules to Set

A virtual read can save a trip to the bench, but it is not a record of the car in front of you. This guide covers what an original file database holds, four ways a library file can let you down, and the licensing and record-keeping rules to set before you rely on one.

Five steps before using a library file: read ID data, find a match, compare, prefer a real read, record the source.

A customer's car is on the ramp, the bench is free, and the read is the slow part. Somewhere in an original file database there is a file for the same ECU that someone else already read. Pulling it from the library and starting the tune from there looks like a shortcut. Sometimes it is one. It is also the point where a tuning job picks up risks that nobody sees until a car misbehaves.

This article is for tuners who already handle original files every day. It covers what a library of originals holds, what a virtual read does and does not give you, four ways a library file can let you down, and the rules and records worth putting in place before you rely on one. Supplier sites list a file database as a selling point, usually with a size claim attached. They rarely say where the files came from or what a match does and does not promise.

Quick definition

What is an original file database?

A library of stock ECU reads, often called ori files, that you can search by ECU or software details. It is used to find a known starting point, to compare a customer's read against a stock file or to restore a car to stock.

What an original file database holds

An original file database is a collection of unmodified ECU reads, indexed by the identification data inside each file: the hardware number, the software number and the ECU family. You search on those details and the database returns files that claim to match.

Three things about that description matter for everything that follows.

  • The files came from somewhere. Reads arrive from several possible sources: workshops that uploaded them, a supplier's own jobs, or imports from elsewhere. Whoever built the library decided what counted as an original. You did not.
  • The index is the match. A library matches on identification data. Two cars with the same software number can still have different histories.
  • A library is a snapshot. It holds what a unit looked like when someone read it, not what your customer's unit looks like today.

Virtual read versus a real read

A virtual read gets you an original file without dumping the unit's memory. In the usual form the tool reads only identification data, a library supplies a matching stock file, and you carry on as if you had read the car. The speed is real. The catch is in what the file is.

Quick definition

What is a virtual read?

A way of getting an original file without reading the ECU's memory. The tool reads the unit's identification data and the file comes from a library that matches it, instead of from the car itself.

What each method actually gives you

The speed gain of a virtual read comes with a different kind of file.

Real readVirtual read
What you getThe memory of this unit as it is todayA stock file matched on identification data
Earlier changes on the carVisible in the readInvisible: the library file knows nothing about them
Data specific to the unitIncluded where the tool can read itLeft out or generic, depending on the platform
Return to stockA true record, if the read is untouchedA close relative of the car's original, not the original
If a job goes wrongYou can show what was on the carYou can show only what you assumed
EffortA full read cycle on the carA quick identification and a search

Four ways a library file can let you down

  1. It is not this car's file. An earlier flash, a software update at a main dealer or a previous tune all change what is in the unit. Some platforms also store data that belongs to the individual unit. A library file knows none of that.
  2. The label can be wrong. A file marked as an original may be partial, previously modified or filed under the wrong software number. Without the car's own read there is no second source to check it against.
  3. Checksum correction hides the mismatch. A tuned file built on the wrong base still gets its checksums corrected, and the ECU accepts it. The checksum only proves the file agrees with itself.
  4. There is no way back. If a library file is your only base and something goes wrong, you cannot restore what was on the car, because you never had it. You can restore a close relative of it.
Quick definition

What does checksum correction do?

It recalculates the check values inside a modified file so the ECU accepts it as valid. It does not check that the file started from the right original.

Rules to set before you rely on a library

None of this is a ban. It is a short list of rules a tuning business can write down once and follow on every job.

  1. Read the physical ECU whenever it can be read. The library is the cross-check, not the source.
  2. Read your supplier's terms. Database access is usually tied to an account and credits. Check whether files may be used only on your own orders, and whether copying, bulk export or passing files to third parties is allowed. Terms differ by supplier.
  3. Remember whose software it is. ECU software belongs to the manufacturer. Rules on reading, copying and modifying it differ by country, so take advice for your market. This article is not legal advice.
  4. Say which base you used. Write on the job record whether the base was a real read or a library file, and tell the customer when it was a library file.
  5. Treat files as personal data. A read can carry the VIN, and a VIN linked to an owner can count as personal data in the EU. Limit who can open files and decide how long you keep them.

Keep your own record of every original

The safest original file database is the one you build yourself from your own reads. It has known provenance, it matches cars you have actually worked on, and nobody else's terms apply to it. It only takes a routine.

Five-step routine for keeping an original read: read, save untouched, log details, store read-only, link to the order.

The five steps cost a few minutes per job. They pay off the first time a customer comes back with a complaint and you can show exactly what was on the car before you touched it.

Where a file portal fits in

A portal that identifies files adds a second pair of eyes to this routine. It does not replace it. On TheTuningGroup you send the stock read from your own tool, and the portal identifies the ECU and checks it on intake. A real tuning engineer then writes a custom file for that vehicle, and checksum correction is part of the job. Because the base is your own read, the record starts with the car in front of you.

The Tools & ECU support page lists the tools and ECU families covered, and How it works walks through the order flow.

Common questions

Is a virtual read ever acceptable?

As a cross-check, or as a starting point when the unit cannot be read, yes. The identification has to match exactly, you note the source on the job record, and you are ready to say so to the customer. It is not a substitute for a real read when the ECU can be read.

Can I build my own original file database?

Yes, and it is the safest kind. A private store of your own reads has known provenance and no third-party terms. Keep it access-controlled, log the tool and version for each read, and never edit an original in place.

Is it legal to use files from an original file database?

It depends on your country, the supplier's terms and how you use the file. Read the terms, keep to your own orders, and take advice for your market before building a business process on a shared library.

Does checksum correction fix a wrong base file?

No. Checksum correction makes the ECU accept the file. It cannot tell whether the file started from this car's original, so the base still has to be right.

Start every job from your own read

Create a free TheTuningGroup account, upload your original read and we will identify the ECU on intake and show the price before you commit.

Create free account