Two numbers on a controller report can describe different things. Hardware identification concerns the physical platform or version; software identification concerns the installed program or calibration. The exact naming scheme varies by manufacturer, so retain the labels shown by the diagnostic tool.
Send the complete identification screen
A cropped photograph containing only the largest number can omit the detail needed for compatibility assessment. Include the casing label and readable scan identification where available. Keep the vehicle model, engine and transmission information alongside them rather than in a separate unexplained message.
Do not infer interchangeability from appearance
Matching connectors and a similar housing do not settle software compatibility. Nor does a different software number automatically prove the unit is wrong: supported updates and variants must be checked against the correct application. The assessment needs the full context.
For AXION, state whether the request concerns a fault in the original unit, a software update or a donor already purchased. Preserve original files and logs if programming has been attempted. Agree the supported operation before writing data. A clear identification record helps prevent a parts enquiry from turning into an avoidable recovery job.
Related help
- Same ECU Part Number: Is a Used Replacement Automatically Compatible?
- Interrupted ECU Update: What to Preserve Before Trying Again
Browse all fault guides or use the vehicle module finder to prepare your enquiry. Include the vehicle, symptoms, complete fault codes and any previous test results. Assessment scope and compatibility must be confirmed before booking or sending a unit.