SCXI-1102/SCXI-1303 not detected in SCXI-1000 chassis

[mtd12]

I am using a setup with SCXI-1303 module in a SCXI-1102 within a SCXI-1000 chassis to take voltage and thermocouple measurements.

Until recently, everything was working fine. but it now appears I am unable to communicate with the interface. I have tried two different computers and the hardware is not detected in MAX. The power light and fan on the SCXI-1000 still comes on, there just appears to be no acknowledgment of the connection to the computer.

A few more specific error codes:

* When I double-clicked the DAQ Assistant in the block diagram window and clicked "Test" on one of my inputs, I received the following error:
"Error -88705:The specified device is not present or is not active in the system."

* I have also gotten the error code "Error -89130: Device not available in NI-DAQmx" in the DAQ Assistant test panel

* When closing the DAQ Assistant test panel, I see the error "Error -89130: Device not available for routing"

* In MAX, if I try to "test" the chassis or module, I have seen errors either saying that the device is not detected, or that the device needs to be reset or is in the process of being reset, or that Traditional DAQ drivers need to be reset (I've tried these reset suggestions with no result)

At this point I'm wondering if the board or the cable is shot. I unfortunately don't have another 68-pin cable to test at the moment.

Thanks in advance...

[nyc_(is_out_of_here)]

Errors even when using NI-MAX usually indicates a hardware problem.

[James-B]

Yeah,

It sounds like either a connection issue or another hardware problem, especially if you are not able to add the chassis in MAX.

Definitely try to get your hands on another cable or even another 1102 if possible.  Basically try to isolate which part of the system is causing the problem.

[mtd12 · Accepted solution]

Thanks guys, I was able to resolve the problem. For anyone who might come across this,

* I noticed in Windows Device Manager that two PCI devices were listed as not being installed properly.

* After trying to update the drivers, I couldn't start the computer; got BSOD after BIOS load.

* Some research prompted me to pull out the two PCI cards that I was not using, and I also moved my DAQ card to another slot to force a hardware reinstall.

* Booted up, loaded the drivers automatically, and off I went.

Doesn't explain why it didn't work in the other computer, but in the words of Spinal Tap, the authorities said it was better left unsolved at this point.

[nyc_(is_out_of_here)]

---

@mtd12 wrote:

Thanks guys, I was able to resolve the problem. For anyone who might come across this,

* I noticed in Windows Device Manager that two PCI devices were listed as not being installed properly.

* After trying to update the drivers, I couldn't start the computer; got BSOD after BIOS load.

* Some research prompted me to pull out the two PCI cards that I was not using, and I also moved my DAQ card to another slot to force a hardware reinstall.

* Booted up, loaded the drivers automatically, and off I went.

Doesn't explain why it didn't work in the other computer, but in the words of Spinal Tap, the authorities said it was better left unsolved at this point.

---

You should move the DAQ board back and verify whether it still works. Perhaps one of the slots went bad.

You didn't notice that you had two PCI devices that were not installed properly before?

[mtd12]

This seemed to be some kind of sudden driver failure. I'm not sure if it was caused by a virus or just a glitch. It's pretty old hardware, Dell Dimension 4600 running XP SP2. There had been no reason to suspect improperly installed hardware before this issue spontaneously occurred.

[nyc_(is_out_of_here)]

---

@mtd12 wrote:

This seemed to be some kind of sudden driver failure. I'm not sure if it was caused by a virus or just a glitch. It's pretty old hardware, Dell Dimension 4600 running XP SP2. There had been no reason to suspect improperly installed hardware before this issue spontaneously occurred.

---

If there was no new software installed prior to your problems why would there by a sudden driver issue?

[mtd12]

I honestly don't know. It's a shared computer, maybe someone else made some change and didn't realize it. Either way, I've worked on/with computers long enough to expect that out of 100 "identical" power-ups I won't get 100 identical Windows start-ups. 

[nyc_(is_out_of_here)]

---

@mtd12 wrote:

I honestly don't know. It's a shared computer, maybe someone else made some change and didn't realize it. Either way, I've worked on/with computers long enough to expect that out of 100 "identical" power-ups I won't get 100 identical Windows start-ups. 

---

And this bit of information would have been useful to know as well.

When you don't know what someone else has done to a system, you cannot assume anything.

[Mbern]

HI! I'm having a similar problem. 1x SCXI 1000 chassis, 2x 1303 and 1x 1313 modules. My devices are working properly in Device Manager so I don't have the exact same problem as the OP, but we get the same error and have most of the same equipment. NI MAX isn't recognizing any hardware except the GPIB's, and the chassis and modules are "whited out" with small red X's on their icons in MAX. Any ideas?

Thanks!

Max