Jump to content

Jeremy LAURENT

Members
  • Posts

    5
  • Joined

  • Last visited

Jeremy LAURENT's Achievements

Newbie

Newbie (1/4)

0

Reputation

  1. Sorry for the delay, I got heavily sidetracked. I put the latest waveform version on our test machines with the swapped FDTI driver and it seems to hold out just fine. I was trying to deal with a "Invalid device handle provided" error but it seems unrelated to the driver and caused by our own code which worked before the update and still seem to work but returns a non zero value which trips the check_error function I added while testing the driver. Thanks, Jérémy
  2. Hello @malexander, I managed to find a dowload link for older versions of libftdi2xx (http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx%{version}.tar.gz only works for version < 1.2.0). Seems like the issue is found since the version 1.1.0 (the one right after 1.04) and is still present in the latest (1.4.27). I tried a few versions in between and all of them and they all had the same issue. I'm currently testing this on a xubuntu 22.04 VM running inside Vsphere 6.7, waveforms 3.20.1 and adept 2.79.9 Here are the speed tests for the different versions of libftdi2xx: 1.0.4: 1.1.0 : 1.1.12: 1.4.24: 1.4.27 : Sources: libftd2xx release notes: https://ftdichip.com/wp-content/uploads/2022/07/release-notes.txt libftd2xx1.1.0: http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx1.1.0.tar.gz libftd2xx1.1.12: http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx1.1.12.tar.gz libftd2xx1.4.24: https://ftdichip.com/wp-content/uploads/2021/09/libftd2xx-x86_64-1.4.24.tgz libftd2xx1.4.27: https://ftdichip.com/wp-content/uploads/2022/07/libftd2xx-x86_64-1.4.27.tgz
  3. Thanks @artvvb 👍 I changed the symlink in /usr/lib64/digilent/adept from 1.4.24 down to 1.0.4 (the version bundled with adept 2.17.1) and now it works much better (connecting takes les than 3-4sec) . This seems to indicate an issue with libftd2xx > 1.0.4 indeed
  4. Thanks for the quick answer, I'll try that. BTW all the old download links for older version of adept seem to be broken
  5. Did you ever figure out why it took so long to connect on VMWare/Ubuntu ? We are currently seeing the same issue with our AD2 running on VMware vSphere 6.7. The issue is not present before Adept 2 runtime version 2.18.3 as far as we can tell. We noticed that with Ubuntu and Adept runtime > 2.17.1 the read speed is way down and connecting to the AD takes ~ 2 min.
×
×
  • Create New...