Showing results for 
Search instead for 
Did you mean: 

Emulating NI-SCOPE SGL Trigger in LabVIEW+TestStand



I am attempting to emulate the SGL trigger mode from the SCOPE Soft Front Panel using Labview and TestStand.  In my TS sequence, I have a VI to configure the trigger, then I apply a single pulse to the scope, and then I read the scope measurement.  However, I find that I must keep applying the pulse or the measurement info will be gone by the time I get to the "read measurement" step.  Is there a way to ensure that the scope trace is preserved from a single trigger?  (I have learned that the SGL trigger mode from the SFP is not directly replicable in LabVIEW).  Or, is there a better way of doing this?


Billy Maier

0 Kudos
Message 1 of 5

Lets see how you are implementing this.  If I had to guess (I don't have to if you share more info) I'ld say that the NI-Scope vis are being unloaded by TS

"Should be" isn't "Is" -Jay
0 Kudos
Message 2 of 5

Sorry, I wasn't sure if the text description would be enough.  Attached is the image of the sequence I'm using (the pulse generator is currently controlled externally, the user sends the pulse during the message popup titled "Send Pulse").  Also included are images of the "Arm Scope" vi (the first step in the sequence) and the "Get Measurement" (misspelled in the sequence) vi.  Also attached is an image of our channel configuration VI, which is the sub-VI in "" which has the default icon.


The final popup only shows the measurement recorded.  Let me know if any further info would be helpful.




0 Kudos
Message 3 of 5

Those Images don't show a whole lot.


Oddly, the Get Meaurement (SIC) Step is of type "Action" and therefore has no "Result."


Could you post code rather than pictures?

"Should be" isn't "Is" -Jay
0 Kudos
Message 4 of 5

Sure, VIs are attached.  To clarify, at the moment I'm not attempting to get a TestStand result from that step, I am just storing the result in a variable that I then show in a popup.

0 Kudos
Message 5 of 5