• Content Count

  • Joined

  • Last visited

  1. Thanks for the answer, indeed it is no big deal to save this state myself. I was mostly just curious if there was a solution. I will write an email with my comments about dwf.h. Thanks a lot for your assistance.
  2. I tested the solution with the new beta, this works -- thanks a lot, it saves us a lot of hassle. It is necessary to set the "OnClose" parameter before doing the open. Am I correct in understanding that the "OnClose" parameter is now also inspected while opening a device? If so, this makes the name of the parameter a bit of a misnomer, of course.. Is there a way to get the currently programmed and active value of the DC offset through the API, after opening a device without a reset/reconfigure? As a last remark: I made a pretty eleborate Python binding to libdwf, which I plan to put on github once I'm satisfied with it. In the process of making this, I encountered a few minor issues in the header file dwf.h. Is this forum the correct place to report those issues, or should I send them to some email address? Best regards, Sidney
  3. Hi Attila, That's great! Will this feature be available in upcoming stable releases as well? For my application I need a 64-bit Linux version. Best regards, Sidney
  4. Hi, I have a question about the Analog Discover 2. I am programming it using Python. When you close a device, it's possible to keep the device running by setting the "OnClose" parameter on the device. This is useful, e.g., when the AD2 is part of a larger measurement setup. I use it in this way to set a DC voltage on the AnalogOut device. However,. when you later re-open the device, it resets the AnalogOut device, setting the output level to 0V. Is there a way to prevent this resetting behavior at open time (analogous to preventing resetting of the device at close time)? Best regards (and thanks for your wonderful product), Sidney