-200107 and -200835 error messages

[ImaqUser]

I have a Multifunction NI PCI-6289 connected to SCXI 1001 chasis.  The chasis carries 9 modules in order SCXI-1520, 1540, 1102, 1581, 1125, 1124, 1162, 1163 and 1530.  My application is using all the modules except the modules 1125 and the 1530 in slots 5 and 9.I used my LabView application without any problem for sometime and didn't get any of these errors.  However, recently I keep getting these error messages after running my application for half an hour or so for both DAQmx Read and DAQmx Write Vis.  I m not sure if these errors indicate hardware or software problems?? 

The exact messages are:    

Error -200835 occured at DAQmx Read (Analog 1D DBL NChan 1 Samp).viSCXI device cannot be used in this task because the power to the device was turned off after the task had been created.Call DAQmx Clear Tast and then create a new task to use this SCXI device.SCXI Module: SC1Mod3Chas's Communicator: Dev1 

---

I also get the below message if you hit the continue button in the error message dialog box: 

Error -200107 occurred at DAQmx Read (Digital 1D Bool NChan 1Samp 1Line) Module specified in the hardware configuration is not the module found. Make sure that the module specified in the hardware configuration is present in the specified slot. Device Specified: SC1Mod7Task Name: _unnamedTask<18> 

I have no idea how to solve these problems.  Because when I start my application, I get these errors after a while. Can anybody help me on these error messages ? 

[AnalogKid2DigitalMan]

Have you checked to make sure all the modules are well seated in the chassis? You may want to power down the system and remove/reinsert the modeules.

Power connections tight?

That is where I would start.

-AK2DM

[ImaqUser]

I removed all the modules an re-inserted to the chasis.  I also reset the PCI 6289 and the modules one by one.  When I test the DAQ card and the modules, I don't get any errors and they all pass the test.  I don't understand why I get problem after running the application after a while.

[EEsRULEtheWORLD]

Hi,

I've experienced this issue before, and a simple uninstall/reinstall of the drivers seemed to fix this error.  It is possible that the driver may have become corrupted.  After this error occurs, are you able to detect all modules in Measurement and Automation Explorer (MAX) or in Device Manager? 

Try uinstalling/reinstalling the driver, and see if this helps.