New? Start here. There are 569 Volvo forum users online now. See the forum's active topics. Say hi contact Matthew.
MVS-Amazon link helps MVS!

Bluetooth OBDII Connect To ECU

bluetooth-connect-to-ecu.jpg

MVS Forums contributor ESL explains how to connect to your Volvo’s ECU via Bluetooth adaptors:

Torque uses the standard OBDII emission diagnostics.

If you can’t connect with Torque, the first thing I’d try to do with Torque is find a way to force it to use the ISO 9141-2 protocol. If you can somehow monitor the Torque’s communication exchange with the bluetooth scanner, you should see the Torque software sending an “ATSP 3” command to the bluetooth scanner. Forcing the bluetooth device (via the ATSP 3) to only use ISO 9141-2 when attempting to connect to your ’97 850 will eliminate timing issues that are introduced when another protocol is unsuccessfully attempted to connect before ISO 9141-2 is attempted to connect.

RE: 1997 850 BLUETOOTH OBD2 DOESNT CONNECT TO THE ECU
Quote
Post by E Showell » Mon Dec 22, 2014 7:27 pm
Sometimes the Chinese knock-off ELM 327 bluetooths require a password — usually 1234 or the like. On occasion, you need to try the mating a few times in a row before it takes. See if that works and report back.


’98 V70 NA FWD 5 spd, silver sand metallic (sold)
’99 V70 NA FWD Auto, dark blue (actively for sale)
’99 S70 NA FWD Auto, black (sold and resurrected — Don’t cry for me Argentina . . . )
’07 S80 3.2 FWD Auto, Barents Blue Metallic
’06 V70 R AWD Auto, Sonic Blue Metallic
’04 XC70 Ruby Red Metallic
’95 855 auto (sold)
’86 245 manual (sold)
Top


RE: 1997 850 BLUETOOTH OBD2 DOESNT CONNECT TO THE ECU
Quote
Post by tzanis » Mon Dec 22, 2014 7:36 pm
Well, I used 1234 and got connected the first time, I am just wondering if there are any settings i could change or else. I will check again though, I dont think that I ll get any results though.

RE: 1997 850 BLUETOOTH OBD2 DOESNT CONNECT TO THE ECU

Post by esl_97_850_T5 » Wed Dec 24, 2014 9:38 pmThe most common initial problem (at least on Windows systems) is to:

a) not have the port # specified correctly, or
b) not have the port speed specified correctly.

If you’re getting responses from the bluetooth adapter when you type ATZ, ATL1, ATH1, and other AT commands, then you’ve probably got those 2 potential problems solved.

So what speed are you using?

Another occasional problem is:

c) not seating the bluetooth adapter, USB cable, serial cable, etc. firmly enough into the car’s OBDII port.

What software are you using to connect your Android phone to the car’s OBDII port?

Does your software provide any ability to log the commands/requests that are being sent to the car’s OBDII port and the ELM327’s responses? Maybe in some sort of Advanced or Experienced users menu?

Are you simply trying to read the OBDII emission diagnostic codes, if any?

Or have you tried the KWPD3B0 setup and requests for communicating with the COMBI, SRS, ABS, etc.?

Have you tried the Android based ELM 327 Terminal app to explicitly issue the following?

ATZ
ATL1
ATH1
ATPPS
0100

1997 850 Bluetooth obd2 doesnt connect to the ECU