• Content Count

  • Joined

  • Last visited

  1. For what it's worth, I seem to get fewer errors if I use a USB hub powered with an external supply. Note: by fewer errors I mean that I'm at least able to connect to the device. dwf.FDwfDeviceOpen(c_int(-1), byref(hdwf)) if hdwf.value == hdwfNone.value: print "failed to open device" ## Doesn't happen nearly as often with external power supply quit() I'll keep an eye out for FTDI updates. Unfortunately I don't have an electronics explorer handy
  2. Funny I'm reading this now. I'm actually using a Raspberry Pi 2 with the Analog Discovery Module right now, trying to get *some* version of the Waveforms SDK to run. I had a great data acquisition program running in my Ubuntu machine and was disappointed to see that it didn't port over to the ARM architecture. I had a similar experience with the libc6 problem. Now I keep getting a "failed to open device" error, but not always. What I've done so far is installed the Waveforms 3 .deb file into my Raspberry Pi, extracted all the /usr/lib/libdwf.so* files, and uninstalled the .deb again. Next I installed the Adept Runtime and the i386 Waveforms SDK tar file into the Pi, but before running ldconfig I restored the Waveforms 3 libdwf files that I had backed up. Now it mostly doesn't work but if I run the example code AnalogIn_Sample.py, it sometimes works (kind of). Usually it says "failed to open device" but occasionally it reads a value. This is a modified version of AnalogIn_Sample which actually scans 500 samples and prints the voltages on screen. Consecutive samples often get frozen at the same value, which makes me wonder if something is interrupting the serial commands. Anyway, it's strange that the data acquisition sometimes works. I'm going to keep hacking away at it. Any advice?