6602 on Traditional DAQ : can't assign gate(0) to source input of counter (0)?

Question

We are replacing a system that used PC-TIO-10 boards with 6602 boards.
In an attempt to minimize system changes, the new system has been wired
identically to the old system, which used the gate lines to count by
opening the gate on the rising edge of the gate line and counted on the
falling edge.
Apparently, we are prevented from using the gate line as source to a
counter. It is confusing enough that the manual says each of the fourty
counter I/O lines can be assigned to any of the counters and any of the
counter functional inputs: I still don't know if this is true or if it
is an improper interpretation of the manual.
Additionally, using DAQ 7.4, we are specifically limted to using source(x) lines as source inputs to the counters.
a) Is it really not possible to connect a gate() line to the source input of the same counter?
b) If so, is it possible to connect the gate(x) input to the source
input of counter(x+1) or (x-1) without affecting counter (x), which is
how it appears in the VI's?
c) If worse comes to worse, we are driving the gate inputs with the
output of an MC14490 hex contact bounce eliminator. Can we tie the gate
and source inputs to a single counter together, and in software set the
source as input and set gate on, and count events that way?
and I guess,
d) we're hopelessly  crazy and misinformed, and have to remake the
interface boards and/or completely rewrite the software to use DAQmx?
ray

Answer 1

We are replacing a system that used PC-TIO-10 boards with 6602 boards. In an attempt to minimize system changes, the new system has been wired identically to the old system, which used the gate lines to count by opening the gate on the rising edge of the gate line and counted on the falling edge.
I don't understand the function you were accomplishing.  What do mean by "opening the gate" on the rising edge?
It is confusing enough that the manual says each of the fourty counter I/O lines can be assigned to any of the counters and any of the counter functional inputs: I still don't know if this is true or if it is an improper interpretation of the manual.
No, the assignments are not that flexible.  However, you certainly can assign any counter's default source pin to be used as a source by any other counter's task (or by several tasks at once).  There are a few other special-case assignments, but for the most part they are flexible within their own category.  Any source pin can be the source for any counter, any gate pin can be the gate for any counter, etc.
a) Is it really not possible to connect a gate() line to the source input of the same counter?
b) If so, is it possible to connect the gate(x) input to the source input of counter(x+1) or (x-1) without affecting counter (x), which is how it appears in the VI's?
c) If worse comes to worse, we are driving the gate inputs with the output of an MC14490 hex contact bounce eliminator. Can we tie the gate and source inputs to a single counter together, and in software set the source as input and set gate on, and count events that way?
a) I'm not at hw now and can't recall for sure about using a counter's own gate signal as a source.  See b).
b) I'm pretty sure a counter can use as its source the gate signal from its paired counter (x+1 or x-1).
c) Um, it isn't clear to me why you need both source and gate connected this way if you are just counting events.
d) we're hopelessly  crazy and misinformed, and have to remake the interface boards and/or completely rewrite the software to use DAQmx?
I don't think so.  If the PC-TIO-10 was just performing event (edge) counting, then you shouldn't need to worry about the gate inputs on the 6602.   The new counters can simply count source edges without regard to a gate input.
Can you describe how the source and gate inputs were used to accomplish the measurement you needed on the PC-TIO-10?  It's been a long time since I used one and I only ever used it for period measurement...
-Kevin P.