Search the Community
Showing results for tags 'dwfcmd'.
Found 3 results
I have a weird issue with my Analog Discovery 2 and I was wondering if there are ideas out there how to track it: I use a Digilent Adept with the Waveforms 3.3.7 software on linux. It seems to work fine but does not detect my triggers. If I use the provided pyhton examples or C examples trigger detection does not work meaning the program just stays in "Waiting for trigger" state all the time. But if I use the dwfcmd: cd /usr/share/digilent/waveforms/samples/dwfcmd && dwfcmd analogintrigger.txt I get one trigger without a problem. It took me so much time to detect this behavior and now I don't have any idea how to solve this. The dwfcmd is not powerful enough for my application but maybe I'll end up modifying the code to fit my needs. I'd really like to keep using python, any ideas what I am doing wrong or any known bugs? Thanks Daniel Rech
I found the dwfcmd in /usr/share/digilent/waveforms/samples/dwfcmd/dwfcmd.cpp. How do I compile this file? g++ throws many errors starting with "ISO C++ forbids forward references to 'enum' types" and "use of undeclared identifier".
Searched for this issue but couldn't find any earlier queries. I've just installed the software tree up through waveform3 on a debian box. Dwfcmd returns nothing when I run it as an unprivileged user but gives the correct result (finds the Analog discovery) if I run it as root. Same is true for my python scripts that access the AD. Is there anything I can do to be able to access the AD as a normal user? Thanks. O/S details are: Description: Debian GNU/Linux 7.9 (wheezy) Linux debian73-Iguana 3.2.0-4-686-pae #1 SMP Debian 3.2.73-2+deb7u2 i686 GNU/Linux libc is 2.21