09-22-2007 01:17 PM
09-24-2007 11:18 AM
09-24-2007 01:07 PM
Thanks Chris,
Yes I am using the following:
Express Work Bench 1.5.0 Signal Express 1.2.0 Tek Edition 1.1.0
Tek TDS2024B scope USB
My problem is that the steps repeat continuously even if there has not been a newly triggered scope event to look at. This repeating loop piles on to the appended output file (or adds the next named output file) continuously repeating the same scope data. So I think I need a step to querry the scope to see if it has been triggered before repeating the acquire input step and generate output step.
By looking at the scope and using OpenChoice Desktop to look at settings their are four states of interest. I think I want to be in the first or second state. In the first state I wait. Iin the second state I do the acquire input & generate output steps and wait again until querries of the scope return acquired status.
Single Sequence Ready
:ACQUIRE:STATE 1;
:ACQUIRE:STOPAFTER SEQUENCE;
Single Sequence Acquired
:ACQUIRE:STATE 0;
:ACQUIRE:STOPAFTER SEQUENCE;
Run/Stop Ready
:ACQUIRE:STATE 1;
:ACQUIRE:STOPAFTER RUNSTOP;
Run/Stop Stopped
:ACQUIRE:STATE 0;
:ACQUIRE:STOPAFTER RUNSTOP;
Note: I put in a request here at work for a LabView license seat so I can learn how to create a user defined VI to querry the scope.
Thanks!
09-24-2007 01:13 PM
...plus, the acquire input step available in WorkBench Express/SignalExpress/Tek only knows about normal trigger and auto trigger, not single sequence. So once a triggered event comes in, the scope goes from "Ready" to "Trig'd" and immediately back to "Ready". Thats why I think I need the single sequence and acquired status.
Bob
09-26-2007 10:51 AM