A controller that responds at rest but disappears when an output operates presents a useful event to capture. Record the requested function and whether communication returns automatically. This is different from a controller that never responds at all.
Keep the event synchronised
The most useful garage evidence links the control request, supply behaviour and communication loss in time. A voltage reading taken several minutes later may miss the condition. Ask for recorded measurements and the exact operating state, using the vehicle’s approved test procedure.
Do not assume an internal processor failure
The controller, its power connections and the connected load all belong in the investigation. The symptom alone cannot establish which is responsible. Repeatedly commanding an abnormal load may cause further damage, so testing should be planned by the technician rather than performed as repeated owner trials.
For AXION, provide the controller identity, function involved and any previous repairs. Explain whether the complete vehicle is available. A removed-unit assessment may answer some questions, but the installed wiring and load can be essential to reproducing this particular fault. Agree the evidence required before dispatching the controller.
Related help
- Scan Tool Connects to the Engine but Not the Body Systems
- Network Fault Appears After an Aftermarket Accessory Is Fitted
Browse all fault guides or use the vehicle module finder to prepare your enquiry. Send your vehicle details, what has gone wrong and any scan or test results. Contact us before booking or posting a module so we can check whether we can help.