I just purchased an OBDLink SX from scantool.net. This was one of the adapters listed in the "ELM327 compatible adapters - how to choose" forum. I installed the drivers as recommended by scantool.net and their software (OBDwiz) sees the adapter. However, FORScan, after searching all the ports, gives me an error... "No ELM found. Please check connection and try again". I get the same message if the adapter is plugged into my vehicle or not.
Am I missing something?
OBDLink SX not seen by FORScan
-
Boland1776
- Posts: 13
- Joined: Fri Feb 01, 2019 12:26 am
- Vehicle: F150, 5.4l, 2010
Re: OBDLink SX not seen by FORScan
If you go into device manager or devices (depending on what OS you have) are you seeing the USB port and the OBDLink SX?
Sounding a lot like a driver issue to me....
Sounding a lot like a driver issue to me....
-
Boland1776
- Posts: 13
- Joined: Fri Feb 01, 2019 12:26 am
- Vehicle: F150, 5.4l, 2010
Re: OBDLink SX not seen by FORScan
This is very frustrating!
At one point I had my OBDLink SX working on a windows 7 laptop. After reading what FORScan can do I decided to purchase an ohp-ELMconfig, which has MS-CAN functionality. I plugged the new adapter in, started FORScan and got the old "No ELM found" message. I plugged the OBDLink SX back in and not it too gets the "No ELM found" message (again).
I'm starting fresh with Windows 10 (Enterprise) and followed the instructions at http://www.totalcardiagnostics.com/supp ... 2-software
It looks like the drivers install properly but FORScan still says "No ELM found". I tries the "EasyOBD", in the troubleshooting section and it just hangs trying to communicate with the adapter. I still sounds like a drive issue bit I'm not sure.
I was going to attach some screen shots but it says "file too large"
COM4 entry....
device manager -> COM4 -> General:
Type: Ports (COM & LPT)
Manufacturer: FTDI
Location: on USB Serial Converter
device manager -> COM4 -> Driver:
Provider: FTDI
Date: 9/28/2016:
Version: 2.12.24.0
Digital Signer: Microsoft Hardware compatibility publisher
Serial Converter entry...
device manager -> USB Serial Converter-> General:
Type: USB controller
Manufacturer: FTDI
Location: Port_#0001.Hub_#0005
device manager -> USB Serial Converter -> Driver:
Provider: FTDI
Date: 9/28/2016:
Version: 2.12.24.0
Digital Signer: Microsoft Hardware compatibility publisher
How can I get this working???
At one point I had my OBDLink SX working on a windows 7 laptop. After reading what FORScan can do I decided to purchase an ohp-ELMconfig, which has MS-CAN functionality. I plugged the new adapter in, started FORScan and got the old "No ELM found" message. I plugged the OBDLink SX back in and not it too gets the "No ELM found" message (again).
I'm starting fresh with Windows 10 (Enterprise) and followed the instructions at http://www.totalcardiagnostics.com/supp ... 2-software
It looks like the drivers install properly but FORScan still says "No ELM found". I tries the "EasyOBD", in the troubleshooting section and it just hangs trying to communicate with the adapter. I still sounds like a drive issue bit I'm not sure.
I was going to attach some screen shots but it says "file too large"
COM4 entry....
device manager -> COM4 -> General:
Type: Ports (COM & LPT)
Manufacturer: FTDI
Location: on USB Serial Converter
device manager -> COM4 -> Driver:
Provider: FTDI
Date: 9/28/2016:
Version: 2.12.24.0
Digital Signer: Microsoft Hardware compatibility publisher
Serial Converter entry...
device manager -> USB Serial Converter-> General:
Type: USB controller
Manufacturer: FTDI
Location: Port_#0001.Hub_#0005
device manager -> USB Serial Converter -> Driver:
Provider: FTDI
Date: 9/28/2016:
Version: 2.12.24.0
Digital Signer: Microsoft Hardware compatibility publisher
How can I get this working???