A basic-setting or adaptation routine may refuse to begin when its required conditions are not met. Keep the exact refusal message rather than describing every unsuccessful attempt as a failed module. The vehicle-specific procedure determines the prerequisites.
Record the routine and conditions
Include the controller, tool version, selected routine and any values or states the procedure requires. Note whether the tool refused immediately or started and then aborted. Those two outcomes can lead to different diagnostic questions.
Do not force the procedure
Do not invent substitute values, bypass interlocks or use a similar model’s routine to get past an error. If the correct procedure cannot be completed, the reason needs investigation. Mechanical condition, existing faults and configuration may all be relevant depending on the application.
Send AXION the failed routine log and the work that preceded it. State whether parts were replaced and whether the original configuration was preserved. Agree whether the enquiry needs vehicle-level diagnosis rather than a removed-controller repair. A successful adaptation should be followed by the appropriate functional checks; completion of the routine alone is not a complete assessment of the underlying repair.
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.