Frequently Asked Questions: Software, Files, Credits and Checksum

The flow has three steps: upload the file, choose the operation, download your file. The software enables only the operations that fit your file; one that does not fit is not applied. Writing the file to the vehicle and, where needed, correcting the checksum remain your steps.

Stage 1, DPF Off, EGR Off, AdBlue / SCR Off, Full Emission Off, Stage 2, DTC Off, Vmax Off, Decat / Catalyst Off, Lambda / O2 Off, TVA Off, Swirl Flaps Off, Pop & Bang, E85 Flex-Fuel, Start & Stop Off, Immo Off, Torque Limiter Off, Stage 3, Gearbox (TCU) Calibration. Not all of them open on every file; the software enables only the operations that apply to yours.

It is the software file read from the vehicle's engine control unit (ECU). It is read with a reading tool; the unmodified version is the original (ORI) file and the version with an operation applied is the modified (MOD) file.

The original (raw) file you read from the ECU with your own tool. The ECU is identified from the file itself; if it is not recognised, the panel asks you to select the vehicle type, make and ECU yourself. The pre-check is free.

The panel asks you to pick your vehicle yourself: vehicle type, make and ECU. If the library solution for the ECU you picked fits your file, the operations open; if it does not, they stay closed. This analysis does not use credits. If no applicable operation comes up, you can open a request in the Support & Requests tab of your panel and attach your file.

No. EcuPrime Studio runs in the browser; no installation or licence dongle is needed. Log in with a free account and upload your file.

Yes, it is on sale. It is for chiptuning workshops and tuners who read and write files with their own tool and want to make their own files without waiting for anyone else: Stage 1, DPF, EGR, AdBlue and module operations. "AI-assisted" means a solution library that learns from real original/modified file pairs and automatic identification and matching of your file; an operation that does not fit your file is not offered or is clearly marked.

The software is independent of the tool: you upload the open raw file you read with Autotuner, Flex (Magic Motorsport), KESS3 (Alientech) or Dimsport (New Genius / New Trasdata) and the ECU is identified from the file. These names are trademarks of independent manufacturers and are mentioned only to indicate compatibility; EcuPrime is not their dealer, representative or partner.

A raw ECU file (.bin or similar). ZIP and GZIP archives and Intel HEX and Motorola S-record files are opened automatically. RAR and 7z are not opened; extract the archive first.

You can; however, identification data may be missing in a partial read, so the file can be harder to identify. If the file is not recognised, the panel asks you to select the vehicle type, make and ECU yourself. An operation that does not fit your file stays closed; upload the full read if you can.

The package produced by a slave tool is encrypted; the file inside cannot be read, so it cannot be processed. You need to upload the decrypted (open) read; your master provides it.

With your own tool. The software processes the file and lets you download it; it does not write to the vehicle. Before writing, keep a backup of the original file and check the checksum status.

The solution is applied after byte-level verification and the output then passes an independent check (unauthorised bytes, identity area, file size). If one of your selected operations cannot be applied or the output fails the check, the file is not delivered automatically and the credit is refunded. Results that cannot be verified are clearly labelled; still, keep a backup of your original file before flashing.

The file is not delivered and the credit is refunded. You are told which operation could not be applied.

No. If the analysis detects that an operation is already applied in your file, its card cannot be selected and the request is rejected without charging a credit. The same rule applies to operations that are partly applied or whose state cannot be determined.

If the analysis predicts that the solution will only partly fit your file, the operation card says 'partly applied' before you select it. This is a prediction; the outcome is stated in the delivery report.

No. The checksum is not corrected in the processed file, so the file is not ready to be written as it is. Before writing, correct the checksum in the PrimeChecksum tab, or write the file with your reading tool if it corrects the checksum while writing.

A module job costs 1 credit (any number of modules in one job); Stage 1 costs 2 credits for cars/bikes and 3 credits for trucks, tractors and construction machines. No credit is charged for a job without a result. A package is bought once and renewed every year with the annual licence. The pre-check is free.

Yes. With a free account you can upload your file and see your ECU identified and the operations that apply to your file without spending credits. Credits are used only when you start an operation, and refunded if it cannot be delivered.

A checksum is the control value an ECU uses to check the integrity of its software. When the data in the file changes, this value has to be updated too; if it is not, the ECU may reject the file and the vehicle may not run.

The checksum is not corrected automatically in the delivered file. Checksum correction happens inside the platform, in a separate tab: 1 credit, charged only when the result is ready. Some newer-generation ECUs (RSA-signed) need an external tool; the system detects this and warns you.

On modern signed ECUs (for example the MED17 / EDC17 / MG1 class) the checksum is not corrected by the system; an external tool or your own device is needed instead. The system detects the families it knows and warns you.

No. On an unrecognised ECU no checksum is written: no blind correction is made. In that case you need to verify the checksum with your own tool.

On some ECUs the checksum comparison needs the original (factory, unmodified) version of your modified file. The original must be the same size as the modified file; credit is charged only when the result is ready.

A checksum job costs 1 credit, charged only when the result is ready. If PrimeChecksum made no change to the file, no credit is charged.

It is the practice of changing map values in the software of a vehicle's engine control unit (ECU) to adjust the engine's power, torque and behaviour. ECU remapping and ECU tuning are other names for the same job.

Stage 1 is a software calibration for stock hardware. Stage 2 is prepared for vehicles with hardware upgrades such as an exhaust or intercooler.

Typical range by engine type — Turbo diesel: power +20–30%, torque +25–35%; Petrol (turbo engines): power +15–25%, torque +15–25%; Diesel (heavy-duty): power +15–25%, torque +20–30%. The horsepower figure depends on the vehicle's stock output. Gains vary by vehicle hardware and file; typical ranges are indicative.

Software that stays within the limits of the engine and drivetrain, is produced from the correct file and has been verified behaves predictably. The risk arises with the wrong file, an unverified change, a calibration beyond the limits or a vehicle with a mechanical problem.

It depends on the country and the intended use; complying with local law is the user's responsibility. The condition for operations on emission systems is stated in the note under the operations section.

Car, truck and bus, tractor, construction, marine and motorcycle ECUs. The supported ECU list is available on the site.

Turbo diesel: +20–30% power gain, +25–35% torque gain. Petrol (turbo engines): +15–25% power gain, +15–25% torque gain. Typical range; the exact figure depends on the vehicle's hardware and the file. Compatibility is measured at hex level when you upload it.

Diesel (heavy-duty): +15–25% power gain, +20–30% torque gain. Typical range; the exact figure depends on the vehicle's hardware and the file. Compatibility is measured at hex level when you upload it.

Diesel (heavy-duty): +15–25% power gain, +20–30% torque gain. Typical range; the exact figure depends on the vehicle's hardware and the file. Compatibility is measured at hex level when you upload it.

Turbo diesel: +20–30% power gain, +25–35% torque gain. Petrol (turbo engines): +15–25% power gain, +15–25% torque gain. Typical range; the exact figure depends on the vehicle's hardware and the file. Compatibility is measured at hex level when you upload it.

Petrol (turbo engines): +15–25% power gain, +15–25% torque gain. Typical range; the exact figure depends on the vehicle's hardware and the file. Compatibility is measured at hex level when you upload it.