Is digital change detection supported in PCI-6259 M-series?

[Des A.]

I am trying to set up a series of timed loops in LabVIEW 7.1 using DAQmx 7.3, triggering off of rising and falling edges of a digital input signal. I am getting an error in "DAQmx Create Timing Source" when I try to set the instance to "digital change detection", saying that this feature is not supported by my hardware. The specification for the PCI-6259 board indicates that Port 0 is capable of digital change detection, so I'm wondering what I'm doing wrong.

If I use the "digital edge using counter" option instead, the program works...however, I need to trigger digital pulse generation events on both the rising and falling edges of my clock signal, so the PCI-6259 does not have enough counters to do this. Suggestions?

Des A.

[sergesl]

Hello Des. A

Although this feature is supported in hardware, the current version of the driver does not support it since the driver was out before M Series devices. A future version of the driver will allow you to benefit from this hardware feature.

[Des A.]

Hi Serges...if the feature is not supported by the current driver, that should have been clearly stated in the specification for the PCI-6259. This is the second such problem I've had with this board (the specification also doesn't state that you must have Labview 7.0 or 7.1 to use the board). When the specification does not provide a true description of the currently-supported features and software requirements, it leads to wasted time trying to debug problems that actually have no solutions. In my particular case, I now have to redo a large section of my Labview code since I was counting on using change detection (I tend to believe specifications when I read them).

Are you able to say when the new driver that supports change detection on the PCI-6259 will be released? Are we talking about weeks, months, years, or is it an unknown?

Thanks,
Des A.

[sergesl]

Hello DesA,

Our appology for the lack of clarification. We are continually working to make sure that you get the right information when needed. In this direction, this documentation error has been detected and corrected for future releases.
Regarding the release date for the version supporting change detection, there is not set date. So I really could not give you even an estimate. But it will be added to a future release.
Sorry again for the inconvenience.