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?
Question
Daniel Rech
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
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.