Daniel Rech

Members
  • Content Count

    27
  • Joined

  • Last visited

About Daniel Rech

  • Rank
    Member

Recent Profile Visitors

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

  1. Thank you for the quick response!
  2. Is there a document that explains the changes somewhere?
  3. Last time I checked was with Waveforms 3.3.7. Nowadays I read that Version 3.5.4 is the current version. --> Are there any changelogs available? I wasted a lot of time debugging this problem last time and I don't want to get into this again... @neoclassic I don't know if the problem is solved
  4. I didn't test your code but from my experience with high speed python variable declaration is critical: results1=[0.0]*len(rgc) ^-- this could happen before the loop --> then within the iteration you would not need to wait for the declaration. Did this solve your problem? Or did I misunderstand you question?
  5. Hi ravi_butani, I experienced similar issues with Digilent Adept 2 and a RaspberryPi 3. I think these issues might be correlated to the 4.4 kernel that is coming with it. On Beaglebone Black with a 3.8 kernel, the Digilent Adept works fine.
  6. Ok, then I'll stop trying to get it working Thank you for you help. I am using the Digilent Adept 2 with an older Beaglebone Black image (kernel 3.8) and it works perfectly.
  7. Ok, I'll look into it. The example you uplaoded uses DigitalIn. Which pins should I connect to the trigger signal? Is it wrong to use the AnalogIn to generate a trigger signal? The core of my problem is a weird behavior with Linux and kernels > 3.8. If I run my program on a Beaglebone Black with a 3.8 kernel, the triggering works fine, but if I run the same program on a Raspberry Pi 3 with a kernel 4.4 the scope seems to crash without a message. Only the dwfcmd seems to work with the kernel 4.4 system.
  8. Thank you for your response. I ended up with a solution where I don't need to compile dwfcmd. Thank you for the hint with the repository, I'll look into it!
  9. 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".
  10. 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
  11. I have the same issue but no idea how to solve it. Did you solve it already?
  12. Am I the only one who's having problems on linux systems? I still haven't figured out how to solve this.
  13. Are you using Kernel 4 or 3? My linux driver keeps crashing with Kernel 4.4.24. I'm still looking into it. Did you solve your problem in the meantime?
  14. Thank you, you help solved my problem, almost getting to 50Hz
  15. I get weird triggering behavior with the same code and 3.3 version. Not it seems that there are 400 triggers but my normal scope only shows 70 Is there an API change in 3.3 that I missed?