Labview does not wait for TDS 1012B trigger before acquiring data

[dmerthe]

I have written a VI which, at its core, is very similar to the example "TDS 1000 Triggered Acquisition" VI. It initializes the scope, configures the channel, timebase and trigger and then runs the Read VI. The data from that is plotted in an XY Graph. However, when I run the program, it does not wait for the scope to trigger - it just records and plots whatever is currently on the scope (from the previous acquisition) and then stops the scope.

In fact, when I run the example "Triggered Acquisition" VI, it does the same thing.

How can I get it to wait for the scope to trigger before acquiring the data?

[billko]

---

@dmerthe wrote:

I have written a VI which, at its core, is very similar to the example "TDS 1000 Triggered Acquisition" VI. It initializes the scope, configures the channel, timebase and trigger and then runs the Read VI. The data from that is plotted in an XY Graph. However, when I run the program, it does not wait for the scope to trigger - it just records and plots whatever is currently on the scope (from the previous acquisition) and then stops the scope.

In fact, when I run the example "Triggered Acquisition" VI, it does the same thing.

How can I get it to wait for the scope to trigger before acquiring the data?

---

Apparently you're not telling to to trigger on a sweep, and you should probably go tell it to.  Seriously.  Okay, well semi-seriously.  😉

Can't really say more without actually looking at the code.

[dmerthe]

Thanks for the response. I'm using the high level Tektronix VIs and they don't really give many options for the trigger setup. I would appreciate any advice.

Here's the code.

[billko]

Timing is everything.  Of course when I read this, I no longer have access to a computer with LabVIEW on it.  😕

I'm fairly certain that Tektronix would not leave such a basic function out of their drivers.  Maybe you overlooked it?