did you try a different speed

did you use genuine drivers  https://ftdichip.com/wp-content/uploads/2023/09/CDM-v2.12.36.4-WHQL-Certified.zip

how to use https://ftdichip.com/wp-content/uploads/2023/11/AN_396_FTDI_Drivers_Installation_Guide_for_Windows_10_11.pdf

 

@Botus I didn't use those drivers specifically.... it just installed automatically via Windows from memory.

I can't find the website I used to download ELMConfig, Runtime Drivers (and possibly something called CDM / CDM drivers?) thought it was via the James Simpson site but doesn't seem to be working.

 

I think the reason the ELM327 I have doesn't work is because it's probably a fake / poorly manufactured unit with bad chips!

The ELS27 I bought was more expensive at £50 and appears to operate better.

However after reading James Simpsons site in a bit more detail he says when using Adapter Setup and clicking Open Port it should automatically assign the baud rate, if it doesn't it's likely to be a fake.

"We will now need to set up the baud rate for the unit before we open the main program, this is done by selecting the “Adapter Setup” button at the bottom of the ELMConfig screen. This will open a new part of the program. Simply press the “Open Port” button, this then scans through the different baud rates that is capable with the ELM and should stop on the 500k baud rate setting, showing you that it is capable of handling 500k baud rate (if it does not stop here, you may have a fake unit). "

https://www.jamessimpson.co.uk/getting-started-elmconfig/

 

 

CDM is the windows drivers - Windows Combined Driver Model (CDM) - don't ever believe Microsoft know how to do anything properly

wow this seems to be the stuff - note: always be careful with this sort of stuff - looks just like his old site - ummm seems legit with the right files and nothing nasty my end

 

http://civil.techserviceford.com/ELMConfig/

 

maybe you need to slow the decent vlinker cable to cope with the older software - but try with the newer version of EMLconfig from link - its from August 2016

and don't forget to update the vlinker cable to its latest firmware - all this vehicle comms is a game - few knew the madness the manus got up to trying to make it difficult - they still unravel peculiarities that cause complex procedures to crash -

 

read the release notes for forscan check this from the last release in Dec 2024...  the red bit is fixes for cars most scrapped 10 years ago

- bug: incorrect work of PCM Service function "Fuel/Change Fuel Injector Correction factors" for Edge 2.0 TDCi 2019-2020MY
- bug: unability to gain PATS security access on some last generation cars with Start button if no keys are available
- bug: unability to gain PATS security access on some EU models that have no VIN programmed in PCM
- bug: "The vehicle conditions are incorrect" error on DTC reset on some old ABS blocks (Focus Mk1)

 

and here bug fixes and missing bits for the vlinker cable Nov 2024  v2.3.04  https://www.vgatemall.com/downloadcenter/

  - Added VTIMSP0/1/2 command.
  - Added VTIIAP0/1/2 command.
  - Added VTISOSI addr,mode command.
  - Added SWGP switch variable: KWF0/1.
  - The PWM protocol supported 83.3Kbps.
  - The VPW protocol supported 41.6Kbps.

 

OK thanks, what should I do? Use these files and drivers / runtime pack instead?

check what drivers the PC is using - update the vlinker firmware (if you haven’t already)

download and install the last EMLconfig and give it a go - you must set it to a Ford Focus or it will go silly

if it plays up try the runtime pack full of ancient files and reinstall EMLconfig

then try again - you can test all that stuff without a car anywhere near - indeed not only can you - you should !

then check/change the baud rate

and if that’s messing about try the old crap cable

 

3 hours ago, Botus said:

 

download and install the last EMLconfig and give it a go - you must set it to a Ford Focus or it will go silly

 

re this point.... its quite well hidden and will get a curved ball on the interface if you don't select Focus II