Guide · Tool compatibility
Tool Compatibility: Files Read with Autotuner, Flex, KESS3 and Dimsport
EcuPrime runs in the browser and is independent of the reading tool: it looks at the file itself, not at the tool. You upload the original file you read from the ECU with Autotuner, Flex, KESS3 or Dimsport (New Genius / New Trasdata); when the job is done, you write the file with your own tool again.
Tools
Files from which tools can be uploaded?
The software is not a reading tool and does not connect to one: you upload, from the browser, the file your tool saved to your computer.
Autotuner
Manufacturer: Autotuner. You upload the original raw file read with this tool; the ECU is identified from the file itself.
Flex
Manufacturer: Magic Motorsport. You upload the original raw file read with this tool; the ECU is identified from the file itself.
KESS3
Manufacturer: Alientech. You upload the original raw file read with this tool; the ECU is identified from the file itself.
New Genius · New Trasdata
Manufacturer: Dimsport. You upload the original raw file read with this tool; the ECU is identified from the file itself.
A file read with a tool that is not listed follows the same rule: if it is an open (unencrypted) raw file, it can be uploaded.
These names are trademarks of independent manufacturers and are mentioned only to indicate compatibility; EcuPrime is not their dealer, representative or partner.
File
Which file do I upload?
The original raw file
Upload the original, unmodified file you read from the ECU (.bin or a similar raw file). The ECU is identified from the file itself; when it is, you do not need to pick a make or model.
ZIP, Intel HEX and S-record
ZIP and GZIP archives and Intel HEX and Motorola S-record files are opened automatically and converted to a raw file. If a ZIP holds several files, the largest one is taken. RAR and 7z are not opened: extract the archive first.
Full read and partial read
A full read contains the whole ECU memory. A partial read (calibration area only) is one part of the file; because identification data may be missing, 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.
Encrypted slave package
An encrypted package produced by a slave tool cannot be processed: the file inside is encrypted. When the software recognises such a package, it tells you why. Upload the decrypted (open) read; if you use a slave tool, your master provides the decrypted file.
Flow
From reading to writing in four steps
Read with your tool
Read the ECU with your own tool and keep the original file: it is your backup.
Upload to the software
Upload the file from the browser. The ECU is identified from the file and only the operations that apply to your file are enabled; this pre-check is free.
Choose the operation, download your file
The solution is verified at byte level as it is applied; if one of your selected operations cannot be applied, the file is not delivered and the credit is refunded.
Check the checksum, write with your tool
The checksum is not corrected automatically in the delivered file; before writing, look at the Checksum tab of the software. You write the file to the vehicle with your own tool: the software does not write to the vehicle.
PrimeChecksum
The checksum before writing
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.
Checksum correction: when it is done and when you need an external tool →
What should good chiptuning software do?
Six criteria — correct file identification, refusing unfit files, credit refunds, honest checksum status, range of operations and support — and what EcuPrime does on each.
Want to edit the file yourself?
EcuPrime Studio runs in the browser: edit maps in Hex, Table, 2D and 3D view, list ORI/MOD differences and save versions.
Help
Frequently asked questions
Files from which reading tools work?
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.
Which file formats can be uploaded?
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.
Can I upload a partial (calibration-only) read?
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.
I use a slave tool; why is my file not processed?
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.
How do I write the processed file to the vehicle?
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.
Is the checksum done automatically?
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.
Start today
A free account for dealers and tuning pros: upload your file, see which operations work, apply your solution.
Create free account