New here from UK and looking for the best adaptor on the UK market (USB) to use it with FORscan. Do you have any recommendations, from either eBay or Amazon or anything I can pay with PayPal so I can return if it doesn't fit my expectations?
Thank you!
google search or ebay search OBDLink EX usb or els27v4 usb
Thanks, I did look around for them but they're both around 80 pounds shipped. I can get for a bit more a SVCI J2534 if I have to spend that much Any Chinese clone recommendations?
Re: ELM327-compatible adapters - how to choose
Posted: Tue Jun 16, 2020 2:12 am
by darrenboddy
New member! Hi~
I only have apple products (iOS) and it seems like everything I have seen on here is geared for Microsoft users. I purchased a (OHP ELMconfig FORScan OBD2 USB Adapter for Windows, Ford Diagnostic ELM327 Coding Tool with MS-CAN / HS-CAN Switch) but fear it will not work on my application.
Thoughts?
Re: ELM327-compatible adapters - how to choose
Posted: Mon Jul 13, 2020 7:08 pm
by vvmaks
darrenboddy wrote: Tue Jun 16, 2020 2:12 am
I only have apple products (iOS) and it seems like everything I have seen on here is geared for Microsoft users. I purchased a (OHP ELMconfig FORScan OBD2 USB Adapter for Windows, Ford Diagnostic ELM327 Coding Tool with MS-CAN / HS-CAN Switch) but fear it will not work on my application.
Thoughts?
For iOS, FORScan recommends OBDLink MX+. For Windows, OBDLink EX is your best option.
Kind regards,
Vitaliy
Re: ELM327-compatible adapters - how to choose
Posted: Wed Jul 22, 2020 7:45 am
by davecm
I bought the ELS27. Very happy with it. Worked first time, no switch needed, super quick in use, good build quality and cable.
Only downsides are high price and the fact the manufacturer seems not to have heard about airmail or DHL, and they only ship it by standard Russian postal service. I ordered from manufacturer's Ebay store and it took 5 weeks to arrive, presumably by boat, from St Petersburg. Much longer than than advertised delivery time. I would have happily paid extra for courier delivery.
darrenboddy wrote: Tue Jun 16, 2020 2:12 am
I only have apple products (iOS) and it seems like everything I have seen on here is geared for Microsoft users. I purchased a (OHP ELMconfig FORScan OBD2 USB Adapter for Windows, Ford Diagnostic ELM327 Coding Tool with MS-CAN / HS-CAN Switch) but fear it will not work on my application.
Thoughts?
For iOS, FORScan recommends OBDLink MX+. For Windows, OBDLink EX is your best option.
Kind regards,
Vitaliy
I own an OBDLink EX and I am going to order an MX+ soon for advanced options. I had some questions and their support team is so responsive and helpful. The build quality is really great as others have stated...
richvollberg wrote: Tue Feb 25, 2020 4:06 am
Update to my post above. The first EX unit I got had a bad USB cord. I contacted OBDLink and they sent out a new unit ASAP. It instantly conected and I had all the functions I was Looking For!.
Great Company and products. Working in the manufacturing field I understand that a Bad part gets sent out at times. Working on robots and PLC's we often order double the parts because the first one never works...
I already did the mods I wanted like horn off and DRL to fogs, Global window up and down from fob. Bambi Mode. Mirror heater on with remote start.
This is a awesome tool and just added a couple thousand dollars value compared to other stock f-150 Sports XLT with the snow plow option.
I highly recommend supporting this company, I own a Snap-On Solus Edge, a Drew-Tech Cardaq Plus 2 and a bunch of Fluke and Fieldpiece equipment so I have had the good fortune of using high-quality tools and the OBDLink EX that I now own is top notch.
Gary
Re: ELM327-compatible adapters - how to choose
Posted: Sat Oct 03, 2020 2:00 pm
by fido
Hello.
I have Viaken STN1170 V3.3.1 (ELM327 v1.3a) cable, will it be good for APIM update?
viaken.jpg (27.38 KiB) Viewed 17486 times
Re: ELM327-compatible adapters - how to choose
Posted: Sat Oct 17, 2020 3:25 pm
by remy16
Hello FORscan community
I just tried the Obdlink EX USB module.
It is recognized by the PC (W7) but it does not recognize the 1995 Ford Transit 2.5l TD vehicle. The vehicle is equipped with a 16-pin obd socket and a 95V89J464 AA computer.
Could someone tell me the correct parameters to set for obdlink EX,
Thank you
Translated by Google
Re: ELM327-compatible adapters - how to choose
Posted: Sat Oct 17, 2020 8:32 pm
by f-wolf
remy16 wrote: Sat Oct 17, 2020 3:25 pm
Hello FORscan community
I just tried the Obdlink EX USB module.
It is recognized by the PC (W7) but it does not recognize the 1995 Ford Transit 2.5l TD vehicle. The vehicle is equipped with a 16-pin obd socket and a 95V89J464 AA computer.
Could someone tell me the correct parameters to set for obdlink EX,
Thank you
Translated by Google
Your 1995 Ford Transit is too old !!
Your System
SNAG-20101807180800.jpg (32.8 KiB) Viewed 17259 times
New System
OBD2-Connector-Pinout.png (26.44 KiB) Viewed 17259 times
Re: ELM327-compatible adapters - how to choose
Posted: Thu Oct 22, 2020 2:30 pm
by adrianopery
FORScan wrote: Fri Mar 30, 2018 9:52 amUpdate 2019-12-11. Article updated as the following:
- Added reference to OBDLink EX
We are asked every day about adapter's choice. The problem is that there is no easy answer, as there is no ideal adapter that would fit best every specific case. In this article we have tried to address most important issues of the choice problem in most compact way.
Note: For professional work we would recommend to consider purchasing J2534 Passthru adapters that support Ford protocols. ELM327 family is recommended for amateur and semi-professional usage. This article reviews only ELM327 familty of adapters. J2534 Passthru devices will be addressed in a separate article.
1. Protocols
Table 1.1 - Ford protocols
OBDII name / Ford name
OBDII jack pins
Bus speed
Bus min. response time
How to detect
SAE J1850 PWM / Ford SCP
2, 10
41600 bps
20...40 ms
ISO9141 / Ford ISO
7
9600 bps
150...250 ms
CAN / Ford HS CAN
6, 14
500 Kbps
0...20 ms
/ Ford MS-CAN
3, 11
500 Kbps
0...20 ms
/ Ford UBP
3
10400 bps
150...250 ms
Table 1.2 - Ford protocols by model generations P - primary protocol (PCM) S - auxiliary protocol (not mandatory for FORScan)
Generation
SAE J1850 PWM
ISO 9141
CAN
Ford MS CAN
Ford UBP
Comment
Ford 1996 - 2003
P
S
-
-
-
Mazda 1996 - 2003
-
P
-
-
-
Some models used SAE J1850 PWM as primary
Ford EU, Mazda 2004 - 2009
-
S
P
S
-
Some models used SAE J1850 PWM as primary
Ford NA 2004 - 2009
-
S
P
S
S
Ford, Mazda 2010+
-
-
P
S
-
HS2, HS3 through MS-CAN
Simplest and quite reliable way to find out what protocols are supported in your car is to make a photo of the OBDII jack. Examples:
Focus Mk2 - only HS-CAN and MS-CAN
Mondeo Mk3 after restyling - J1850, ISO9141, HS-CAN, MS-CAN
Table 1.3 - Ford protocols by adapters
Chip
SAE J1850 PWM
ISO 9141
CAN
Ford MS CAN
Ford UBP
Adapter
ELM327 standard
X
X
X
-
-
ELM327, Kiwi 3
ELM327 with HS/MS switch
X
X
X
X
-
ELM327 marked as Ford, Mazda compatible
STN 1100
X
X
X
-
-
OBDLink SX/LX
STN 115x
X
X
X
X
-
OBDLink MX BT
STN 1170
X
X
X
X
-
ELS27 (old versions), Viaken STN1170
STN 2120
X
X
X
X
-
ELS27 (new version)
STN 2255
X
X
X
X
-
OBDLink MX+
STN 2230
X
X
X
X
-
OBDLink EX
2. Performance
Two parameters are mainly important for performance: Min. interface respone time (minimal response time or ping) - minimal possible time from the moment request to adapter is sent to the moment the response from adapter is received Max.interface baud rate - max possible data transfer baud rate between computer and adapter
These parameters directly affect connection time, parameter (PIDs) reading frequence, overall programming time
Table 2.1 - Adapters' performance
Adapter
Chip
Interface
Min.interface
response time
Max.interface
baud rate
Comment
ELM327 OHP HS/MS WiFi
ELM327 (clone)
WiFi
30-40 ms
38400 bps
Unknown manufacturer - "good clone". Recommended only for iOS
Kiwi 3
ELM327 compatible
Bluetooth Low Energy
40 ms
-
Can be used only with FORScan Lite for iOS
ELM327 HS/MS USB
ELM327 (original)
USB
0..2 ms
500 Kbps
OBDLink EX
STN2230
USB
0..2 ms
2Mbps
Recommended for FORScan for Windows
OBDLink SX
STN1100
USB
0..2 ms
2Mbps
OBDLink LX
STN1100
Bluetooth
-
-
OBDLink MX+
STN2255
Bluetooth
6..20 ms
-
Recommended for FORScan Lite for iOS, Android
OBDLink MX BT
STN115x
Bluetooth
8..20 ms
115200 bps
OBDLink MX WiFi
STN115x
WiFi
-
115200 bps
WiFi interface works unstable - it freezes and times out. Strongly not recommended!
ELS27 v3
STN2120
USB, Bluetooth
0..2 ms USB, 20 ms BT
8 Mpbs USB
Viaken STN1170 USB
STN1170
USB
0..2 ms
2 Mbps
Last versions of this adpater have buggy firmware 4.3.x. Recommended to downgrade to stable 4.1.1 or upgrade to stable 4.5.1
Viaken STN1170 BT
STN1170
Bluetooth
20..30 ms
38400 bps
Uses cheap BT chip so may freeze on some cars. Not recommended
Overall system performance can be easily estimated by adapter's performance and bus parameters as the following:
Overal min.response time = Min. adapter response time + Min.bus response time Overal baud rate = MIN ( Adapter max. baud rate / 2, Bus baud rate)
Examples:
Example 1: Ford Mondeo Mk3 PCM, bus J1850. Adapter ELM327 OHP HS/MS WiFi. According to the table 1.1, let's assume min. bus response time is 20 ms, bus baud rate is 41600 bps. According to the table 2.1 adapter's min response time is 40 ms, baud rate is 38400 bps.
Overal min.response time = 40 ms + 20 ms = 60 ms
Overal baud rate = MIN ( 38400 / 2, 41600) = MIN ( 19200, 41600) = 19200 bps.
Note: we divide interface baud rate by two because ELM327 family adapters exchange data in text format. So every machine byte is represented in 2 transferred bytes.
As we can see, the adapter significantly limits the overal system peformance in this example (in case of cars with CAN bus, like Mondeo Mk4 or Mk5, the test results would be much worse). Is that bad? Well, it depends on your goals. If reading DTC and some PIDs is the only objective you have, it is not too important. But if you plan to read PIDs in real-time (or as much close to it as possible) or perform programming (actual for CAN bus), then this adapter is a bad choice.
Example 2: Mazda 323 2001, bus ISO. Same adapter.
Overal min.response time = 40 ms + 250 ms = 290 ms
Overal baud rate = MIN ( 38400 / 2, 9600) = MIN ( 19200, 9600) = 9600 Kbps.
In this case the adapter is OK, because the bus itself is very slow. Reponse time is less than 20% higher than maximum possible for this car, and transfer speed is also limited by the bus.
Example 3: Ford Fusion 2015, bus CAN. Adapter ELS27 v3 USB. Let's assume CAN bus response time is 0 ms, and adapter has 2 ms of response time and 2 Mpbs baud rate.
Overal min.response time = 2 ms + 0 ms = 2 ms
Overal baud rate = MIN ( 2000000 / 2, 500000) = MIN ( 1000000, 500000) = 500 Kbps.
So in this case the response time is minimal, and baud rate is limtied by the CAN bus one.
3. Reliability
Two things are important for reliability:
- quality of the adapter. Not original adapters in general case have lower quality than original ones. We will create a dedicated article about so-called "clone problem".
- type of interface. The fact is that wireless interfaces used in ELM327 family of adapters are much less reliable than USB interface. And this problem is actual not only for "clones", but also for "original" adapters (OBDLink MX WiFi and Viaken VScan Bluetooth are most obvious examples).
So in general case we recommend to use USB for Windows version of FORScan, where it is possible. BT and WiFi devices are only recommended for mobile platforms (iOS and Android).
Also, important note about adapters with mechanical HS/MS switch: in addition to the fact it is not very convenient to switch it manually, it may be not possible to perform some operations with this type of adapter. If some operation requires a simultaneous access to both HS and MS (so FORScan needs to access some module(s) on HS CAN bus and, at the same time, other modules on MS-CAN bus), it cannot be normally executed using adapters with mechanical switch. Example: reading parameters (PIDs) in virtual module All, Module initialization subfunction in service functions "Remote keyless entry and Start".
4. Recommendations
Table 4.1 - recommendations on adapters
NO - not recommended for this platform
D - recommended for diagnostic: read PID, read/reset DTC, simple service functions
C - recommended for configuration: write configuration parameters to modules, complex service functions
P - recommended for programming: complex configuration, firmware update (only for CAN )
Adapter
FORScan for Windows
FORScan Lite for iOS
FORScan Lite for Android
OBDLink EX
D, C, P
NO
NO
OBDLink SX
D, C, P*
NO
NO
OBDLink LX
D (if MS-CAN is not required)
NO
D (if MS-CAN is not required)
OBDLink MX+
D, C
D
D
OBDLink MX BT
D, C
NO
D
OBDLink MX WiFi
NO
NO
NO
ELS27 v3
D, C, P
NO
D
Viaken STN1170 USB
D, C, P
NO
NO
Viaken STN1170 BT
NO
NO
NO
* - can be modified for MS-CAN support as described here.
Note: actually, all what we write about Viaken adapter is related to older version (v1 or v2, in black case). We had no chance to test their v3 version yet.
Hi guys, I would like to know if we have any other new option to use as Bluetooth device?
An updated list!