When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
My OBDLink MX Bluetooth arrived this morning, so I gathered up all the spreadsheets, instructions, and laptop specially set up with Windows 7 that I have spent a week studying and prepping, and ran down to my truck.
I plugged the module in and paired it with the computer, no problem.
Opened Forscan and tried to connect. Problem.
It went through checking all the possible connections - even showed a bluetooth device address, but ultimately reported No ELM Found.
So I tried the OBDwiz native software for the OBDLink. It showed the device paired with the computer, but also failed to connect.
I have searched the OBDLink forum and this one for this problem. I found a couple on the ABDLink forum but no solution posted.
Is there something easy I'm missing?
Oh yeah, I uninstalled and repaired the module to ensure it was installed correctly. It does show up in the devices and printers section, and the computer reports the device is working properly. So I'm kind of at a loss at this point.
Help is definitely appreciated.
According to the box, supported platforms are:
Android 2.2 or later
Windows XP/Vista/7/8/10
Windows Phone 8 or later
Microsoft Surface Pro tablets
My copy of Windows 7 is as up-to-date as possible. The laptop - a Lenovo ThinkPad X61 has Bluetooth built in, and since it pairs up, that shouldn't be an issue, either.
I ran into the same thing when I first tried mine. I was able to get it to connect and I am trying to recall what I did -
just double check you unclicked demo mode in forscan and then in the connection tab I believe I had to select blue tooth specifically. I'm looking as we speak.
You got the adapter to connect with the computer but I think the issue is that Forscan does not know to look for your bluetooth - I know despite what the screen messages show.
I would open up device manager and confirm that the device driver installed properly. If so you should also see it in the “devices and printers” section.
at that point it should be available via bluetooth.
If the device doesn’t show in “devices and printers” it didn’t install correctly. Pull it, reboot, try again.
I have an OBDLink MX Bluetooth adapter and when I try to connect it says “No ELM Found” Stop running the OBDWiz software that came with the adapter and try again. If the message persists, re-pair the adapter according to the directions that came with the adapter.
Credit from the forscan for dummies thread - I had to do this as well ...worth a try
I ran into the same thing when I first tried mine. I was able to get it to connect and I am trying to recall what I did -
just double check you unclicked demo mode in forscan and then in the connection tab I believe I had to select blue tooth specifically. I'm looking as we speak.
It had "auto" selected on the connection tab. I've changed it to "bluetooth" so I'll see what happens when I try again.
I also have a USB wireless mouse that I'll disconnect just in case it's somehow using the same com port.
Since the device fails to connect to Forscan or the OBDLink software, but it shows up paired in both applications, it has to be something common to both. I kind of doubt it would be a simple setting. More likely a hardware issue, so I'm suspecting the OBDLink module.
Originally Posted by Cohlmeyer
Windows 7 will work no problem.
I would open up device manager and confirm that the device driver installed properly. If so you should also see it in the “devices and printers” section.
at that point it should be available via bluetooth.
If the device doesn’t show in “devices and printers” it didn’t install correctly. Pull it, reboot, try again.
There's no doubt it installed correctly. But I did uninstall and reinstall "just in case" but it made no difference. I'm going to go back out to the truck and try again.
Thanks guys, it's working now! It was one of two things - the only two I changed. I disconnected the wireless USB mouse, and under the connection tab I changed from auto to bluetooth as Bernie suggested. If the mouse was the issue, it would because both applications were trying to use Com 4, though I don't know for sure what com port the mouse was using. It was a "just in case" kind of thing. I really think it was Bernie's suggestion that fixed the issue.
Now I have to get busy and enable Bambi mode and HDC.
I told myself I was only going to change one thing and see how that went, but I went ahead and activated the Hill Descent Control, disabled seat belt chimes, and enabled entering GPS destination while moving. It was hard to make myself stop! If my laptop battery hadn't gotten low, I'd probably still be out there!
Enabling the Hill Descent Control did cause a warning to Check Brake System with a DTC on the Vacuum Pressure Sensor that won't reset. So now I have to research that to see what's going on. The Hill Descent Control did work as it should though, so there's that!
Welcome to the world of Forscan wrvond! Pretty cool stuff for sure. For your next fix, I suggest slinging seatbelt alarms, Bambi mode, police mode. So many good things to tweak? Glad you got it working now.
Rezvani's Latest Post-Apocalyptic Monster Is a Ford F-150 Raptor Underneath
Slideshow: Called the Fortress, the 850-horsepower pickup combines Raptor underpinnings with military-inspired features, survival equipment, and a starting price of $285,000.
sweet
