Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmxResetCOPulseTerm is not working as expected on USB6216 (NIMAX 21)

Solved!
Go to solution

Hi,

 

I expect DAQmxResetCOPulseTerm to disconnect a signal from a counter </ctr0>. But, if I look with DAQmxGetCOPulseTerm (), I see it is disconnect but not on the hardware side.

 

If I switch from PF9 to PF10 using DAQmxSetCOPulseTerm, but now, both is outputting the signal.Then PF10 to PF11, all three are now outputting the signal.

 

I tried DAQmxResetCOPulseTerm, and all three PF are still outputing the signal. The only way I found is to reconfigure the signal on a digital output.

 

Germain

 

 

0 Kudos
Message 1 of 2
(788 Views)
Solution
Accepted by topic author Sheppard74

Not a solution, but for more info search for the term "lazy uncommit".  You already found one of the workarounds, and you probably can't really do any better than that.

 

 

-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.
0 Kudos
Message 2 of 2
(757 Views)