OBDLink® EX
Re: OBDLink® EX
Well, not sure what happened to the reply that was posted to me. It had a link to instructions for dl'ing a bunch of drivers to try. The reply was here earlier today but just disappeared. Not sure why. None of the drivers worked anyway. One of them even created a non-working PCMCIA wireless modem in the hardware list. Tried every configuration I could think of and nothing would work on the laptop.
Decided to try on my desktop to make sure that it wasn't the OBDLink EX that was the issue. Plugged it in and Windows 10 installed the driver all on it's own and I got a yellow light. That is as far as I have gotten at this time since it would be a PIA to lug my desktop to the garage (would need a 50 foot usb cable otherwise and don't think that length is supported). So I will have to look into getting a cheap windows laptop, the cheaper the better as long as it works.
John
Decided to try on my desktop to make sure that it wasn't the OBDLink EX that was the issue. Plugged it in and Windows 10 installed the driver all on it's own and I got a yellow light. That is as far as I have gotten at this time since it would be a PIA to lug my desktop to the garage (would need a 50 foot usb cable otherwise and don't think that length is supported). So I will have to look into getting a cheap windows laptop, the cheaper the better as long as it works.
John
-
rgcarnevale
- Posts: 19
- Joined: Thu Sep 03, 2020 8:15 pm
- Vehicle: F150, Gasoline 3.5L 2011
- Location: Massachusetts
Re: OBDLink® EX
I have this adapter has anyone tried using it with FJDS software for programming? Forscan will not program or even reset my PCM. I have not tried or even looked at FJDS yet but came across it while doing some research. I have downloaded IDS but this needs Ford device from what I can tell.
-
scorpionul22
- Posts: 37
- Joined: Thu Aug 04, 2016 9:31 am
- Vehicle: Ford Focus MK3 RS
Re: OBDLink® EX
v5.6.5 - 2020/10/14
-------------------
- BUG: Fixed ISO protocol detection failure
v5.6.4 - 2020/10/06
-------------------
- BUG: Fixed a BUFFER FULL caused by the CAN RX buffer getting filled while waiting for a FC frame during a multi-frame transmission
-------------------
- BUG: Fixed ISO protocol detection failure
v5.6.4 - 2020/10/06
-------------------
- BUG: Fixed a BUFFER FULL caused by the CAN RX buffer getting filled while waiting for a FC frame during a multi-frame transmission
Re: OBDLink® EX
How does EX compare to the MX+ besides the wireless functionality?
-
f-wolf
- Posts: 1451
- Joined: Sat Apr 18, 2015 12:41 am
- Vehicle: *** Ford ***
- Location: Third planet from the sun
Re: OBDLink® EX
davev6 wrote: Fri Nov 27, 2020 12:30 pm How does EX compare to the MX+ besides the wireless functionality?
https://obdstation.com/?s=+OBDLink+EX
Re: OBDLink® EX
Newbie so be kind
What is the difference between the 2 update files?
stn2230-5.1.3.zip vs obdlink_ex-5.6.5.zip?
Looking in Forscan under Configuration
Interface:
Type: FTDI #1:223010156535, 2000000 kbps
Adapter: OBDLink EX r1.0 STN2230 v5.1.3 (ELM327 v1.3a)
So I assume I have the latest STN, but do I need the obdlink update?
What is the difference between the 2 update files?
stn2230-5.1.3.zip vs obdlink_ex-5.6.5.zip?
Looking in Forscan under Configuration
Interface:
Type: FTDI #1:223010156535, 2000000 kbps
Adapter: OBDLink EX r1.0 STN2230 v5.1.3 (ELM327 v1.3a)
So I assume I have the latest STN, but do I need the obdlink update?
-
scorpionul22
- Posts: 37
- Joined: Thu Aug 04, 2016 9:31 am
- Vehicle: Ford Focus MK3 RS
Re: OBDLink® EX
v5.6.5 - 2020/10/14
-------------------
- BUG: Fixed ISO protocol detection failure
v5.6.4 - 2020/10/06
-------------------
- BUG: Fixed a BUFFER FULL caused by the CAN RX buffer getting filled while waiting for a FC frame during a multi-frame transmission
v5.6.1 - 2020/09/18
-------------------
- NEW: Added command to change CAN consecutive and flow control frame reception timeouts
- NEW: Added command to specify additional STmin delay
- NEW: Added support for 4 byte header to ATSH
- CHG: Removed CAN deaf time after sending a CAN message
- BUG: Fixed 7Fxx78 message being counted when using STPTO 0
- BUG: Fixed STSLU, STSLVL, and STSLX not working
v5.5.3 - 2020/06/09
-------------------
- BUG: Fixed EEPROM not retaining settings after firmware update
v5.5.2 - 2020/06/03
-------------------
- BUG: Fixed inability to transmit after CAN ERROR
v5.5.1 - 2020/06/02
-------------------
- BUG: Fixed possible FATAL ERROR when receiving multi-frame message
v5.5.0 - 2020/05/28
-------------------
- BUG: Fixed CAN OUT OF MEMORY error introduced by async CAN optimization
v5.2.0 - 2020/05/10
-------------------
- NEW: Added support for PP 2C bit 4 (8/7 CAN)
- CHG: CAN driver improvements
- CHG: Changed welcome string to print "ELM327 1.4b" instead of "ELM327 1.3a"
- CHG: Increased response pending timeout to 6000 ms to account for tolerance
- CHG: "STOPPED" is now printed exiting all monitoring modes
- BUG: Reset message reception timeout on CAN first frame causing "NO DATA"
- BUG: Fixed "BUFFER FULL" when CAN flow control arbitration fails due to a busy bus
v5.1.3 - 2020/01/24
-------------------
- CHG: Removed unnecessary sleep functionality
- CHG: Increased UART RX buffer size to accomadate large transfers @ 2Mbps baudrate
- CHG: Set max UART baud rate of EX and SX to 2000000
v5.1.1 - 2019/10/10
-------------------
- Initial release
all difference
-------------------
- BUG: Fixed ISO protocol detection failure
v5.6.4 - 2020/10/06
-------------------
- BUG: Fixed a BUFFER FULL caused by the CAN RX buffer getting filled while waiting for a FC frame during a multi-frame transmission
v5.6.1 - 2020/09/18
-------------------
- NEW: Added command to change CAN consecutive and flow control frame reception timeouts
- NEW: Added command to specify additional STmin delay
- NEW: Added support for 4 byte header to ATSH
- CHG: Removed CAN deaf time after sending a CAN message
- BUG: Fixed 7Fxx78 message being counted when using STPTO 0
- BUG: Fixed STSLU, STSLVL, and STSLX not working
v5.5.3 - 2020/06/09
-------------------
- BUG: Fixed EEPROM not retaining settings after firmware update
v5.5.2 - 2020/06/03
-------------------
- BUG: Fixed inability to transmit after CAN ERROR
v5.5.1 - 2020/06/02
-------------------
- BUG: Fixed possible FATAL ERROR when receiving multi-frame message
v5.5.0 - 2020/05/28
-------------------
- BUG: Fixed CAN OUT OF MEMORY error introduced by async CAN optimization
v5.2.0 - 2020/05/10
-------------------
- NEW: Added support for PP 2C bit 4 (8/7 CAN)
- CHG: CAN driver improvements
- CHG: Changed welcome string to print "ELM327 1.4b" instead of "ELM327 1.3a"
- CHG: Increased response pending timeout to 6000 ms to account for tolerance
- CHG: "STOPPED" is now printed exiting all monitoring modes
- BUG: Reset message reception timeout on CAN first frame causing "NO DATA"
- BUG: Fixed "BUFFER FULL" when CAN flow control arbitration fails due to a busy bus
v5.1.3 - 2020/01/24
-------------------
- CHG: Removed unnecessary sleep functionality
- CHG: Increased UART RX buffer size to accomadate large transfers @ 2Mbps baudrate
- CHG: Set max UART baud rate of EX and SX to 2000000
v5.1.1 - 2019/10/10
-------------------
- Initial release
all difference
-
GermanTourneo
- Posts: 21
- Joined: Sat Feb 29, 2020 3:00 pm
- Vehicle: Ford Tourneo 1.8 TDDI 75cv
Re: OBDLink® EX
Hi, I have tried to adapt the vp30 pump in my 2006 ford tourneo 75cv 1.8tddi, with eml327 but it always gives me this error. If I buy the OBD Link EX does it solve the problem or could it be due to a problem with the car itself?


Re: OBDLink® EX
I've ordered a OBDLink EX from Amazon. I've updated the firmware also.
When I use Forscan everything works well but when I'd like to connection ELMconfig 0.2.17c I get error responds message.
As (V)CP and FTDI D2XX method also get the same "Incorrect response from adapter to request "ST I": STN2230 v5.6.5.
Has somebody met with this befor? Colud you help me to sold the problem? Thx.
When I use Forscan everything works well but when I'd like to connection ELMconfig 0.2.17c I get error responds message.
As (V)CP and FTDI D2XX method also get the same "Incorrect response from adapter to request "ST I": STN2230 v5.6.5.
Has somebody met with this befor? Colud you help me to sold the problem? Thx.
- Attachments
-
- Error.JPG (14.83 KiB) Viewed 5200 times
-
Ecmbuster
- Posts: 2433
- Joined: Sun Mar 15, 2015 4:08 am
- Vehicle: Subaru, Volvo Bertone and two Motorcycles
- Location: On a spinning rock
Re: OBDLink® EX
The ELMconfig is dated software and never kept up to the new interfaces.troby wrote: Fri Jul 09, 2021 5:24 pm When I use Forscan everything works well but when I'd like to connection ELMconfig 0.2.17c I get error responds message.
As (V)CP and FTDI D2XX method also get the same "Incorrect response from adapter to request "ST I": STN2230 v5.6.5.
This link offers what should be used.
https://fordcom.de/elm327/
The STN firmware is very different than the standard ELM327 device.
If you want ELMconfig to work, purchase the BAFX v1.4 and add the switch inside.
Do not ask for help in PM. Use the forum to ask and answer questions! There's a special place for NOT following up!