• Content Count

  • Joined

  • Last visited

  1. Attila, Is there a new .Impedance script object? The 3.6.8 docs don't show this. Craig
  2. Ahhh, so the impedance analyzer computation uses only the scope output available via the SDK (which calls the dwf). OK, I got it. Thanks for the clarification. BTW, I haven't had access to an impedance analyzer since 1988 with a HP4192. Having one again allows for an interesting and informative understanding of tube amplifier design. Thanks, love that AD2.
  3. Dear Digilent, I've been exploring the 3.6.8 features and love the impedance analyzer. What's the schedule for updating the Waveforms SDK and its Reference Manual? I'm very interested in automating some impedance measurements using python. If this has been done already, I apologize for not finding and asking this question. Thanks for the awesome tool. Craig ps. here's my video I created a couple days after 3.6.8 release, Analog Discovery 2 Impedance Analyzer, OPTs and What Tube Plates Really See!!!
  4. Thanks for reading all these, I figured out a lot in this single acq mode configuration. from the sdk doc, FDwfAnalogInTriggerPositionInfo returns the minimum and maximum values of the trigger position in seconds. The horizontal trigger position is used for Single acquisition mode and it is relative to the buffer middle point. From a GUI perspective I can see why this important, pre and post trigger data display. From a data analysis perspective this a little messy to figure out the position value exactly such that only post-trigger data is returned. Or is it? I mess around and post here
  5. Now I'm back to figuring out why my data has the trigger point in the middle of my array.
  6. OK, I got it. I had to set FDwfAnalogInTriggerHysteresisSet to 0.01, this fixes the rise/fall inconsistency issue. Digilent, please add dwf.FDwfAnalogInTriggerHysteresisSet(hdwf,c_double(0.01)) to AnalogIn_Trigger.py example
  7. I discovered that calling dwf.FDwfAnalogInReset before I setup or acquired data was affecting the trigger performance. Removed that and the middle point in my array is now near the trigger level. Now my problem is trigger.condition = trigcondRisingPositive isn't consistent. I get both rising and falling values at the array mid-point.
  8. OK, I was looking at my same signal's data arrat in waveforms. I think the center value of the returned data array is the trigger point value. Is this true? If this is the case, how is the timestamp for data array values computed or acquired? Thanks.
  9. Folks, I'm looking at data from the example code, AnalogIn_Trigger.py. I made it simpler by removing the average loop, now just prints a single post-trigger dataset. I have the following 1KHz 2Vrms attached to ch1 dwf.FDwfAnalogInTriggerAutoTimeoutSet(hdwf, c_double(0)) #disable auto trigger dwf.FDwfAnalogInTriggerSourceSet(hdwf, trigsrcDetectorAnalogIn) #one of the analog in channels dwf.FDwfAnalogInTriggerTypeSet(hdwf, trigtypeEdge) dwf.FDwfAnalogInTriggerChannelSet(hdwf, c_int(0)) # first channel dwf.FDwfAnalogInTriggerLevelSet(hdwf, c_double(1.20)) # 1.2V dwf
  10. Folks, I'm writing a python object for the AD2 trigger, when I set the autotimeout value with dwf.FDwfAnalogInTriggerAutoTimeoutSet isn't returned with FDwfAnalogInTriggerAutoTimeoutGet. My unittest sets autotimeout value to 1.213, get returns 1.25494304. do autotimeout values have to be some subdivided range of values? @property def autotimeout(self): v = c_double() self.dwf.FDwfAnalogInTriggerAutoTimeoutGet(self.hdwf,byref(v)) return v.value @autotimeout.setter def autotimeout(self,value): self.dwf.FDwfAnalogInTriggerAutoTimeoutS
  11. does winpython help with python lib installs on cygwin?
  12. Attila, I'm sitting now in front of win7 waveforms. shift and ctrl zoom modifiers do have an effect but all three move the trigger position, not desired. When I set the trigger/horizontal position, it should stick regardless of timebase value like a scope. Neither of these modifiers step through the pop up menu selection. Does someone actually want a timebase of 348ms/div? If so, let them type it in. The alt modifier quickly will move the horizontal position back to its location, so that's nice. All this gripping applies to y axis mods as well. Do people actually want 366mV/div? if s
  13. Attila, Sorry for the late reply. Thanks for the tips. I'll try out the shift and ctrl zooming and animation disabling as you mentioned. I'll see if I can zoom without moving the trigger point. I've worked with linux waveforms for hours in past couple weeks and will get back with more specific suggestion towards faster user interface. Oh, one quick thing that won't impact screen optimization much is adding scaling label for both channel 1 and 2 simultanously, I know you can switch the yaxis labels by clicking on a trace. Most of the time your comparing wave 1 to wave 2 and need to se
  14. Folks, I'm forced to use a win7 host for something (I've been a desktop linux-only for about 15 years). I'm working with an analog discovery 2 kit and wanted to develop using vi on cygwin which is quite lovely. Start with this post, https://www.codefull.org/2015/12/installing-scipy-numpy-and-matplotlib-under-cygwin/ after you install numpy, pip exits without errors but continuing install results in a lapack error something like this from numpy.linalg import lapack_lite, _umath_linalg you need to add /usr/lib/lapack to your PATH. export PATH=$PATH:/usr/lib/lapack