Two cars can look identical, use the same engine and even carry ECUs with the same part number on the label, yet need completely different tuning files. The reason is that an engine control unit has more than one identity. There is the hardware it was built on, the software it runs, the calibration data inside that software and the vehicle-specific data that ties it to one particular car. Understanding these layers is the first step of any professional ECU job, whether you work on cars, trucks, tractors or motorcycles. This article explains what each number means, where to find it and why it matters.

Hardware number: the physical unit
The hardware (HW) number identifies the electronic unit itself: the circuit board, processor, memory size, connector layout and output stages. It is printed on the housing label together with the ECU supplier’s part number and usually a serial or production code. Many suppliers use a fixed number format for their units, so an experienced technician can often tell the supplier and the family at a glance.
The hardware number tells you which tool protocol, read method and pinout are likely to work. It does not tell you what program and maps are currently inside the unit. One hardware version is normally used with many different software versions across engines, gearboxes, markets and model years.
Software number and version
The software (SW) number identifies the program and data set stored in the flash memory. Vehicle makers often use their own numbering on top of the supplier’s, so a single ECU may report a maker part number, a maker software version and a supplier software reference at the same time. These identifiers change when the dealer installs an update, for example to fix a driveability complaint, improve an emission strategy or add a new feature.
This is the number that matters most for tuning. A calibration file is built for one specific software. If a dealer update has changed the software since the car left the factory, the label still shows the old information while the ECU runs something newer. Maps may have moved to other addresses, changed size or gained new correction factors. A file made for the old software can then cause anything from warning lamps to a no-start.

Calibration ID and calibration verification number
For emissions-related ECUs on light vehicles, OBD-II service $09 (vehicle information) lets a generic scan tool request several identifiers directly from the control unit:
- VIN – the vehicle identification number stored in the ECU.
- Calibration ID (CALID) – a label identifying the calibration software currently installed.
- Calibration verification number (CVN) – a value the ECU calculates over its calibration area. If the data has been changed, the CVN no longer matches the value expected for that calibration ID.
- ECU name – a short identifier for the module (on vehicles that support it).
Inspection programmes and manufacturers can use CALID and CVN to check whether an ECU is running a known, approved calibration. For a technician, these values are a quick way to confirm which software is really present, without opening the unit. Heavy-duty engines use comparable identification messages over SAE J1939, and most motorcycle and agricultural ECUs can be identified through the maker’s own diagnostic services.
Vehicle-specific data: VIN, immobiliser and coding
Besides the program and maps, an ECU stores data that belongs to one particular vehicle. Depending on the design this sits in a separate EEPROM chip or in an emulated EEPROM area of the processor’s data flash. It typically includes:
- The VIN and sometimes mileage-related records.
- Immobiliser data that pairs the ECU with the car’s keys and immobiliser system.
- Variant coding: gearbox type, air conditioning, cruise control, cooling fan type and other equipment options.
- Learned values such as idle adaptations, throttle learn and injector quantity corrections, as described in our guide to adaptation values and relearn procedures.
This is why simply copying a file from one car into another ECU rarely works, and why a used ECU often needs VIN, immobiliser and coding work before the engine will start and run correctly.
Why the right identification matters for tuning
A tuning file is a modified version of one exact original read. The safest workflow is always to start from the vehicle’s own software, which is why file services ask for the original read rather than just the car model. When the hardware and software identifiers match, the person preparing the file can work on the correct map layout, and the result can be written back with confidence.
Typical mistakes we see include:
- Ordering a file by engine size and power only, without the software number.
- Using a file from a forum or another car with the same hardware but different software.
- Sending a read that has already been modified, while describing it as original.
- Reading only part of the memory, so the calibration area or the vehicle data is missing.
Where to find the numbers in practice
- The label: photograph it before the ECU goes back in the car. It gives supplier, part number and hardware number.
- The tuning tool: most OBD and bench tools display the identification block (hardware, software and calibration references) before reading. Save a screenshot or the ID log together with the file. The different read methods do not all show the same information, so note which one you used.
- A generic scan tool: service $09 shows VIN, CALID and CVN on most OBD-II compliant vehicles.
- A calibration editor: software such as WinOLS can show identification strings and compare a read against other versions of the same family.

Notes for trucks, tractors and motorcycles
Commercial vehicle and agricultural ECUs are often shared across many engine power ratings, with the rating selected by software or parameters. That makes accurate software identification even more important, because two engines with the same block and the same ECU hardware can have very different torque limits and protection settings. On motorcycles, the same ECU hardware is commonly used for several models and markets, with differences in ride modes, speed limits and emission settings held in software.
Related fault codes (DTCs)
When software, coding or vehicle data does not match the ECU, or a write did not complete, the following generic codes are among those that may be stored. Manufacturer-specific codes often add more detail.
| Code | Meaning | Typical causes |
|---|---|---|
| P0602 | Control module programming error | ECU not programmed or programming incomplete, interrupted or failed software update, software that does not match the hardware |
| P0610 | Control module vehicle options error | Variant coding missing or wrong after ECU replacement, used ECU from a different vehicle configuration, coding not matched to the car’s equipment |
| P0630 | VIN not programmed or incompatible – ECM/PCM | New or used ECU without the correct VIN, VIN not written after replacement, ECU from another vehicle |
| P062F | Internal control module EEPROM error | Corrupted or incomplete EEPROM data, data written from another ECU, internal ECU fault, supply voltage problems during writing |
| P0603 | Internal control module keep alive memory (KAM) error | Battery or permanent supply interrupted, poor ECU ground or supply, internal ECU fault |
| P0605 | Internal control module read only memory (ROM) error | Corrupted program or calibration memory, interrupted write, internal ECU fault |
| P0606 | Control module processor | Internal ECU fault, supply or ground problems, corrupted software |
| P0513 | Invalid SK key (immobiliser key) | Key not recognised, immobiliser data not matched to the ECU after replacement or EEPROM change |
| U0100 | Lost communication with ECM/PCM “A” | ECU not powered or not running (for example after a failed write), blown fuse, ground fault, CAN wiring fault |
Generic SAE meanings shown. Exact wording and additional codes vary by manufacturer, so check the service data for your vehicle.
Have an original ECU read with its hardware and software ID? Upload it to the tuning file service at ECUFileMarket and get a file built for your exact software version.