Hello!
I was hoping anyone might has some ideas or knowledge about how to wire/implement the LabVIEW software of a PCI 6601 counter. Specifically, I am using a PC6-C-4-H5, which essentially takes a quadrature encoder output and converts it into the outputs of a standard up/down counter. So it takes in the channels A and B as well as the index of an encoder, and converts that into the Index, Up/Down signal and Clock output of a up/down based counter.
I've been having difficulties wiring this into my lab's PCI-6601 interface, even after searching through the manual. I've been attempting to modify code from the Counter Input: Count Edges (Finite Clock) VI example in the example finder, just to test if the counter alone is working properly, which I have not managed to get to work correctly. Based off the hardware manual of the 660x series, I have believed that in order to tie this counter output to counter2, I would need to tie that clock output of the chip to the SOURCE (2) pin, the index to the GATE (2) pin, the Up/Dwn output to the UP_DOWN (2) pin, and the clk output again to a different SOURCE pin to use as a trigger, as I've marked below:
However, running the program provides nothing but a -200284 error, which I believe correlates to the trigger not running properly? So I know that something is likely incorrect in how I've wired this system, but I haven't been able to find anywhere in the documentation that goes this specific issue, so I wanted to ask if anyone here had experience in this type of chip/wiring setup.
Sorry if this is a basic question, I just haven't found anything on it. Thanks in advance for any advice people have!
For reference, the exact error was:
Error -200284
Possible reason(s):
Some or all of the samples requested have not yet been acquired.
To wait for the samples to become available use a longer read timeout or read later in your program. To make the samples available sooner, increase the sample rate. If your task uses a start trigger, make sure that your start trigger is configured correctly. It is also possible that you configured the task for external timing, and no clock was supplied. If this is the case, supply an external clock.
Property: RelativeTo
Corresponding Value: Current Read Position
Property: Offset
Corresponding Value: 0
Task Name: _unnamedTask<348>