How the FILHEX ECU file service works

Each step in detail

1. Read the ECU and keep the original

FILHEX starts where your read ends. Read the control unit with the tool and method you normally use (OBD, bench, or boot, depending on the ECU) and keep an untouched copy of that read — it is your way back if anything goes wrong on the car. The File you upload to FILHEX should be the complete, unmodified original read of that ECU. Partial or already-modified reads are a common reason a scan comes back with fewer Solutions than the Catalog suggests.

2. Upload and scan

Open New Solution Job in the app, upload the File (up to 16 MB), and let scan run. Scan reads the binary itself and reports the Brand, the ECU, and the exact Solutions that apply to that software version. It never spends a Credit, so you can check a File before you decide anything — including before you buy your first pack. A File that is not supported, or that has no applicable Solutions, is a dead end you learn about before paying anything; the app offers to send that Brand/ECU to support so coverage can be reviewed.

3. Select Solutions

Pick every Solution you need on this File in one go — for example DPF Removal together with EGR Removal, or Stage 1 with Start & Stop Disable. Combining Solutions on one Solution Job does not change the price: 1 Credit covers the whole job, however many Solutions you selected. Choose only Solutions that match the hardware state of the vehicle — a File that assumes a removed part while it is still fitted (or the other way round) is the classic cause of limp mode and regeneration loops. That judgement stays with the workshop.

4. Process — automated

Confirm the job. Every Solution is prepared and maintained by our engineering team; the job itself runs automatically, the app polls status for you, and there is no queue of people to wait for. A Credit is only captured when the Solution Job completes and a result File exists. If the job fails for any reason, the reserved Credit goes straight back to the wallet. At 0 Credits the job is saved as priced and waits in the list — buy a pack and process it when you are ready.

5. Download, verify, flash

Download the result File from the job. The app checks the download against its SHA-256 before saving it, and suggests a filename that names the ECU and the Solutions on it, so the right File lands on the right car. Flash it with the same tool and write method you used for the read. The original File, the selected Solutions, and the result File stay together on the job in your Workspace, so you can come back to any job later and see exactly what was delivered.

6. DTC clear after the job

Need a code gone that scan could not foresee — a sensor that was unplugged during the mechanical work, a module that is no longer on the bus? Open the completed job, start DTC clear, search and select the codes, and download the updated File. It runs on the result File, is free, and can be used up to 3 times per File.

7. Compare in the Hex Editor

The app includes a Hex Editor built for checking, not for authoring maps. Open the original and the result of any job side by side, jump through the list of differences block by block, read values as 8/16/32-bit numbers or a 2D graph, and search for hex or text. It is the quickest way to see what changed before you write a File to a customer's car. Local byte edits are possible but stay on your PC; FILHEX does not correct checksums on locally edited Files and warns you before you export one.

Credits in one paragraph

1 Credit = 1 processed File. Each new Workspace receives 5 free Credits after email verification. Packs are €5 for 1 Credit, €40 for 10 Credits, €150 for 50 Credits, €200 for 100 Credits — one-time purchases bought in the app by the Workspace Owner, paid by card through Stripe in your browser. Packs stack, Credits never expire, and there is no subscription. Full detail on pricing.

FAQ

Next: what the file service covers · ECU tuning files explained · full Solution list · Download FILHEX.