Connecting the AutoTap OBD II For Windows to your vehicle is a straightforward process, beginning with the hardware setup. The AutoTap Scanner hardware clearly labels the “Vehicle” and “Computer” ends, simplifying the initial connection. The OBD II cable is connected to the “Vehicle” port on the AutoTap Scanner, while the serial cable links to the “Computer” port.
For laptops equipped with a DB9 serial port, the serial cable connects directly. However, for newer laptops lacking this port, AutoTap offers USB adapters, ensuring compatibility across various devices. Serial extension cables are also available as accessories for added convenience. These accessories can be explored further on the AutoTap accessory products page.
The final step in the physical connection is linking the OBD II cable to the DLC (Diagnostic Link Connector) in your vehicle. Once connected, the red LED indicator on the AutoTap OBD II hardware should illuminate, confirming that it’s receiving power from the vehicle.
Understanding new automotive diagnostic equipment can initially feel overwhelming. To make the Autotap Obd2 Streamer system more approachable, we’ll explore its functionality through a practical, real-world example. This hands-on approach aims to build your confidence and demonstrate the user-friendliness of the system right from the start. Many car owners invest in diagnostic tools that end up unused due to a lack of clear initial guidance. However, the AutoTap system is designed with user experience in mind, featuring a readily accessible Help function to address any questions that may arise during use.
Let’s delve into a simple diagnostic scenario to illustrate the AutoTap OBD2 streamer in action.
Our first diagnostic test involves a 2001 Oldsmobile Alero with a 2.4L engine. This is a firsthand account of a situation encountered by my daughter. One evening, her car, with only 15,000 miles, refused to start after work. The only sound was a “click, click, click,” indicating a potential battery issue. Around midnight, I went to investigate the problem. After some basic checks, it became clear that the car battery had failed. Fortunately, the dealership where she purchased the car was nearby. Once jump-started, we took the car to the dealer. The next morning, a call from the dealer confirmed my diagnosis, and the battery was replaced.
However, the story didn’t end there. Shortly after picking up her car, my daughter called again, this time reporting that the “Service Engine Soon” and “Trac Off” lights were now illuminated. Being an OBD II compliant vehicle, diagnosing the issue without a compatible scan tool was impossible. It’s worth noting that while I own a professional-grade scan tool, its 2001 update wasn’t yet available, rendering it ineffective for this particular vehicle. This highlighted a crucial advantage of the AutoTap system: its up-to-date compatibility. As you’ll see, the AutoTap OBD2 streamer quickly identified the problem.
Upon bringing the car home, I connected the AutoTap OBD2 streamer to the vehicle’s DLC connector.
With a few mouse clicks, the AutoTap software was up and running. First, I selected the AutoTap icon on the desktop and then clicked the “Connect to a Vehicle” button.
At this point, an important detail emerged. My laptop also uses a Palm handheld device, which synchronizes via the DB9 serial port. The Palm HotSync manager, which automatically loads on startup, was interfering with the AutoTap system. The “Unable To Communicate With Vehicle” error message appeared because the HotSync manager was occupying the serial port needed for the AutoTap connection. The solution was simple: by double-clicking the Palm HotSync icon in the system tray (near the clock) and confirming “Yes” to exit the HotSync Manager, the serial port became available for the AutoTap OBD2 streamer. This highlights the importance of ensuring that the communication port required by AutoTap is free and accessible before initiating a diagnostic session.
Focusing initially on retrieving the Diagnostic Trouble Codes (DTCs) that triggered the “Service Engine Soon” light, the AutoTap software displayed a DTC code chart. Looking at the bottom of the AutoTap screen, above the Windows start button, the vehicle’s VIN was visible, the connection status indicated “YES,” and the MIL (Malfunction Indicator Lamp) status showed “ON.” Within approximately 10 minutes, I had connected to the vehicle, resolved the communication port conflict caused by the Palm HotSync manager, and identified a single DTC: “IAT circuit high.” This DTC pointed to the Intake Air Temperature sensor circuit, with “high” suggesting an open circuit. It was time to inspect under the hood.
Upon inspection, the new AC Delco battery and the IAC sensor were visible. And there it was – the IAC sensor connector was unplugged. Reconnecting the sensor harness was a straightforward fix. While not all diagnostic issues are this easily resolved, this example underscores the efficiency of the AutoTap OBD2 streamer in quickly pinpointing problems.
Before concluding, it’s worth noting some of the advanced features available within the AutoTap software. In the DTC window, the “Advanced” function button leads to a window offering further control. Here, you can customize DTC options, enabling or disabling DTC checking and MIL status monitoring. You can also set the interval for automatic checks when these functions are enabled, ensuring you receive real-time updates on DTC and MIL status. This level of customization enhances the AutoTap OBD2 streamer’s utility, allowing users to tailor the diagnostic process to their specific needs.
