tmnoble
2007-05-03 00:10:08 UTC
Does my Sample Clock need to be running before I call niHSDIO_Initiate???
I am using dynamic acquisition of Sample Clock on the STROBE port.
I used niHSDIO_Initiate and niHSDIO_Fetch instead of the atomic niHSDIO_Read operation
because I use GPIB to tell the PC when to start niHSDIO_Initiate and then start my DUT
running, and then call niHSDIO_Fetch to finish the acquisition and transfer the data.
My external clock from the DUT into the STROBE port is not intially running and
intermittently stops and starts. Every time I see a rising clock edge on STROBE,
I want to sample the data on DIO15..0. I used to do this with NI-DAQ all the time.
When I call niHSDIO_Initiate with I get the error below.
DAQmx Error -200586 occurred:Hardware clocking error occurred.
If you are using an external sample clock, make sure it is connected and within specifications.
If you are generating your sample clock internally, please contact National Instruments Technical Support.
Device: Dev1
I am using dynamic acquisition of Sample Clock on the STROBE port.
I used niHSDIO_Initiate and niHSDIO_Fetch instead of the atomic niHSDIO_Read operation
because I use GPIB to tell the PC when to start niHSDIO_Initiate and then start my DUT
running, and then call niHSDIO_Fetch to finish the acquisition and transfer the data.
My external clock from the DUT into the STROBE port is not intially running and
intermittently stops and starts. Every time I see a rising clock edge on STROBE,
I want to sample the data on DIO15..0. I used to do this with NI-DAQ all the time.
When I call niHSDIO_Initiate with I get the error below.
DAQmx Error -200586 occurred:Hardware clocking error occurred.
If you are using an external sample clock, make sure it is connected and within specifications.
If you are generating your sample clock internally, please contact National Instruments Technical Support.
Device: Dev1