DNAEksper — ECU software analysis and inspection

DNAEksper reads the identity of an engine control unit (ECU) file from its contents, matches it with the factory (original) software in the library and compares them byte by byte. It reports changes to EGR, DPF, SCR, speed limiter, fault code suppression and injection/turbo maps in plain language.

The process is automatic and traceable. Every step from file intake to report delivery is recorded; the report can be sent back to the requesting system with an API key and signed webhook.

Capabilities

File intakeUpload, format detection and hash calculation.

Change detectionExtracting differences against a reference file.

Map analysisNaming changed regions by the affected system (EGR, DPF, turbo, injection…).

Consistency reviewWhen no matching original exists, it searches for tuner signatures, patches in erased areas and flattened tables; by default the result is shown only to staff.

Structured reportPDF report, time-limited customer share link and QR code; customer summary in plain language.

IntegrationExternal systems send files with an API key; the result is delivered by signed webhook, with retries on failed delivery.

Self-growing libraryA file that is byte-identical across independent vehicles is accepted as the factory original and pending analyses rerun automatically; files with tuning traces are not admitted.

VIN extraction and mismatch warningMake, model year and production region are read from the VIN; the report warns if the file appears to belong to another vehicle.

Report accuracy feedbackExperts mark each report as correct, partly correct or wrong; the dashboard tracks the accuracy rate for the last 90 days.

Library contributions and quarantineUsers can submit factory files they have; the file stays in quarantine until an expert approves it and is not used in comparisons.

Software number and date hintsSoftware number and date hints are read from library files and displayed, speeding up matching.

Pending jobsA file without an original becomes a pending job; when the original is uploaded, matching jobs complete automatically.

Limits of the analysis

We state up front what it shows and what it does not; the report should be read within these limits.

Supported files: Read files with .bin, .ori, .mod, .hex, .s19, .fls, .frf, .dat, .mpc, .bdm and .dump extensions, from 1 KB to 100 MB. Files are compared as raw bytes.
Recognized ECU families: Bosch EDC15/16/17, MED/MEV/MEG17, MD1C; Delphi DCM, DDCR; Magneti Marelli MJD, IAW; Siemens/Continental SID, SIMOS, PCR2.x; Kefico SIM2K. Whether a file can be analyzed depends on the library holding the original of that software.
When it says “uncertain”: If the file is not the full ECU, or the original it is compared with is partial or suspect, the result is marked “uncertain” or “insufficient reference”. For a file with no known original, the analysis waits until one is found.
Not a substitute for a mechanical inspection: It is a software comparison only. The vehicle's physical condition and hardware changes are out of scope; system names and interpretations are estimates and should be confirmed with a diagnostic tool.
How long files are kept: Uploaded files are deleted after 180 days; the report record stays in the account. A file with no matching original may be added to the reference library if it turns out byte-identical across at least three independent uploads.
AI and model training: The analysis is a rule-based comparison; no AI model is used and files are not used for model training.

Screenshots

DNAEksper — Analysis history — Analysis history

DNAEksper — Analysis details — Analysis details

DNAEksper — Reference library — Reference library

DNAEksper — Pending analyses — Pending analyses

Frequently asked

What does DNAEksper detect?

It compares the software file taken from the vehicle control unit with its original in the library, marks the changed regions by affected system and reports the findings in plain language.

How is the report delivered?

A shareable inspection report in a standard format is generated; if required, it's sent automatically to the requesting system via webhook.

When is it used?

Software appraisal in used-car sales, technical verification in insurance and assessment processes, detecting intervention history at service shops, and software history tracking for fleet vehicles.

Other products

What can DNAEksper do for you?

Let's plan the whole process together, from installation to integration.

Request a Call All Products