A diagnostic tool may command a fan, valve, motor or relay during an actuator test. A successful response is useful, but it only proves what happened under those particular test conditions. It does not establish that every input and operating condition required for normal use is correct.
Describe what passed
Record the commanded function, the actual response and whether movement, current, pressure or another result was measured. Hearing a click is different from proving that the controlled mechanism performed its job. Keep any conditions or warnings displayed by the test routine.
Compare with ordinary operation
If a cooling fan runs on command but not when expected, diagnosis should consider the normal request, relevant sensor information and control strategy. If a motor works unloaded but stops in service, the real load and supply conditions matter.
For an AXION enquiry, include the garage’s test results alongside the customer complaint. Avoid running unfamiliar output tests without the manufacturer’s procedure: components can move or activate unexpectedly. Explain when the failure occurs and which measurements would distinguish a control problem from a load or mechanical problem.
Related help
- Pending and Confirmed Fault Codes: Keep the Status with the Number
- Permanent Fault Code Remains After Repair: What to Ask Next
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.