Skip to content
View in the app

A better way to browse. Learn more.

Ultimate Subaru Message Board

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

OBDII scanner doesn't work

Featured Replies

I have a 2001 Subaru OBW. I'm trying to use a Harrison R&D scanner on it and I'm getting no response from the vehicle. It works on my 2003 Ford work van, and my son's 2001 Jeep Cherokee, but not the Subaru. Any ideas?

Hi. Not sure what to say. You have the key in 'run' right? It will not read otherwise in my experience, on a soob anyway. I've used a couple ODBII code readers on soobs and they work with key in 'run' (not 'acc') and even engine running if desired.

  • Author

As a reminder this is on a 2001 OBW, but I did remember that when I previously scanned the car , way back when, I had connected a pair of green wire connectors(called test mode connectors) under the dash, drivers side, next to the console as suggestsed in factory service manual.

 

When I connected the pair this time it didn't do anything with allowing the scan, but it did set off the check engine light flashing, the engine cooling fan cycling on /off and who knows what else.

 

Anyone out there had problems scanning their Subaru?

I use an Accutron (not sure of the model) on our 2002 OBW without any problems. The key does have to be turned to the "run" position, as someone else pointed out. The Accutron reads and resets the codes fine. No need for any jumpers.

You shouldn't have to couple the green test mode connectors to do an OBDII scan. Assuming the Harrison scanner incorporates the proper communication protocol, I'd check for a possibly blown fuse in the Subaru.

  • Author

I heard mention of the cigar lighter fuse being tied into the test port, is this the case? What does the green test mode connector do? Do any of the symptoms I mentioned when the test connetor was connected make any sense?

The scanner was ISO 9141 protocol, but had it updated to the KWP 2000 a while back , should that matter?

 

 

 

You shouldn't have to couple the green test mode connectors to do an OBDII scan. Assuming the Harrison scanner incorporates the proper communication protocol, I'd check for a possibly blown fuse in the Subaru.

Your scanner just might be incompatible with this car for some reason. Can you go to someplace like an Autozone where they read codes for free, and see if their scanner works on your car?

  • Author

I''try Auto Zone , but it work at one time, so I don't know if the protocol update makes a difference or not.

OB99W, any idea what fuse it might be?

[...]Do any of the symptoms I mentioned when the test connetor was connected make any sense?
Yes, that's typical behavior with the test mode connectors attached. Leave them disconnected.

 

 

The scanner was ISO 9141 protocol, but had it updated to the KWP 2000 a while back , should that matter?
I''try Auto Zone , but it work at one time, so I don't know if the protocol update makes a difference or not.
If the scanner was ISO-9141 compatible and working properly, adding KWP2000 compatibility shouldn't have changed things; if it did, I'd suggest asking Harrison R&D what's going on.

 

 

OB99W, any idea what fuse it might be?
Not offhand, but the DLC (Diagnostic Link Connector) definitely is fused, usually along with other things on the same circuit.
  • Author

I thank you both for your help, I will check for a blown fuse. Dan Harrison of Harrison R&D has assurred me that the addition of the new protocol would not effect it. I'll post to this message when I check the fuse, and if it is OK I'll return the scanner for a check up as he suggested. I have no idea how these scanners work but he figures the ISO 9141 protocol isn't functioning and the KWP 2000 is, hence the ability to scan my 2003 Ford work van, but not the 2001 Subaru. Does that make sense?

We recently acquired an OBD II scanner/logger and it would not work on my '05 Baja. Updated the firmware through the included utility and now it works fine. That was an Innova, IIRC.

[...]he figures the ISO 9141 protocol isn't functioning and the KWP 2000 is, hence the ability to scan my 2003 Ford work van, but not the 2001 Subaru. Does that make sense?
Yes, it's possible for only the ISO-9141 operation to be faulty.

 

You may have checked for this already, but make sure that none of the pins are bent and that the connector is being fully inserted; sometimes they're a bit tight and don't make good contact without a little "convincing". If you can easily get to the back of the DLC in the car, make sure all of it's pins are latched into the connector body.

 

Otherwise, if it's not something simple like a blown fuse or connector trouble on the Subaru, then it could be a problem with the ECU (but I wouldn't jump to that conclusion yet).

when you take the scanner in for it's check up, take the subaru as well. he should be able to scan your car and that will tell you if is the car or the tool.

  • Author

All the fuses under the dash and the hood proved to be fine, in addition I had a test scan done at a local Advance Auto, their scanner worked fine.

The scanner is in the mail back to the builder this AM.

  • 3 weeks later...
  • Author

I thought I'd update you on this, I returned the scanner for repair and it was at fault, its is now repaired and works fine, without any extra connecting under the dash as previously mentioned.

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.