ELM327 problems

This site may earn a commission from merchant affiliate
links, including eBay, Amazon, Skimlinks, and others.

bmac1996acc

bmac1996acc

Joined
Sep 8, 2009
Threads
16
Messages
1,188
Location
Cumming, GA
Anyone had a problem getting one of these to connect to the 80? I've messed with it for a while and can't get it to work. I tried three other vehicles at work and Torque connects to the ECU without issue. The lights on the ELM, when connected to the 80, go from green to yellow to red quickly and then stays red. On other vehicles they went through the same sequence but red stayed on and yellow began to blink rapidly. Anyone had a similar problem and manage to get it to work?
 
Mine works fine, did nothing special. '95 by the way.
 
You are using the little blue Bluetooth thing? That's what I have. I did two things to make mine reliable.

1) Turn the vehicle key off. Unplug the Bluetooth OBD2 device from your OBD2 port. Close the Torque App. Unpair the device from your phone. Turn off then turn on your phones Bluetooth. Plug in the device to your OBD2. Turn the vehicle to on. Scan for devices from your phone. Find the Bluetooth OBD2 device from your phone and enter your PIN. Now open the Torque App and everything should work.

2) In the Torque App under vehicle profiles you can add a specific Bluetooth OBD2 device. Add your device to the vehicle profile. This seems to be more reliable.

On my phone I have to make sure the Bluetooth OBD2 device is broadcasting and paired before my Torque App will see it. Newer vehicles I don't seem to have this problem. I have not found the correlation and am no expert on OBD, Torque, or Bluetooth. This is just what I do to make mine work, and it works reliably every time now.

All that being said, I used one for 6 months and it dies. Ive been on a new on, same brand and seller for a year and 6 months now.
 
Last edited:
OffGridOverland said:
I am a dealer for plx devices. Which brand adapter are you using?

And can you connect to the elm but just not your 80? Which year 80 do you have?
Click to expand...

This is on my 96 LX. I am using a Nexus 5 and Nexus 7, and I think this one
http://www.amazon.com/ELM327-Bluetooth-CAN-BUS-Diagnostic-Scanner/dp/B0090ZJPMK?tag=ihco-20

I use 3 of these devices on 3 different vehicles. Once I set them up in the Torque app as above and in the vehicle profiles it works fine.

Sorry, I just realized you were probably talking to the OP, not me.
 
I run torque, dash comand and bluedriver on my 97 LC everyday.
I have a tablet set up for it. I'm in the process of removing the radio and using a 8.0 tab 4s in dash. This gives me music, maps, and obdii. I'm also installing the plx water temp, oil pressure and o2 sensors and pairing that to my elm so I have it on torque and dash comand.

Those cheap elm devices work sort of hit and miss. I have bought a few off Amazon over the years and had no connection due to chipset issues. Had two just stop all together.

There is also configuration issues. Bluetooth = Android and WiFi = Apple

If we can get which device and year truck the op has. Then which phone. That is a start.
There are a few things to make sure are checked on both sides.

I can write an faq tonight for everyone.
 
OffGridOverland said:
I am a dealer for plx devices. Which brand adapter are you using?

And can you connect to the elm but just not your 80? Which year 80 do you have?
Click to expand...
OffGridOverland said:
Also what phone or tablet are you. using?
Click to expand...
I'm using one of these eBay specials. I can connect to the ELM. Torque as well as a few other obd2 apps see the adapter. They just can't communicate with the ECU. I tested the ELM on a few work trucks and it connected fine but they are Fords. One of my coworkers has an Avalon I'm going to try it on later. I'm using a Galaxy S4. 80 is a 97.

1427907217647.webp
 
Last edited:
OffGridOverland said:
I run torque, dash comand and bluedriver on my 97 LC everyday.
I have a tablet set up for it. I'm in the process of removing the radio and using a 8.0 tab 4s in dash. This gives me music, maps, and obdii. I'm also installing the plx water temp, oil pressure and o2 sensors and pairing that to my elm so I have it on torque and dash comand.

Those cheap elm devices work sort of hit and miss. I have bought a few off Amazon over the years and had no connection due to chipset issues. Had two just stop all together.

There is also configuration issues. Bluetooth = Android and WiFi = Apple

If we can get which device and year truck the op has. Then which phone. That is a start.
There are a few things to make sure are checked on both sides.

I can write an faq tonight for everyone.
Click to expand...
I look forward to the FAQ your solution sounds like what I want.
 
Connected to ELM.

1427907803542.webp
 
I am willing to bet its a chipset issue with the elm.
There was a fix for some but required you to disassemble and solder some jumpers.

I'd also try a second obdii device. Like a autozone borrow in the parking lot. If you don't have one. Just to verify you don't have a port issue on the 80.
 
Just tested on a 99 Avalon... Connected up no problem

1427908399547.webp
 
OffGridOverland said:
I am willing to bet its a chipset issue with the elm.
There was a fix for some but required you to disassemble and solder some jumpers.

I'd also try a second obdii device. Like a autozone borrow in the parking lot. If you don't have one. Just to verify you don't have a port issue on the 80.
Click to expand...

I'll try to clean the connector tonight and check with AutoZone tomorrow.
 
98 SNAKE EATER said:
I love my little ELM mini :)

So far, it has worked on all OBD2 cars I've tried it on except for a BMW 7 series (I was able to clear codes and remove the MIL, but couldn't read what they were......odd)

I use both Droid Scan and Torque, but prefer DS as it's much faster :cool:
Click to expand...

You probably need WinKFP, NFS, NCS Expert, INPA for your BMW
 
Some can but they have limited or no access to the BMW specific stuff. My E39 is a mess and I'm finally going to give up on it and put it on Craigslist.
 
Yeah, the same can be said for many manufacturers that require use of their own specific scan tools to view and program specific parameters (FORD IDS, GM Tech2, MB Star, etc.)

Thing is, basic fault codes should be able to be read by any generic scan tool as that was the whole idea behind OBD2 :doh:
 
You must log in or register to reply here.

Share this page

Back
Top Bottom