I am interested in getting this feature for my '97 850 GLT. No other device setup combines the diagnostics, roadside assistance and GPS. I am already a VzW customer, so the additional cost is minimal, running off my existing data plan.

Verizon Hum is supposed to be eligible for any vehicle from 1996 onward that has the standard OBD port. But when I checked for my Volvo, the auto-answer function on Verizon's website said it was not compatible. So I selected another model from the pull-down menu, the 960, and it said that it was.

Of course, the vehicles are different, but what would be different about the OBD interface on the two vehicles made by the same manufacturer the same year be different enough to disqualify my 850?

I tried asking Verizon employees, and they know nothing. They're only looking at a chart or plugging in the info into a database, but cannot tell me why.

 

Call Hum directly at 800.906.2501. Verizon is a reseller of the tech only. I went on hum.com and it correctly told me where the OBD2 port is for the 850. The only nuance is that these tools will be ok for the generic codes but may not properly interpret the vehicle proprietary ones. Considering your car has the Motronics 4.4 ECU, you can also look up the 98 C70 and V70/S70 (turbo models) for compatibility.

 

96 is when they switched from OBD to OBDII. That's why Verizon says 96 and newer. I can't get my shop scanner to communicate with my 96 850 computers but do get straight OBDII data. When I checked the database it said to use a Volvo scan tool and select "850 language."

I'm guessing "850 language" is different and that's why it doesn't work.

 

I don't think there's a different language for 97 850s' OBD2 versus other Volvo models. But assuming the Hum is just using a generic OBD2 reader design, Wal Ford can do a self test with a generic OBD2 reader (say by pulling a vacuum line to set off the CEL). Maybe other posters can comment if they have had good results using a generic OBD2 code reader on their 96/97 850s...

 

Thanks for the further info. I checked the Hum website and tried compatibility for the '98 C70, V70 & S70. Only the V70 was said to be compatible.

I called the number you provided and was unable to get to talk to anyone who knew anything but how to answer the phone. I asked that person to see if I could talk to anyone knowledgeable, and the operator passed along that there was some sort of "computer error" on that particular model. I never did get to talk to anyone knowledgeable directly.

I did some research based upon my VIN and found that my engine code is B5254T.

That engine was available on the '98 V70, so I cannot understand why that one would work and mine will not.

I was advised by Hum that they simply will not work with me on this and should therefore return the device.

 

The next question would be, which OBDII OBD2 Diagnostic Scanner would be optimal for the 850 GLT -- assuming there is a different scanning device that would work for the larger turbo and normally aspirated models.

 

I did a bunch of research on this because I want access the computers in my car. I found a ton of info that very little was understandable to me. Further and further I went down into the depths of the interwebs I went. Rather than bore you with the details I'll try to sum up my observations. Keep in mind I was looking at '96 (what I have) rather than '97 but it's mostly relevant to you.

1) the 850 had obd2 as early as '93, before the mandate in '96 and those cars had both obd1 and 2.

2) none of the articles I read mentioned the 960

3)850's do have a proprietary code for interfacing system computers (ECU, ABS, ect) but are also generic obd2 (ISO 9141-2) compliant. (This explains why my shop scan tool can only interface with the obd2 and not the ECU directly)
I can read and clear CEL codes but I cannot reset the maintenance light...

4)Volvo used KWPD3B0 (KeyWord Protocol D3B0) in 850's (including early 70 series) until ISO 14230 KWP2000 was mandated.

5)specifics on Hum and how it works are hard to find on the interwebs.

6) (in response to your post whilst I was writing this) generic OBD2 scanners should interface with the 850 on the ODB2 side but won't be able to "talk" directly to the system computers. So reading/clearing codes and live stream OBD2 data only.

7) you can buy an OBD2 cable that connects to a laptop to access system computers, according to some guy on the interwebs.


If anyone wants specifics posted I can add links or you can google stuff I mentioned.