My check engine light is on. I just got back from O'Reilly's and Autozone. Both scanned for error codes with a standard OBD2 device. At O'Relily's one "No DTC definition found" came up and at Autozone it looked like the reader was not communicating with the car's system. I'm not sure either guy knew what he was doing. Do I need a Volvo-specific reader?

 

What year is your vehicle?

 

The car is a 1998 V90.

 

1996+ is when Volvo went to OBD2 so pretty much any scanner will work. The big question is whether you want to simply scan the power train codes (ie the Pxxxx codes that set the check engine light) or if you want to also scan ABS and SRS codes. The chassis codes require an upgraded scanner - typically in the $100+ range and the SRS codes may put you up around $200 for the device. Are you seeing the check engine light or the service interval (service required...) light? The latter is separate from the OBD2.

 

I have seen Volvo cars display a check engine light and yet no code is in the system. Then, attach another scan tool and there the code is. Go figure.

I have a Blue Driver app on my phone and bought the bluetooth connector. It seems to find codes that the Snap On scanner cannot.

https://www.bluedriver.com/

The app is free but you have to buy the connector to make it work. $100

 

I wonder if its related to the code set mappings in the device. There are some code readers that have Volvo specific data (ie the iCarsoft i906 but as Tony noted, the newer PC apps like Bluedriver and TOAD have the advantage of being able to make a more versatile app that works with more of the ECU data beyond just the OBD codes. The $100 is competitive to the cost of a middle size scanner (I went with the $39 version LOL) and give the user the option to upgrade the app for more features/packages.

 

It's the Check Engine light. The SRS light is also on but it goes off after about 30 minutes of freeway driving.

 

I think that you are going to have to try another scan tool. I know that the Blue Driver that I mentioned above takes pending codes and crosswalks them to their OBDII equivalent.