Early 2000s Matco scanners may not have the advanced functionality of modern OBD2 adapters. While they likely support the J1850 protocol common in GM vehicles of that era, they might encounter communication issues due to incorrect protocol selection. For instance, some GM vehicles, like the 2000 Malibu, are listed as using a non-existent “VPN” protocol, adding to the complexity.
Confirming the wiring configuration of the OBD2 ports in both the vehicle and the scanner can help identify potential connection problems. The SAE J1978 specification outlines a specific order for scanning protocols that scan tools should follow. Most OBD2 scanners and apps initiate communication by requesting supported Parameter IDs (PIDs). If no response is received from the vehicle’s Engine Control Module (ECM) or Powertrain Control Module (PCM), the scanner moves on to the next protocol.
If a Matco scanner from the early 2000s progresses beyond the J1850 protocol without establishing communication, it suggests a lack of response from the vehicle. This could be due to several factors, including an incorrect protocol setting on the scanner, wiring issues, or a faulty ECM/PCM. While these older scanners might not function as a versatile OBD2 adapter for modern vehicles, they should still be capable of diagnosing basic issues on compatible vehicles using the J1850 protocol.
Ensuring proper protocol selection and verifying the integrity of the OBD2 connection are crucial steps in troubleshooting communication problems. If issues persist, consulting the scanner’s manual or contacting Matco directly may provide further assistance.
