USB 5132 not recognized by Measurement and Automation Explorer

[PhilLC]

I installed M&AE and then connected a new 5132 via USB.  WinXP reported the new device the first time.  If I plug the 5132 in, the CPU beeps and it also beeps when I unplug.  So the hardware connection seems ok. My new 5132 USB digitizer is recognized by WinXP.  But M&AE never sees the unit even if I press F5 to rescan for devices.  I downloaded the latest version of NIscope and reinstalled to no avail.  (Actually I started this painful process on a new Win7 machine and spent hours getting nowhere.)  The light on the 5132 does not come on when I make the USB connection.  (I have 2 of the 5132.  Both are unresponsive.)

[Jim_S]

Hello PhilLC,

After reading your post, it seems that you having problems with MAX (Measurement and Automation Explorer) not seeing your USB 5132 but Windows can see it. Have you verified this in Device Manager? You can find this by going to this link. I would agree that it seems to be recognizing but I would like to rule this out.

If device manager doesn't see the USB 5132, I have a few other questions to ask. Which version of the NI-Scope do you have? Have you tried a different USB port to ensure that it isn't the port? Have you tried a different.

If device manager does see it, then I would like to make sure that the driver is being assigned correctly. How is the device represented in the device manager? Could you post what your device manager looks like with your card? If this seems normal, I would then check to see if all the services are started. Here is a link about the two main ones to consider.

[PhilLC]

Last week I was working from my home office. Today I am in the lab. I brought the WinXP laptop with me that has just M&AE installed. On a lark, I fired up M&AE and then plugged in one of the 5132 units I brought with me.  WinXP asked for a driver disk and I put in the >1 GB driver download that I got last week. Installation completed, the green light on the 5132 lit up and now M&AE sees the 5132. I have no idea why things have started to work!  Perhaps the computer needed a total shutdown rather than just a restart after M&AE was installed?  In any case, for now my problem is solved and I can move on!!!