A successful coding message means the requested operation completed according to the tool; it does not prove that the entire feature is correctly installed or functional. Record the original complaint, replacement parts and the exact operation performed.
Separate configuration from function
The vehicle may also need the correct hardware, wiring, supported software and application-specific setup. Do not keep changing unrelated coding values to search for a working combination. Preserve the original configuration and any documented changes so the work remains traceable.
What should be checked next?
Ask the technician to compare the installed equipment with the intended specification and read the resulting faults. Include whether the feature responds at all and which prerequisites the diagnostic procedure identifies. A missing physical input cannot be established or corrected solely from a coding success screen.
For AXION, provide both the before-and-after reports and the replacement part numbers. State whether the work restores an original feature or adds equipment that was not fitted. These are different compatibility questions. The supported assessment should define the remaining checks rather than promise that another coding session will necessarily complete the job.
Related help
- Same ECU Part Number: Is a Used Replacement Automatically Compatible?
- ECU Software Number and Hardware Number: Why Both Matter
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.