Counter/Timer

cancel
Showing results for 
Search instead for 
Did you mean: 

6323-counter output -from external input

Thank you

 

So i won't need a Gate input signal to run the countnuous output?.. I do not have my DAQmx Card yet to try it out ,unfortunately, but I wanted to be ready.. it's on back order

In one of the Vi's, I see the DAQmx Vi, there is a Connect Terminal source to dest.. Have u worked with this ? Will this send source PFI pulse to des tination PFI without the need of going through counter. See attachment. 

0 Kudos
Message 11 of 16
(1,543 Views)

No you won't need a Gate signal to run the continuous output.  The "gate" is open by default.  But for future reference, in DAQmx an enable/disable type of "gate" is termed a Pause Trigger.

 

I haven't worked with DAQmx Connect / Disconnect Terminals (see my previous msg #8) as I've generally preferred to do my signal routing from within a task context with DAQmx Export Signal.  But my understanding from things I've read is that:

- yes, it would route a signal from a source PFI to a destination PFI

- however, it would need to consume one of your device's counters in the process.  I don't know how DAQmx chooses which one, but I don't think there's a way to specify.  I think it just picks from what's available.

 

But again, as I also said in msg #8, why?  Wherever you intend to physically wire that "destination PFI", why not just physically wire to the "source PFI"?   The kind of signal duplication you're talking about isn't usually going to be necessary or particularly helpful, especially for systems that haven't already been wired up.

 

 

-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 12 of 16
(1,525 Views)

To answer the question, This is part of an already existing Station Test. The ctr0 (out) feeds ctr1 ,ctr2 to exercise and verify all counter operation with a scope.

0 Kudos
Message 13 of 16
(1,517 Views)

I had a chance to do a quick test with DAQmx Connect Terminals.

 

1. The good news -- it appears to replicate the source terminal signal onto the destination terminal.  I don't try to figure out how much the delay there might be (if any) between source and destination.

2. One of the device's available counters gets consumed to accomplish the routing.  In my really brief test, DAQmx

seemed to use the highest-numbered counter that wasn't already reserved for other another task.

 

 

-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 14 of 16
(1,448 Views)

Thank you for trying it out. I won't have the hardware till later in the year, so it is much appreciated.

0 Kudos
Message 15 of 16
(1,443 Views)

using 6323 counter - continuous output.

 

I would like to have 2 counter output (cntr0,cntr1) going at the same time. It seems like when the  Counter-countinuous Output - stay on. vi (below ) is done, the output turns off even if I did not call the stop task...I will call the .vi 2x- once for each counter

 

Is there a way to keep ctr0 and ctr1 going after the .vi are done ?

0 Kudos
Message 16 of 16
(1,126 Views)