UCDS adapter in Forscan?

Discussion about adapters and connections - usage, problems, solutions

Re: UCDS adapter in Forscan?

Postby mrkb » Tue Oct 03, 2017 6:59 pm

The changelog for new beta (2.3.11) lists J2534 fixes. For me however, it does not solve the problem of the UCDS adapter not working in J2534 mode in Forscan.

I've tried reverting to earlier betas and no luck. I'm beginning to suspect it might be an UCDS issue which I've reported here http://www.ucdsys.ru/tracker/view.php?id=178.
Posts: 2
Joined: Fri May 27, 2016 8:40 am
Vehicle: Ford Focus 3.1 1.0L 125BHP

Re: UCDS adapter in Forscan?

Postby Dragunov » Fri Oct 13, 2017 1:47 pm

Fixed in latest Version?

- bug in J2534 protocol implementation - support for HS2/HS3 CAN presence service
Posts: 33
Joined: Thu Aug 25, 2016 8:55 am
Vehicle: Ford Mondeo MK5 Titanium 2.0TDCi 150HP

Re: UCDS adapter in Forscan?

Postby Dragunov » Sat Oct 28, 2017 10:22 pm

Posts: 33
Joined: Thu Aug 25, 2016 8:55 am
Vehicle: Ford Mondeo MK5 Titanium 2.0TDCi 150HP

Re: UCDS adapter in Forscan?

Postby FORScan » Sat Dec 09, 2017 12:47 am

FORScan implements standard J2534 Passthru API to access J2534 Passthru adapters, no matter if it is UCDS , Ford VCMII, CanTieCar, Tactrix OpenPort, VXNano etc . Yes, different adapters implement some aspects of J2534 standard differently, so we periodically fix J2534 issues in FORScan. For example, in latest versions we added J2534 message send timeout that, as realized later, doesn't work properly in adapters like VXDIAG/VXNano (makes them extremely slow). We are going to fix it in the next release. But connection procedure is quite simple and straightforward. This procedure in FORScan works well and not changed for months if not years. Connection issues, if any, most likely caused by adapter or it's drivers.

As for UCDS, we researched connection problem with this adapter several months ago and found out the following:

1. 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.

2. New versions of UCDS (v3) seems to have no libusb0.dll dependency anymore, but ftd2xx.dll dependecy still exists. FORScan has NO ftd2xx.dll distributed, it uses FTDI drivers installed in the system, if any. So if there are no FTDI drivers installed in the system (so FORScan can reach this DLL in Windows system DLL folder), FORScan may not be able to access UCDS J2534 API. Again, we consider it incorrect J2534 API implementation. However it can be easily fixed by copying ftd2xx.dll from UCDS folder to FORScan EXE folder.

3. New UCDS versions have complex anti-piracy protection system. In our tests we noticed that couple of times FORScan was unable to connect to UCDS until we ran native UCDS software that connected to their server and verified the license, also enabled CAN mode ON.
Site Admin
Posts: 2502
Joined: Fri Jun 13, 2014 2:21 am


Return to Adapters & Connection

Who is online

Users browsing this forum: No registered users and 4 guests