PCI-5124 not detected by plug and play on XP

[beunjb]

I am trying to verify that the two PCI-5124 cards I have are working.  I am following the steps to install the PCI-5124 and it is not being detected by Windows XP Plug and Play.  I installed the driver CD's, rebooted the computer, shut down, added a PCI-5124, and then tried to run the MAX software to make sure NI-SCOPE could see the cards.  I refreshed the menu as prompted in the manual but the card still didn't appear in the list.  I have tested the PCI slot with another DAQ card and moved the card to different PCI slots and plug and play was not able to find it and ask to install softare for it.  Any suggestions on how to get either plug and play and/or MAX to see the PCI-5124?

[John_P1]

Hi beunjb,

Welcome to the NI forums!  The following steps should help us narrow down the cause of your problem:

1.    Make surethat you have NI-SCOPE installed.  The driver CDs have numerous drivers on them, so there is a chance that you may not have selected NI-SCOPE when you ran the install.  If you do have the driver installed, which version are you using?  You can check this in Measurement and Automation Explorer under the Software category.  The 5124 uses NI-SCOPE while the other DAQ device you tested probably uses either DAQmx or Traditional DAQ.  If you do not have NI-SCOPE, you can install it from the driver CD or from the above link and this should resolve the issue.

2.    After verifying that you have NI-SCOPE installed, check to see if the device displays in the Device Manager under Data Acquisition Devices.  If the device is present, check for a yellow exclamation mark over its icon.  If the exclamation mark is present, follow the steps in this article to allow Windows to recognize your device.  The screenshots are from a GPIB device but the procedure should be more or less the same.

If I understand correctly you have two PCI-5124s that cannot be detected, and you are able to use another DAQ Device in the same PCI slots.  For this reason, I am inclined to think that a driver issue is the most likely culprit.  Let us know if you are still experiencing any problems after completing the above steps and what the results of those steps were (i.e. driver version, status in device manager, etc.).  Thanks for posting and have a great day!

-John