Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmx freeze after 49.7 days

Hi all,

 

We use several PCI-6220 cards for doing continuous acquisition of analog signals. The data acquisition is performed by a software written in C (with Microsoft Visual C++ 2008 Express Edition) which uses NI-DAQmx v9.5.5f4 under Windows 7.

 

We have 6 systems deployed with exactly the same configuration. The problem is observed identically on all 6 systems. The serial numbers of the 6 cards are 183827D, 183818, 1838325, 18383F1, 18382FF and 1838401.

 

The file NI_configData.txt contains the information about one of the cards we are using.

 

The file Capture_Start.txt contains the sequence of function calls logged by the NI-TA software. We first do an initialization of the task, then the function DAQmxReadAnalogF64 is called every 10 ms indefinitely.

 

49.7 days after start-up of the application, the data acquisition stops for no apparent reason. No logging of the error code (if there is one) after 49.7 days was possible, as the logs are written into a circular buffer and the problem was not detected immediately.

 

We know the delay to be 49.7 days because we know quite exactly the time when the different systems are restarted and we have detailed logs about the analog values which allows us to see when the value freezes.

 

The problem can be reproduced by using the function calls in the file Capture_Start.txt.

 

Note that 49.7 corresponds to the maximum of a 32-bit integer when expressed in milliseconds.

 

Thanks in advance,

Tom

0 Kudos
Message 1 of 2
(3,999 Views)

Hi tmathes,

 


@tmathes wrote:

Hi all,

 

We use several PCI-6220 cards for doing continuous acquisition of analog signals. The data acquisition is performed by a software written in C (with Microsoft Visual C++ 2008 Express Edition) which uses NI-DAQmx v9.5.5f4 under Windows 7.

 

We have 6 systems deployed with exactly the same configuration. The problem is observed identically on all 6 systems. The serial numbers of the 6 cards are 183827D, 183818, 1838325, 18383F1, 18382FF and 1838401.

 

The file NI_configData.txt contains the information about one of the cards we are using.

 

The file Capture_Start.txt contains the sequence of function calls logged by the NI-TA software. We first do an initialization of the task, then the function DAQmxReadAnalogF64 is called every 10 ms indefinitely.

 

49.7 days after start-up of the application, the data acquisition stops for no apparent reason. No logging of the error code (if there is one) after 49.7 days was possible, as the logs are written into a circular buffer and the problem was not detected immediately.

 

We know the delay to be 49.7 days because we know quite exactly the time when the different systems are restarted and we have detailed logs about the analog values which allows us to see when the value freezes.

 

The problem can be reproduced by using the function calls in the file Capture_Start.txt.

 

Note that 49.7 corresponds to the maximum of a 32-bit integer when expressed in milliseconds.

 

Thanks in advance,

Tom




Do you have any other code other than calling the DAQmx Driver Functions? Does calling the functions in Capture_Start.txt without any additional code reproduce the issue?

 

If the issue does lie entirely with the DAQmx funcitons, it sounds like you may just have to restart your program to reset whatever counters exist in the DAQmx functions.

 

Andy F.
Applications Engineering
National Instruments
0 Kudos
Message 2 of 2
(3,946 Views)