Getting Intermittent Error -200010 from SCXI-1600

[Phillip_Neir]

I am running an application that does both acquisition and control. The hardware consists of SCXI-1000, SCXI-1600, SCXI-1100, SCXI-1126 (5), SCXI-1160, SCXI-1124, SCXI-1162HV, and GPIB talking to two HP 6031 power supplies. The software is LabVIEW v7.1and NI-DAQ 7.5. The acquisition rate is 50S/s. The application reads all data points (points to read -1) every 100ms. The outputs are written every 200ms. Every once in a great while an error dialog pops up with error -200010 (onboard device memory overflow).  There have been about 3 occurrences over the last month which means it is hard to find a common cause. The typical channel count is about 16 and has been always less than 40. If the 1600 has a sample buffer size of 4096, I figure that I should have more than two seconds before it overflows. I have launched applications, opened, closed and saved files, and none of these has triggered the error. The hard drive power management option is disabled. One item that I am unsure about is the screen saver and whether it could have caused anything. Does anyone have any clues as to why this problem might occur.

[devchander]

Probably having a look at your vi, wil help to suggest better

could you attach your vi??

[Phillip_Neir]

I would like to, but I work for GM and they consider this material confidential. I can say that the acquisition runs in a timed loop. The loop also does limit checking, PID control and some miscellaneous data processing. The loop usually completes in about 15ms so there is about 85ms of cushion before the loop runs again. I'm sorry I can't provide more. I did see a post 'somewhere' in the forums that mentioned possible issues with the 1600 and NI-DAQ 7. I can't seem to find it now. Anyway, I was hoping that someone might have some insight as to what could cause this to occur.

[devchander]

Are you using traditional DAQ or DAQmx??

Thats quite an overhead on your Analog input acquisition

Try this, its worth an effort

Assuming you are using DAQmx and also that you are performing continous acquisition

Instead of a timed loop, keep an ordinary loop

To your DAQmx read, specify number of samples to read per channel as 1/10th or 1/5th of your sampling rate ( 5 or 10)

see if it works

Regards,

Dev

[Phillip_Neir]

Dev,

Thanks for the suggestion. I used two timed loops in the app to be able to set a higher priority on acquisition and processing.The system is running a backlog of tests right now so I will have to wait until things slow down. A basic question, though. Given that the loop executes every 100ms and is never late (well, very rarely), how does a real overflow occur? We had a couple of occurrences yesterday. I am beginning to see a possible common thread. The system ran normally and after several minutes, with no user activity on the computer, the error popped up. This could be OS or computer related. The screen saver is set to 45 minutes and the hard drive never shuts off. I will be investigating that as well.

[50ohmTerminator]

Hey Phillip,

I presume that the error you get is from the acquisition. Have you tried to read from the onboard memory more often? Increase the loop rate of your timed loops and see if that helps.

Have a good one.

Malay
NI