Automatic map detection, step by step
1. Upload the ORI file
Start from the original ECU read. Map Decoder detects the ECU family and fingerprint.
2. Maps are detected
The relevant calibration tables are located and labelled automatically — no manual searching.
3. Generate the MapPack
Apply validated modifications and produce a checksum-corrected, ready-to-flash MapPack.
Why automatic detection matters
Traditional hex editor
You manually search the binary, cross-reference addresses, and risk missing a map or breaking the checksum.
Map Decoder
Maps are recognised automatically, modifications are validated, and checksums are corrected for you.
Supported families
EDC16, EDC17, MD1, MG1, SID, DCM, MED, PCR, MEVD across Bosch, Continental, Delphi, Siemens, Denso and Valeo.
ECU map decoder — frequently asked questions
What is an ECU map decoder?
An ECU map decoder is a tool that locates and identifies the calibration tables (maps) inside an ECU binary — fuel, boost, torque limiters, emission strategies and more. Map Decoder does this automatically through map recognition.
Can Map Decoder detect maps automatically?
Yes. Map Decoder automatically detects and labels the relevant maps inside the file, so you do not have to find each table manually as you would in a traditional hex editor.
Which ECUs and families are supported?
Bosch, Continental, Delphi, Siemens, Denso and Valeo, across families including EDC16, EDC17, MD1, MG1, SID, DCM, MED, PCR and MEVD.
Do I need a DAMOS or A2L file?
Not necessarily. Map Decoder detects maps automatically; a DAMOS or A2L, when available, can make identification more precise but is not required to start.
Decode your first file
Request a demo and see automatic map detection in action.