A coloured module in a scan tool’s network map is a visual summary, not a complete diagnosis. Read the legend and the detailed result behind that colour. Different tools may use red for a stored fault, no communication or another condition.
Open the underlying evidence
Save the controller’s full code report where accessible and the exact response if it is not. Record the vehicle selection and scan time. An incorrectly selected equipment variant can make an expected-versus-present comparison difficult to interpret.
Compare the map with the car
Identify which systems the vehicle actually has and which functions fail. Do not order a supposedly missing module before confirming that it should be fitted. A diagram can help organise an investigation, but the physical configuration and repair information remain essential.
Send AXION both the overview and detailed report. Include whether the vehicle was fully powered as required by the diagnostic procedure and whether any repairs preceded the scan. Ask the referring garage to distinguish confirmed non-communication from a controller that communicates but contains a fault. That distinction changes the next test and avoids unnecessary replacement decisions.
Related help
- Scan Tool Connects to the Engine but Not the Body Systems
- A Module Communicates Until Its Motor or Actuator Runs
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.
