A scanner lighting up from the diagnostic socket proves only that it received enough power to operate in that moment. It does not prove that every required communication path, vehicle state or tool function is available.
Separate tool and vehicle observations
Record the tool model, selected vehicle and exact connection message. State whether another supported tool has communicated successfully and whether any modules remain accessible. Include recent battery, accessory or diagnostic-socket work.
Do not bridge socket terminals or use an assumed pinout from a different vehicle. A technician should consult the correct information and distinguish supply, interface compatibility and network faults. If the engine starts normally but diagnosis is unavailable, report that distinction. If the vehicle is also immobilised, preserve its warning messages. A connection failure is not sufficient evidence to order an engine ECU, gateway or replacement diagnostic socket without further tests.
Related help
- Scanner Reads Generic Engine Codes but Misses Manufacturer Functions
- Vehicle Network Fault Appears When a Trailer Is Connected
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.