Tektronix and Keithley

I appreciate the response. I see that the following sequence accomplishes what I was looking for and leaves the scope running afterwards which suits my purposes well: print(scope.query(':MEASU:MEAS1:TYP RMS;VAL?')) scope.write(":ACQ:STOPA SEQ") scope.write(":ACQ:STOPA RUNST") print(scope.query(':MEA...

Hello, When I first turn on an MDO scope, don't trigger it, and, eg., query the RMS of channel 1 (`scope.query(':MEASU:MEAS1:TYP RMS;VAL?')`), I get `9.91e37` which is equivalent to a nan. This is expected behavior and, in my case, desirable. Once I acquire anything , though, I can't seem to get bac...

I guess I could use single acquisitions to ensure synchronization but it complicates my application a bit as I typically do a fair amount of adjustment on the scope manually, then run an acquisition sequence from the computer. I could have the code take over control and do a series of single acquisi...

Adding some more info: From python, I tried the following 10 times, with 's' being the scope object. print s.query(':ACQ:NUMAC?') start_time = timeit.default_timer() s.write(':CH{0}:SCA {1:.2e}'.format(1, 0.05)) elapsed = timeit.default_timer() - start_time print 'Entering loop at ' + str(elapsed) f...

I'm talking to an MDO3012 scope with pyVISA. I have a strange coordination issue. After I make a change to the voltage scale, for instance, I query the number of acquisitions (start_ac = query(':ACQ:NUMAC?')) and then sit in a while loop until the number of acquisitions equals or exceeds start_ac + ...

I've mostly got things working via PyVisa on Windows and am considering porting it to Linux/Pi but might just switch to direct ethernet control.

Thanks for the response!
Nick

Hi all- I've used PyVISA and matlab's implementation of VISA to talk to TekVISA and, in turn, a scope (TDS 3012B, MDO 3012). I'd like to do the same with a raspberry pi . Does anyone have any experience with this? I'd be using PyVISA but am not sure if there is a TekVISA equivalent for linux on an A...

Thanks very much! This makes sense.

Hi- I'm using TekVISA+Matlab with an MDO3012 scope. I query the scope with 'TRIG:STATE?', skip if 'ready', but capture the waveform with CURV if the trigger state is 'TRIG'. Is it possible to shorten the duration that the scope returns a 'TRIG' state? At times, the scope is triggered every 200-250 m...