07-14-2015 01:01 PM
I just found the pinout for the 6535. For acquisition clock, you actually need to use PFI5.
07-14-2015 01:10 PM
07-14-2015 01:13 PM
The DLL I'm referring to is the one supplied with the "Traditional NI-DAQ" that pre-dates DAQmx. This DLL does not work with Windows 7 64-bit.
It did indeed support the clock signal as described. In fact, we still have a legacy machine running Windows XP that works fine, though its rather long in the tooth.
07-14-2015 01:22 PM
I believe we're using 7.4.1. But, the actual board is a PCI-6534, which is functionally the same. I specified the 6535 for my example because it is easy to set up a virtual device in MAX, and both boards are supported by DAQmx.
07-14-2015 05:15 PM
@DennisW wrote:
But, the actual board is a PCI-6534, which is functionally the same. I specified the 6535 for my example because it is easy to set up a virtual device in MAX, and both boards are supported by DAQmx.
Wait a minute. That is a HUGE difference in hardware. The pinouts are not even the same.
But still, from what I can find, the sample clock can only be in PFI2, PFI3, PFI6, or PFI7. So I'm back to the fact that if your clock signal is going into P0.1, then there must be some software processing the data coming in to get the data at the sample clock.
07-14-2015 05:55 PM
Well, OK. I figured that what works for the 6535 should work for the 6534 - in the virtual world, and for my simplified example, at least. And re-creating my virtual device as a 6534 yields the same result. But, I take your other point about the sample clock. Perhaps the ancient runes (documentation) for my actual device are incomplete, or just wrong. Guess I gotta take the lid off and trace some wires...
Again, thank you for your assistance!