EcuInside
Menu

What’s inside this ECU?

Check a car

.bin, .ori, .hex, .s19, or a .zip with one file inside. Up to 32 MB.

Drop in a file read from a car’s engine computer. We find its part numbers and software, and show you the bytes each one came from. Free, and the file isn’t kept.

Every number comes with its bytes

The numbers on an ECU’s label are also written inside its memory. We find them there and mark the exact bytes, so you can check them yourself in any hex editor.

01C00045 44 43 31 37 43 34 36EDC17C46
01C01090 C7 1B 03 02 28 37 D4.....(7.
01C01852 30 25 B3 62 CB FE AER0%.b...
Variant EDC17C46, found at 0x01C000
01C08031 30 33 37 35 32 33 3810375238
01C08834 35 00 00 00 00 D8 C245......
01C090B0 57 2D 9F 6C 21 78 8F.W-.l!x.
01C09814 26 B5 9F B1 41 7F 1B.&...A..
Software number 1037523845, found at 0x01C080
01C10030 32 38 31 30 31 36 3202810162
01C10834 34 00 00 00 00 BC AB44......
01C110B2 E6 1A 43 9B 5F 3E A2...C._>.
01C118AB 0D 4C 68 75 8F 1E EC..Lhu...
Hardware number 0281016244, found at 0x01C100

How sure we are, in words, for the example above:

Sure about this. Five things agree: the family's own markers are present; the software number has the normal Bosch shape; a Bosch hardware number was found: 0 281 016 244; the variant name EDC17C46 is written in the file; a carmaker part number was found: 03L 906 022 LB.

Looks like a full read: 2 MB, a normal size for a whole EDC17 read. About 25 % of the file is blank (0xFF or 0x00), which is normal for some layouts and a sign of an incomplete read in others.

Then open the tables inside

Every result lists the tables we can find by their shape, each with its axes and values, as a grid or a 3D surface, plus a map of the whole file and its hex. It’s all drawn in your browser from your own copy.

Have the original read and a changed one? Compare the two: you see which tables changed, by how much, and every other byte that differs.

Example with made-up values: a 16 × 16 table, engine speed (rpm) by load (%). Drag to turn it.

No file? Check if the car is tuned

Find out whether a car was tuned, remapped or chipped before you buy it. Plug an OBD adapter into the car and we compare the fingerprint of its engine software with other cars running the same software. It only reads. Nothing in the car is changed. Cars built for the US since 2005 have to report this fingerprint; cars built for other markets may not.

  1. 1Plug a Bluetooth or USB OBD adapter into the port under the dashboard.
  2. 2Turn the ignition on. The engine can stay off.
  3. 3Open the check and connect. It takes about a minute.

Engine module

Software ID DEMOCAL-ECM-0412

This car’s fingerprint
A7F0193C
What 14 of 15 other cars on this software report
5C3A91E7

Signs of changed engine software

Same software ID, different fingerprint: this car isn’t running the program the other 14 cars run.

Example with made-up numbers from a demo car.

ECUs we know

38 families from 6 makers today, mostly from the 1990s to now. A file we can’t name still gets the size check, the file map and the tables.

Every family, with the file sizes we expect

Bosch
19 families
Siemens
8 families
Delphi
2 families
Marelli
4 families
Denso
4 families
Hitachi
1 family

What happens to your file

Your browser sends it to our server, which reads it in memory, finds the numbers and the tables, and sends the result back. Then the file is gone: we don’t keep it, open it again or pass it on. We keep what we found (the family and the numbers), never the file, its name or a VIN. The details.