Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

Counter Output Pin on PCI-6229

I am using NI-DAQmx 7.3 C API with (among others) a PCI-6229.

I have used DAQmxSetCOPulseTerm() to connect a counter output to a terminal other than the default. It seems to work- the output pulses do, in fact, appear at PFI 6 (the terminal I'm using for testing). But the pulses continue to appear at the default output pin as well.

Is that expected?

In order to reverse the situation, I used DAQmxResetCOPulseTerm() just before calling DAQmxClearTask(). The function returns zero, but if I subsequently make a new task to do pulse output from the same counter, pulses appear at both PFI 6 and at the default pin.

Am I missing something?
John Weeks

WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
www.wavemetrics.com
0 Kudos
Message 1 of 3
(3,118 Views)
Hi John,

I would suggest using the DAQmxTristateOutputTerminal. I have tried what you are doing in LabVIEW and I'm seeing the exact same results. When I set the default pin to tristate, the counter output does not show up on it.

-Sal
Message 2 of 3
(3,106 Views)


@salvador Santolucito wrote:
Hi John,

I would suggest using the DAQmxTristateOutputTerminal. I have tried what you are doing in LabVIEW and I'm seeing the exact same results. When I set the default pin to tristate, the counter output does not show up on it.

-Sal




Thanks for trying it and confirming what I saw, and thanks for the pointer to DAQmxTristateOutputTerminal.
John Weeks

WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
www.wavemetrics.com
0 Kudos
Message 3 of 3
(3,101 Views)