As a seasoned auto repair content creator for carw.store, I recently got my hands on a Blue-Point Microscan III car scanner to put it through its paces. My initial focus was on understanding its live data capabilities and overall user experience, especially compared to older scanners I’ve used. This review is based on my hands-on experience, aiming to provide insights into its performance and usability for fellow automotive enthusiasts and professionals.
My first interaction involved navigating the installation instructions, which seemed geared towards the broader Microscan series rather than specifically the Microscan III. However, my primary concern quickly shifted to its performance in live data mode. I observed that loading live data was noticeably slow. During an attempt to customize the data display, the scanner became unresponsive, freezing on the touchscreen. On a couple of occasions, I even had to physically disconnect and reconnect the OBD2 connector to regain functionality, which was a bit concerning.
Exploring the live data functions, I found options for custom display screens, which is a useful feature. However, I was surprised to find no readily apparent way to save customized live data selections. By default, it appears all available live data PIDs (Parameter IDs) are selected, potentially contributing to the sluggishness I experienced.
To get a clearer picture, I connected the Blue-Point Microscan III again for more focused observation. I aimed to better understand the scanner’s behavior and familiarize myself with the icon-based menu system it employs, a departure from traditional written menu items. Modern scanners often boast vehicle-specific configurations that are automatically detected. However, with the Microscan III, the initial setup seemed minimal, mainly prompting for a manufacturer selection like Jeep – Chrysler – ?????. This led me to believe that the scanner might not be actively storing detailed vehicle information such as make, model, or engine. It seems to primarily focus on reading and displaying generic OBD2 data PIDs.
This contrasts with my experience using an older MT2500 scanner on a 1998 Jeep. The MT2500 offered more in-depth vehicle-specific selections, including VIN number type, vehicle make, model, and engine. This raises a question: Does the Microscan III rely on VIN reading for more detailed vehicle diagnostics, or does it operate on a more universal OBD2 data approach? My 1998 Jeep, unfortunately, lacks many advanced “Info” functions, including VIN reading capabilities, which might limit the Microscan III’s potential on older vehicles. Furthermore, I didn’t find any specific test functions for components like O2 sensors on this older Jeep, unlike some previous scanners like my Innova, which offered Mode 6 functions for non-continuous test results.
Initially, the protocol selection on the Microscan III was set to “Auto.” During my subsequent test, I manually switched the protocol to ISO 9141, which is the standard I believe is appropriate for Chrysler/Jeep vehicles of that era. Understanding OBD2 protocols is crucial for effective diagnostics. For reference, here’s a breakdown of common OBD2 protocols and their vehicle applications:
- ISO 9141-1 & 9141-2: Commonly used in Chrysler vehicles, as well as European and Asian models.
- ISO 15765-4 CAN (SAE J2480): Prevalent in a wide range of vehicles, especially those not legally mandated to strictly adhere to the OBD2 standard.
- ISO14230-4 (KWP2000): Often found in Asian car makes.
- SAE J1850 PWM: Used by Ford.
- SAE J1850 VPW: Used by GM.
Adding to the complexity, there are actually two different physical types of OBD2 1962 connectors, Type A and Type B.
alt: Type A OBD2 connector diagram highlighting pin positions for various protocols.
alt: Type B OBD2 connector diagram illustrating different pin assignments compared to Type A.
Identifying the protocol a vehicle uses can often be done by examining the pin configuration of its OBD2 connector. Vehicles manufactured after 2008 typically have more sophisticated computer systems relying on the CAN protocol, and their OBD2 connectors will usually have pins 4, 5, 6, 15, and 16 populated. Older vehicles may exhibit more variation in pin usage depending on the protocol employed.
Here’s a quick guide to the OBD2 connector pin assignments:
TOP Row:
- Pin 1: Reserved for OEM communication.
- Pin 2: J1850 Bus+ location.
- Pin 3: OEM Reserved.
- Pin 4: Chassis ground.
- Pin 5: Sensor signal ground.
- Pin 6: CAN High (J-2284), common in modern cars (2008+) with pins 4, 5, 6, 15, and 16.
- Pin 7: ISO 9141-2 K-line.
- Pin 8: OEM Reserved.
BOTTOM Row:
- Pin 9: OEM COMM.
- Pin 10: J1850 Bus- (negative).
- Pins 11, 12, 13, 14: OEM Reserved.
- Pin 15: ISO 9141-2 L-line, positioned below the K-line.
- Pin 16: Unswitched Battery Power, supplying power to the scan tool.
Further testing and exploration are needed to fully evaluate the Blue-Point Microscan III, particularly in terms of its live data performance and vehicle-specific diagnostic capabilities on a wider range of vehicles. Understanding OBD2 protocols and connector types remains essential for anyone working with car diagnostic tools.
