Software Triggering a NI USB-5133

[RTSLVU]

I have been trying to understand how to software trigger a USB-5133 using Ni Scope in LabVIEW

I have tried all the Software trigger settings and can not figure out how to trigger the scope.

So far every attempt results in this error:

I have tried troubleshooting using the Acquisition Status VI in a loop and it always returns Acquisition in progress, meaning the 5133 is not being triggered.

What am I doing wrong here?

[santo_13]

Please share the VI in a older version.

[RTSLVU]

---

@santo_13 wrote:

Please share the VI in a older version.

---

I would love to but...

Here's a picture of what I am trying, all the VI's are part of the NI-Scope toolkit.

[Gregory · Accepted solution]

I would try a delay between "initiate acquisition" and "send SW trigger". Or, you can set the Pre-Trigger time to 0%. Can you try these?

[Gregory]

Actually, on the "Send Software Trigger" VI, use the input to make it a "Reference Trigger" rather than the default of "Start Trigger".

[RTSLVU]

---

@Gregory wrote:
I would try a delay between "initiate acquisition" and "send SW trigger". Or, you can set the Pre-Trigger time to 0%. Can you try these?

---

%0 pre-trigger had no effect

I also tried inserting a delay but gave up at 5 seconds between starting acquisition and sending the software trigger.

No cigar...

[RTSLVU]

---

@Gregory wrote:
Actually, on the "Send Software Trigger" VI, use the input to make it a "Reference Trigger" rather than the default of "Start Trigger".

---

That was it,  I swear I tried that yesterday.

[RTSLVU]

---

@RTSLVU wrote:

---

@Gregory wrote:
Actually, on the "Send Software Trigger" VI, use the input to make it a "Reference Trigger" rather than the default of "Start Trigger".

---

That was it,  I swear I tried that yesterday.

---

It doesn't work anymore?

I don't understand how something so simple can be so unreliable. 

[RTSLVU]

Okay with a clear head this morning I figured this out, it was a combination of initially using the wrong trigger and then not waiting for the scope to be ready to trigger.

I added a VI that takes my selected Time/Div and Pre-Trigger, then calculates the time to wait for Pre-Trigger data to be acquired before advancing the software trigger.

But this brings up a question that I remember having when I first started with Ni-Scope

Why is there no way to determine Trigger Status? 

No, Acquisition Status? is NOT the same thing.

As Acquisition Status only tells you if acquisition is complete. I suppose you could say if it's not complete then it is still "waiting for trigger", but you could be wrong.

Specially in the case of a slow acquisition (seconds/div).

Any modern DSO I have used had a VI to determine Trigger Status and would return several states.

Such as:

Stopped (Acquisition complete)

Ready, Armed, or Waiting (pre-trigger acquisition complete, waiting for trigger) 

Pre-trigger (pre-trigger acquisition in process)

Triggered (Post trigger acquisition in progress)