NI PXI 6259 sample clock

[pingjockey]

We are using a NI PXI-6259 to capture several channels of analog and digital data.  We have set up the Sample Clock routed to PFI6 which is physically connected to APF0 for use as a trigger.  This vi was successfully ran as recently as last December/January, but when I run it now, no data is collected and I see the error

 -200284

“Some or all of the samples requested have not been acquired…”

Using an external scope to observe the PFI6 output I can see the signal going high to +5 vdc but a clock is never being generated.  I have tried 2 additional NI PXI 6259 boards and seen identical results.  I have also tried downloading an example vi (200306.vi) from the NI web site that uses many of the same functions and again saw the same results. 

It appears to me that the NI PXI-6259 boards are themselves the fault, but I am having a hard time believing that 3 separate boards all have the same failure.

I have attached a “scaled down” vi (untitled 1.vi) which contains the sections of code I think are relative to the problem.  I have also included the 200306.vi mentioned above.

Thanks for the assist.

[Izzzzz]

Hello pingjockey,

The error you are getting is a timeout error which occurs when the DAQmx Read waits for 10 seconds (the default setting) and does not see any samples to read.  

1. This Knowledge Base Article discuses reasons you may be getting this error.
2. From taking a look at your code (Unitled 1.vi) it seems you are only allowing 4 seconds to receive the trigger and collect all the samples?
3. Why are you disconnecting the sample clock from the PFI6 input before the task even starts? How are you ensuring the trigger ever gets to the PFI6 when your task starts looking for a trigger?
4. Your device is only capable of performing correlated DIO thus there is no direct DI sample clock.
5. To better assist you could you give me more information on the project you are working on with the PXI-6259. There might be a better way of getting back to the original functionality. I know this is a step back but it is hard to discern from the code posted what may be causing this issue.

Best Regards,

Izzy O.

Applications Engineer

National Instruments

www.ni.com/support