Does "pause trigger" have a status flag?

[oryan]

Hi,

I am using a BNC2110 with PCI6133 multifunction DAQ card. I am reading random analog voltage pulses on one channel for now, and using the "Pause Trigger" properties (on trigger property node) so that the read task only takes in samples from the pulses, and not samples of the baseline noise between pulses.  This works ok. But is there a way of signalling when the pause trigger has actually started and stopped (at the rising and falling edges of a pulse, respectively)? I want to use these signals to index the collected data so that I know where in the data any one pulse starts and ends, and so keep all pulse data separate, but in one array.

Many thanks,

Oliver.

[muks]

---

But is there a way of signalling when the pause trigger has actually started and stopped (at the rising and falling edges of a pulse, respectively)

---

The signal for flag status can be generated  i suppose

[oryan]

How do I generate a signal/flag when the trigger pauses data acquisition?
Thanks.

[oryan]

Hi, I have attached a VI from the NI website which shows what I'm doing with the pause trigger and read task. I need to find a way of sending up a signal every time the pause trigger actually pauses/unpauses the read task and while loop. The while loop iterates for an unknown number of times depending on the length of the input data pulse (which is random in my case) above the trigger level, the sample rate, and the number of samples to read.

Thanks, Oliver.

[BeejalS]

Hi Oliver

One thing you could do it to look for a timeout error to flag when a pause occurs. The time-out error code is -200284. If you set the timeout value to the minimum (1) you can keep checking for the timeout and set a boolean to true when a timeout occurs. So if the boolean is true you know you have a pause, if the boolean is false you know you are reading in the signal.

I have adapted the vi that you posted to do this and attached it below.

I hope this helps

Thanks

[oryan]

That really does help, thank you. What could be done if the pauses are less than a second long (which I have to account just in case)? The timeout error won't happen in that case.
Oliver.

[BeejalS]

Hi Oliver

I have just checked and you can actually set the timeout to a minimum of 0.01 so this gives you a minium pause time of 10ms. Will this still be too long?

Thanks

[oryan]

Perfect! That should do the trick, allowing up to 100 pulses per second to be read. Thank you!

Out of interest, would there be another way to allow for more pauses/pulses? If not, no worries. I'm just looking to over-engineer it to account for all possibilities.

Oliver.

[BeejalS]

Hi Oliver

I don't think you could allow for more pauses using the timeout method. You could maybe explore the possibility of reading in the trigger waveform on another channel and comparing the two. I am not sure if this would be more accurate though.

Thanks