UCDS adapter in Forscan?
Posted: Sat Jul 27, 2024 12:56 am
Hi,
Somebody knows how to connect the UCDS adapter to Forscan?
A friend of me sold me his UCDS, it works perfect in UCDS, but I'm unable to configure Forscan for it.
A solution?
Thanks!
mine used to work no problem, but now it refuses to connect using it. I have uninstalled and reinstalled the UCDS drivers (it's a v3 adapter) and uninstalled an reinstalled various versions of Forscan - no joy.
I'm wondering if it's something to do with the latest firmware updates?
It means that if you use UCDS v3 and it doesn't work with FORScan, copy ftd2xx.dll from UCDS exe folder to FORScan exe folder. This is an incorrect J2534 library implementation by UCDS, and not a problem of FORScan. Also, if you have FTDI drivers installed in your system (so ftd2xx.dll is available in Windows system folder) everything should work "out of the box". This is why it works "out of the box" for some people (who seems to have FTDI drivers installed) and doesn't work for others (who have no FTDI drivers installed).
Old versions of UCDS (v2?) had problem with J2534 drivers. FORScan was able to access the DLL that implements J2534 API (ucdsj2534.dll) in a standard way. But this library had additional dependencies (unknown for FORScan and other s/w) - libusb0.dll and ftd2xx.dll available in the same folder. This is incorrect driver implementation, However it can be fixed quite easily by copying the libusb0.dll and ftd2xx.dll from UCDS folder to any place FORScan can access it - either in Windows DLL system folder or in FORScan EXE folder.
Somebody knows how to connect the UCDS adapter to Forscan?
A friend of me sold me his UCDS, it works perfect in UCDS, but I'm unable to configure Forscan for it.
A solution?
Thanks!
mine used to work no problem, but now it refuses to connect using it. I have uninstalled and reinstalled the UCDS drivers (it's a v3 adapter) and uninstalled an reinstalled various versions of Forscan - no joy.
I'm wondering if it's something to do with the latest firmware updates?
It means that if you use UCDS v3 and it doesn't work with FORScan, copy ftd2xx.dll from UCDS exe folder to FORScan exe folder. This is an incorrect J2534 library implementation by UCDS, and not a problem of FORScan. Also, if you have FTDI drivers installed in your system (so ftd2xx.dll is available in Windows system folder) everything should work "out of the box". This is why it works "out of the box" for some people (who seems to have FTDI drivers installed) and doesn't work for others (who have no FTDI drivers installed).
Old versions of UCDS (v2?) had problem with J2534 drivers. FORScan was able to access the DLL that implements J2534 API (ucdsj2534.dll) in a standard way. But this library had additional dependencies (unknown for FORScan and other s/w) - libusb0.dll and ftd2xx.dll available in the same folder. This is incorrect driver implementation, However it can be fixed quite easily by copying the libusb0.dll and ftd2xx.dll from UCDS folder to any place FORScan can access it - either in Windows DLL system folder or in FORScan EXE folder.