Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

USB-8451 Stopped working

Hi Folks,

      Today, while running a LabVIEW application (that was working) - I started seeing USB-8451 related errors.  I quit LabVIEW and found the device is red-flagged (unresponsive) in MAX.  Of course I tried unplugging/inserting USB cable, and at this point have:

 

1) Replaced USB cable

2) Replaced USB-8451 with another 8451

3) Reinstalled device driver

3) Repaired USB-8451 installation

3) Reinstalled USB-8451 installation

 

I don't know whether it's noteworthy that the device is:

1) Healthy according to the Windows hardware-manager

2) always appearing (red-flagged) in MAX - even when unplugged

3) changing alias and saving has no effect - old alias shows up when MAX is reopened.

 

At the moment, am looking at reinstalling MAX (but hoping for simpler solution!)

 

Any suggestions, comments, helpful criticism or sympathetic remarks are appreciated.

 

Cheers!

 

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 1 of 9
(5,100 Views)

Hey tbd,

 

Have you tried deleting the device in MAX with the device unplugged and then closing out MAX, plugging the device back in, and re-opening MAX?  Also have you tried Resetting the device in MAX by right-clicking and choosing such option in the drop down menu?  Though your symptons aren't blatantly present in the following link, you may want to try the steps recommended in this KB to see if you can get MAX to update and refresh its database.

 

Let me know the results!

David Pratt
Group Manager for Application Engineering Specialists | Automated Test
NIC
0 Kudos
Message 2 of 9
(5,073 Views)

David P. wrote:

Hey tbd,

 

Have you tried deleting the device in MAX with the device unplugged and then closing out MAX, plugging the device back in, and re-opening MAX?  Also have you tried Resetting the device in MAX by right-clicking and choosing such option in the drop down menu?  Though your symptons aren't blatantly present in the following link, you may want to try the steps recommended in this KB to see if you can get MAX to update and refresh its database.

 

Let me know the results!


Hi David,

      Here's a screen-shot of left-click - notice Delete is disabled-and-greyed, also, no "Reset" option.

 

 

Note: While poking-about, I selected the NI Device Monitor option (right-click DevMon taskbar shortcut) "Clear All Device associations" and was presented this dialog:

 

I have no idea how to view the "auto-launch" dialog in order to see a "Always Take this Action" checkbox...

 

Thanks/Cheers!

Message Edited by tbd on 02-23-2009 12:35 PM
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Download All
0 Kudos
Message 3 of 9
(5,066 Views)

Smiley Tongue


tbd wrote:
 Here's a screen-shot of left-click - notice Delete is disabled-and-greyed, also, no "Reset" option.

Screen shot of MAX actually shows right-click options...

 

Cheers!

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 4 of 9
(5,062 Views)

Uninstalled everything NI related, reinstalled NI-DAQmx, NI-488, NI-845x, & LabVIEW (uninstall required w/MAX.).

 

MAX now shows USB device (and com-ports) healthy (no-read flag), but 

 

Now a DAQ board refuses to be recognized - always appearing as "PCI Device" in new-device dialog. Smiley Mad

 

Tried removing card, pwr-up, pwr-dwn, install card. with same result.  "PCI Device" can't be installed and results in yellow question-mark in device manager.

 

This board did install two-weeks ago with the same rev of NI-DAQmx!

 

Cheers!

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 5 of 9
(5,057 Views)

Hey tbd,

 

Whenever you re-inserted the card and let Windows Hardware Wizard try to automatically find the driver this failed?  What happens if you select the third option the wizard gives you for not connecting to the internet and only searching the local hard drive?  Is the DAQmx installation from a disk or from the downloadable version?  If not, try the most recent version available here.

David Pratt
Group Manager for Application Engineering Specialists | Automated Test
NIC
0 Kudos
Message 6 of 9
(5,047 Views)

Hi David,


David P. wrote:

What happens if you select the third option the wizard gives you for not connecting to the internet and only searching the local hard drive?


 

      Thanks for the ideas.  I did try restricting search to local-drive - same results.  I think it's a key point that device was recognized as only a generic "PCI Device" and not a PCI-xxx.

 

While the device had been recognized and working with DAQmx 8.6.?, today installed 8.7.1 and the DAQ board was finally recognized.

 

This episode was a productivity-killer - hope I don't do this I mean, hope this doesn't happen again.

 

Cheers!  

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 7 of 9
(5,033 Views)

Hey tbd,

 

I'm glad that updating the driver worked for you.  I'm not sure what else could have been causing this unless something in your chipset driver wasn't able to recognize and associate the NI-DAQmx driver files with the hardware.  Typically your computer will only recognize the model number PCI-xxxx if there is some known association occurring between the driver and Windows, and for some reason, this association was lost with the uninstallation. Glad to hear it's working though, thanks for posting to the community!

David Pratt
Group Manager for Application Engineering Specialists | Automated Test
NIC
0 Kudos
Message 8 of 9
(5,023 Views)

Hey David - thanks again for response/ideas.  I'm hoping the problems were related to something I did (though I don't remember disturbing the environment prior to original problem.)

 

Regarding the NI-board failing to be recognized, your remark regarding "if there is some known association" had me wondering about PCI resource "caching" problems.  Seem to recall the BIOS (or other low-level OS) caching PCI-device info, also there's an "inf" folder in the windows installation directory.  Prior to DAQmx upgrade I tried powering-up w/out board and also changed slot (to no avail.)

 

Cheers!

"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
0 Kudos
Message 9 of 9
(5,003 Views)