1997 850 Bluetooth obd2 doesnt connect to the ECU

tzanis · Post by **tzanis** » 22 Dec 2014, 18:56

So, I just received a bluetooth obd2 adapter, which I connected to my android phone. It doesnt connect to the ecu. Has anybody experienced the same? I will attach a picture of what is the info I am given. It connects to the adapter, and the adapter lights work.

Also, another one I bought around summer didnt work as well, and I gave it to my friend. But when I first ly bought the car, it had a check engine light, which I deleted and fixed the issues through a usb obd2 and laptop. I had a cable obd2 around and long ago in the summer I tried but still didnt connect to my laptop.

I am putting the pic here, and I will wait for any responses.

Thanks

tzanis · Post by **tzanis** » 22 Dec 2014, 18:59

Also bonus pic from today

Post by **E Showell** » 22 Dec 2014, 19:27

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.

tzanis · Post by **tzanis** » 22 Dec 2014, 19:36

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.

tzanis · Post by **tzanis** » 23 Dec 2014, 22:22

so I ve been looking on the internet and found this video

and based on the comments there is a timing problem on the cheap ones :/

not sure what to do (maybe get a newer car

)

Post by **esl_97_850_T5** » 24 Dec 2014, 21:38

The 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

Do you have a factory Motronic 4.3 or a factory Motronic 4.4? Or some kind of modification or enhancment to either of them?

Have you recently verified that your car's OBDII port is OK? To be specific, are pins 5, 7, and 16 indeed working correctly in your car's OBDII port to allow OBDII emission diagnostics connections or KWPD3B0 protocol connections? The reason I ask is your statement "...it had a check engine light, which I deleted and fixed the issues through a usb obd2 and laptop. I had a cable obd2 around and long ago in the summer I tried but still didnt connect to my laptop..." seems to say that your were both a) successful at using a USB OBD2 cable with a laptop, and b) "still" unsuccessful at using an OBD2 cable. I'm confused?!?! and uncertain if pins 5, 7, and 16 are working.

Is the fuse for your OBDII socket OK? I know from experience fuse 15 is for the OBDII socket on my '97 850 T5. That also agrees with my Owner's Manual (fuse 15 - OBD socket...) and the label on the under-the-hood fuse box (fuse 15 - ...Diagnostics...). [NOTE: It may be different on your car, since I've seen on another thread on ~2014-12-24 where Matty Moo said the Cigarette Lighter fuse controlled the OBDII socket -- I think he was referring to some sort of '96 850. That's definitely not the case in my '97 850 T5. Removal of my fuse 30 for the Cigarette Lighter does not disable my OBDII port.] If it were me, I'd recheck all my fuses before giving up on the bluetooth adapter.

esl_97_850_T5

Edit: Include Motronic 4.4 question. And ask about OBD socket fuse...

Post by **Ben850** » 25 Dec 2014, 11:58

In my experience, The Bluetooth elm327 needs to be pared using either 1234, or sometimes the code is 0000.
Either way, if the android device, or computer is Bluetooth enabled, there should not be an issue.

When you mention "slow", there is a communication lag between real time devices that are attached to your engine, and counting on information transmitted by way or radio waves. No matter the frequency.

I have one of these vacuum and digital, which is real time for sure, but even the Bluetooth is not horrible.

: This works nice on the A pillar.; boost gauge.jpg (7.3 KiB) Viewed 7950 times

I have the Torque app. and it serves as a reference. Not the last word.
I don't like the cliché, but it is what it is.

You still may have to get another car.

tzanis · Post by **tzanis** » 27 Dec 2014, 18:37

Ok.

I need to take things from a start.

In the past I have connected an obd2 cable to the port, to scan check engine codes or play etc, and I remember one time we exchanged a few messages about the mileage resurrection through obd2 esl_97_850_t5. So, in the past, with my laptop I have been connected to the obd2 all fine.

It happened that I tried to connect again at one time afterwards through usb obd2 and laptop, and was unsuccessful, which was probably my fault.

Before, in the autumn I bought one of the "knock off" 5 buck bluetooth obd2 for the sake of connecting it to my phone. With that I couldnt even connect to it, so i gave it to a friend, and on his car, it was working fine.

Now, I bought another bluetooth one, for the sake of having one in general, and I tried connecting it to my 97 850 glt. From the initial post where I have a screenshot of my phone, I can connect to the obd2 bluetooth, no problem, I used the 1234 password the first time anyway, but it has no connection to the ecu.

So, I was wondering if anybody else had the same issue, not connecting to the ecu, but connecting to the bluetooth,

I want to try your written commands that we talked and read about the mileage thing, but I think it will be easier to use the android terminal for the commands.

edit replies: I am using torque for android.
Also, I dont think the ecu has been modified in any matter. The previous owner told me that the car was non turbo, so I dont think he really cared about what he was driving

and, I will check the fuses, though I am getting power at the cigarette lighter, and the obd2 itself (lamps of the adapter are blinking).
I fear the pins too, i need to check them, I am not sure if anything happened to them, or a cable been pitched out,but i didnt unmount the console or plastics.
I will check the version, 4.4 or 4.5, I really dont know.

I will try with my laptop and usb obd2 to see if the thing is working, only reason I havent is, the usb belongs to my friend.

what I wrote about slow connection, I didnt know it and thanks for the clarification ben850, but I wrote it jokingly

p.s. I ll be putting a boost gauge too, I received it a few days ago

It's mechanical though.

last edit reply to esl. I am just simply trying to have the torque app give me realtime readings of the car. based on the comments of the youtube video I am not the only one I would say. I will be back with answers

Post by **esl_97_850_T5** » 28 Dec 2014, 00:22

tzanis,

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.

At the very minimum, I'd expect Torque to issue ATZ / ATL1 / ATSP 3 / 0100 in order to establish an OBDII emission diagnostics connection to a '96-'97 Volvo 850 or '98 S70/V70.

For the time being, I'm assuming your fuse 15 is OK (or whatever fuse controls your OBD socket is OK), and your bluetooth ATPP values are OK enough to be able to connect successfully after the protocol is forced to ISO 9141-2 via ATSP 3 (not via ATSP 3A, not via ATSP A3, and not via any other ATSP command).

The same applies if you use the "ELM 327 Terminal" Android app. You'll need to send at a minimum the ATZ / ATL1 / ATSP 3 / 0100 (or 0101, 0103, or any of the other OBDII emission diagnostics requests).

Did you previously try to force the Torque software to use ISO 9141-2?

esl

tzanis · Post by **tzanis** » 04 Jan 2015, 20:55

Tried to force ISO 9141-2 protocol to connect, with an app called OBD auto doctor, it tries to connect, and then it ends up disconnected. Tomorrow, I am starting school, so probably next weekend, I will check with my buddy's usb and laptop, he was the one to read the codes when I firstly got the car. I will be keeping you up to date with the matter. Lastly, if the usb fails too,the solution will probably be I f***ed one of the pins. I want to get moving with that though, I have put it off for long, and wanted to try your mileage recovery tutorial esl. The connection was my problem from the beginning I suppose.

cheers