• Content Count

  • Joined

  • Last visited

About AndrewSM

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For anyone else having a similar problem I found a workaround, though it's a little strange. Install the glibc 2.14 library in parallel in an alternate location. I put mine in a folder in the root directory. The libdwf.x.x.x binary does not look for the glibc-2.12 library directly. It looks for a symbolic link file named in directory /lib64. That file redirects libdwf.x.x.x to the glibc library. Now if you modify to point to the new glibc library, you will have major problems because many systems in the computer rely on the current installed version 2.12 (I got a kernel panic and had to use a recovery disk to revert my changes...). Instead of modifying, make a new symbolic link file in the same location that points to the new library. I named mine "". But libdwf.x.x.x will still look for instead of the new file so you have to open it in a hex editor and modify it. All I had to do was Ctrl-f for "" and change the 6 to a 7. After all that it works! I think you could also modify a binary in the same way to get the waveform GUI application to work. Try running if from terminal and look at the errors to find whatever file is looking for the glibc library and modify it to look for instead of I havn't gotten around to it though since I just need to run python scripts.
  2. Hi, I'm a grad student in a university lab working on superconducting nanowire single photon detectors (SNSPDs). We've been using an analog discovery 2 for testing these devises and so far it's been very handy. A lot easier and more intuitive than the other heavyweight scopes we have around. I'm working on getting custom python scrips to run on it so we can automate a lot of our tests. Andrew
  3. Hi I’m having trouble getting the waveforms sdk to work with my analog discovery II. I have the Adept runtime & Utilities installed with the FTDI drivers. The analog discovery shows up when I run this command: $ dadutil enum So I don’t think it’s a USB driver issue. I’m using Red Hat Enterprise 6.10 with glibc 2.12, which may be the source of my problems. I’m trying to run python scripts from the example folder (with python 2.7). When running the latest versions of Adept 2 runtime, I would get errors from the libdwf.x.x.x about missing the required glibc 2.14 library. When running older versions of the runtime, I would not get those explicit errors but the script would never find and connect to the analog discovery. Is there a way to run the scripts without updating glibc for the whole system? I’ve learned that just updating glibc is a disruptive change that could break other statically and dynamically linked binaries on the system (and this computer is used for a bunch of other stuff in our lab). I can download another version of glibc but I don’t know how to direct the libdwf.x.x.x to use it. Thanks! Andrew