Six things you can check yourself
A report with every file
Which maps changed and by how much, every protective map that changed and why, the limits it was checked against, and anything outside the known maps. You can hand it to your customer.
Emissions and OBD untouched
Every emission and diagnostic map of the software is compared with the original, one by one, and the report says how many were checked. A file that changes one is rejected, ours or anyone else's.
Honest status
Statically checked, road validated with logs, or measured on a dyno: each file says which one it is. If it has not been on a car yet, the report says so.
Support after the flash
Send a log after flashing. We put it on the file's own maps, cell by cell: boost, knock, lambda. If the car needs a correction, it is free.
Fix it or money back
If a file does not work as described, you get a free correction or your credits back. No discussion.
Your files stay yours
Every read is encrypted with its own key and stored in three copies. Nobody outside your company sees it, and the customer never sees who else worked on a file.
What the report looks like
Real numbers from version 3 of the case study car below, not a mock-up.
The same checks run in File Check on any file you upload, ours or another provider's. The two open points are exactly why the status is not higher.
One car, every version, every miss
Our own test car. We publish the whole path, including what did not work, because that is how you can judge how we work.
- Car
- VW Golf 5 GTI, 2.0 TFSI (BWA), manual
- ECU
- Bosch MED9.1.5, SW 391082
- Hardware
- Stock K03 turbo, intake, downpipe and catalyst; aftermarket exhaust after the catalyst
- Fuel
- 98 RON
- Status
- Calibration proposed, not yet road validated
v2: 2,960–3,680 rpm, through the mid-range. v3: a single event at ~2,250 rpm at the start of a pull; the mid-range is clean. Our target is under 3°, so v3 is not done.
Checking files that are already out there
A widely shared Stage 1 changed 16 protective maps without any reason. Another popular file switched off catalyst diagnosis, so we rejected it. One raised rail pressure above a limit the ECU enforces anyway: the change could never take effect, and the log later showed 110 bar. A widely used map pack had 54 maps shifted by one byte; we found and corrected it.
Boost below target
Boost 180–350 mbar under target because the boost controller limit was still stock. One pull with −3° on cylinder 2. Lambda and fuel OK.
Boost reached, but too much
Overshoot up to +210 mbar between 2,960 and 3,680 rpm, knock retard up to −4.5° on cylinder 4. Not good enough: replaced.
Mid-range clean
Overshoot down to +50 mbar, no knock retard through the mid-range. Still open: one −3.75° event at ~2,250 rpm, and above 4,700 rpm the stock turbo cannot hold the target even with the valve at ~95 %.
Less load low down, target the turbo can reach
Lower load at 1,750–2,500 rpm, and a boost target at the top that follows what the K03 actually delivers. Validated only when the next log says so.
Our numbers, live
Straight from our database, never edited by hand.
What we will not do
- Call a file “dyno tested” without a dyno run on that software.
- Promise horsepower we have not measured.
- Switch off a protection without writing down why.
- Hide a failed check or an open point.
- Change bytes outside the known maps of the software.
- Buy, write or show fake reviews.