cDAQ stops and requires power off/on to reset

[N1gel]

I have a CompactDAQ 9172 with a single 9205 analogue input module.

Recently my labview program keeps stopping (error -200284), having previously been running for a number of weeks without a problem and now it's stopping on a more regular basis. The only way to get it to run again is to turn off the cDAQ and turn it back on again. If the cDAQ is not power cycled the program will not run.

The first time this happened the program had been running for about 1 month.

After resetting it lasted about two days before stopping.

After the next reset it lasted about a day.

Does anyone know if this a hardware problem or some form of timing/buffer problem?

The error I get when the program stops is...

Error -200284 occurred at DAQmx Read (Analog 1D Wfm NChan NSamp).vi:2

Possible reason(s):

Measurements: Some or all of the samples requested have not yet been acquired.

If I stop the program and restart it I get the error...

Error -50405 occurred at DAQmx Start Task.vi:2

Possible reason(s):

No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified

From searching the internet someone suggested reseting the DAQ by using MAX

If I go into Ni MAX, select ‘Devices and Interfaces’, ‘NI-DAQmx Devices’,

Highlight/select ‘NI cDAQ-9172: “cDAQ1” and click ‘Self Test’and I get the error...

Error -50405 occurred at Self Test

Possible reason(s):

No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified

The same error (-50405) occurs if I try a 'Reset Chassis'

I've also tried reseting the 9205 this way and I get the error...

Error -200324 occurred at Device Reset

Possible reason(s);

Measurements; Device not available in NI-DAQmx. It is possible that the device is being used by Traditional NI-DAQ or that the device is being reset.

 Any ideas as to what is going on?

Thanks 

Nigel

[Andrew McL]

Hi N1gel,

It is difficult to work out what is causing the error without seeing your code. Could you possibly attach your VI to this post? I've added a link to common causes of DAQmx Errors and I would recommend having a look at that. 

Many thanks,