http://forums.ni.com/t5/Multifunction-DAQ/Can-6014E-generate-an-interupt-when-the-terminal-count-is/m-p/93054I have found above and need assistance to generate toggle at output pin of counter when terminal count is reached. I opened two NI MAX, and use one to generate a counter input task with initial count as 5, counting down direction. Use another NI MAX to monitor the output pin (PFI12 for Ctr0 in my case). I have supplied an external contineous pulse source to the source pin of Ctr0. I would expect to see a pulse or toggle at the output pin of Ctr0 when the count rolls over zero. However, there was no signal generated at output at all and I have verified that with a oscilloscope. It remains the same scenario when I set a large initial count and counting up. Could anyone help in addressing how I can program the counter to output a pulse (or toggle) when TC is reached using DAQmx and how I can set up a simple test to pick out Terminal Count? By the way, my card is PCIe-6363.Thank you.

Multifunction DAQ

Terminal count is reached for counter Input task

I'm inclined to expect there's a way to do the same kind of thing in C that I posted earlier in LabVIEW. Unfortunately, I know little about the syntax. Just an observation that the DAQmx API's for both LabVIEW and C-family coding seem to be generally congruent. It's rare that a hardware feature is exposed via one and not the other.

Over on the LabVIEW side, there are also a number of restrictions about combining properties for CI and CO in the same task. In fact, you generally can't. Sometimes I just try stuff, partly b/c I still remember the hardware features available through the old driver back in Y2K era and figure most of them are probably still supported *somehow*. In other words, I agree it isn't obvious on the surface how to determine what combinations of properties are allowed. I wouldn't say you're missing anything, at least not anything you should expect to notice.

Here, I suspect after the fact that there's a clue in the property name. The specific important distinction appears to be that the Output Terminal and Behavior properties are categorized in terms of signal routing ("Export Signal property node") rather than directly in terms of an output task. That's a bit of a guess though. All I'm sure of is that the code I posted worked the way I described. I expect there's a way to program the same behavior in C but I couldn't do it myself.

Anyone else out there know the C syntax for this?

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.