I am translating a Traditional DAQ Counter application to DAQmx. The old hardware was a PXI-6602, the new hardware is a PXIe-6614. Both have 80 MHz clocks. They are very similar hardware devices.
I'm not a counter expert, but I'm pretending for this application.
One of the counters is used for "gated event counting", where the counter counts down a specified number of 80MHz clock while the gate is high, and toggles the counter output when the counter reaches zero. Here's a subset of the Traditional DAQ code. (I didn't bother with a snippet, since most people don't have Traditional DAQ installed.)
My understanding is that the "internal max timebase" will be 80M, which is then set as the "source selection".
Based on this post, I tried:
(Oops, I just now realized that these snippets left out the "Start", but the read autostarts, so it returns the same error. This was a test VI that I derived from my actual code.)
This returns an error:
Error -200452 occurred at Property Node DAQmx Channel (arg 1) in Test GEC.vi Possible reason(s): Specified property is not supported by the device or is not applicable to the task. Property: CI.CtrTimebaseRate Channel Name: Dev1/ctr3 Task Name: _unnamedTask<52>
I've also read this post: Why Can't I Choose the Internal Clock in DAQmx Counter Input Example Programs?
I am using all 8 counters and don't have a spare counter to recreate the 80Mhz clock.
Here are a couple of other things I've tried, to no avail:
Calling the DAQmx Timing VI, which returns a similar error:
Error -200303 occurred at Test GEC.vi Possible reason(s): External sample clock source must be specified for this application. Unspecified Property: SampClk.Src Channel Name: Dev1/ctr3 Task Name: _unnamedTask<53>
And also trying to use the CountEdges terminal to /Dev1/Ctr3SampleClock, which returns the error
Error -89136 occurred at Test GEC.vi Possible reason(s): Specified route cannot be satisfied, because the hardware does not support it. Property: CI.CountEdges.Term Property: CI.CountEdges.ActiveEdge Source Device: Dev1 Source Terminal: Ctr3SampleClock Task Name: _unnamedTask<55>
Given that this was possible with Traditional NI-DAQ, I assume that I'm just missing something obvious.
But given that there's a KB entry that implies that you have to use an extra counter, I'm worried.
Another part of my app needs to use "CI Two Edge Separation", and I think it will have the same problem. I want to count the 80 MHz clock in between two pulses.
Any ideas?