Item 98614 OBD2 Scanner: Initial Setup and Vehicle Diagnostic Scan

Setting up the Item 98614 Obd2 scanner proved to be a straightforward process, especially for users running Vista Home Premium 64 bit. The software and driver installation completed without any hitches, establishing a reliable connection via COM5. Functionality checks, such as printing, were also successful right out of the box, indicating a smooth initial operation. The device specifications noted a burn date of 11/25/09, along with software version V2.10, hardware V1.50, and library version V2.60.

Upon connecting the item 98614 OBD2 scanner to the vehicle, the system promptly initiated diagnostic tests. The initial report displayed “Control Module $10 SAE J1850 VPW Vehicle Info. Not Supported Or Sto-red No Data.” This message suggests that while the scanner communicates with the vehicle, it might not fully support retrieving vehicle information using the SAE J1850 VPW protocol, possibly for certain parameters. Further examination revealed “Stored Codes No codes are stored in the module!” and “Pending Codes No pending codes are stored in the module!”, indicating a clean bill of health regarding stored and pending diagnostic trouble codes at the time of the scan. Similarly, “View Freeze Frame No Freeze Frame Data Stored!” confirmed that no snapshot of data was recorded due to any triggered fault codes.

The OBD2 scanner proceeded to perform an O2 Monitor Test on O2 Bank1 Sensor1, providing specific voltage threshold readings. These included “Rich-Lean Threshd(V) MOD : $10 MEAS: 0.345” and “Lean-Rich Threshd(V) MOD : $10 MEAS: 0.550”. Additionally, parameter values such as “$70 (Counts) MOD : $10 MEAS: 20”, “$71 (Values) MOD : $10 MEAS: 21”, and subsequent values up to “$87 (Values) MOD : $10 MEAS: 113” were reported, all associated with the “MOD : $10” identifier. However, the precise meaning of this “$10” designation within the context of the control module and these sensor readings remains unclear and warrants further investigation or community insights from experienced OBD2 users.

Further tests, specifically the On-Board Mon. Test, revealed a series of data points identified by IDs ranging from “04” to “72”, again frequently tagged with “MOD : $10”. These tests presented measurements (MEAS), alongside maximum (MAX) and minimum (MIN) expected values, and a status (STS) indicating either “OK” or “Fail”. Notably, Test $02 Data ID : 06, 50, 30, 40, and 11 returned a “Fail” status, suggesting potential issues within those specific on-board monitoring systems. Conversely, tests such as ID : 04, 66, 36, 60, 62, 72, and 21 reported “OK”. Interestingly, Test $05 Data and Test $0E Data were reported as “Not Supported Or Sto-red No Data,” indicating these particular test modes may not be applicable to the vehicle or are not supported by the item 98614 OBD2 scanner in this configuration. The user manual, unfortunately, is noted to be “pretty lame,” implying it offers limited assistance in deciphering these detailed diagnostic outputs.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *