Discussion:
USB-6501 static problems
(too old to reply)
Zebraman
2008-03-31 23:40:11 UTC
Permalink
Hi,
I too, are having an issue with this 50405 error code.  My test setup is such:  PC going to a USB hub.  A UUT is then connected to the USB hub, along with the USB-6501.  With this setup, as soon as I toggle my UUT thru USB, the 6501 would drop out, giving me a 50405 error.  As you mention, I have to unplug the 6501 in order to reset it.  What's even more curious is that this only happen when I use a Dell PC, but works perfectly fine when I have my test bed setup with a HP PC.
What exactly is the 50405 error code means anyway?  Is it as James had mention, not enough grounding?
 
Thanks,
J_Thomas
2008-04-01 17:10:13 UTC
Permalink
Hi Zebraman,


 Here are some thoughts with regards to your questions.



ERROR 50405:




Under normal circumstances your USB
device should not stop responding during acquisition. Error 50405 simply indicates that a
device you have plugged into a into a USB 2.0 host controller has lost its connection.  The common reasons this occurs are:



- You unplug or insert a second device You lose power to the device (from
hub (is your hub powered?) or PC)



Improper grounding leading to a static
discharge could also cause this behavior. It is always a good idea to ensure proper  grounding of all  components in the system.


 


SUGGESTIONS WHY ONE PC WORKS AND ONE
DOESN?T:

The southbridge or I/O controller hub (ICH) is responsible for USB
communication for your PC. Making or breaking another USB connection while your
data acquisition device is connected may cause a communication error. This has
been observed on chipsets with ICH versions 2, 4 and 6, but may affect others
as well.

To determine the chipset in your PC, you can find it listed in the Windows
Device Manager or in your motherboard's BIOS. If you know you have an Intel
processor, Intel also provides a <a href="http://www.intel.com/support/chipsets/inf/sb/CS-009266.htm" target="_blank"> Chipset Identification Utility</a> that you can
download to identify what chipset your motherboard has.

If your application requires plugging/unplugging of USB devices and your PC has
one of these ICH versions, a quality powered hub connected to USB 2.0 may help.
Alternatively, consider using a PC with a different chipset. If you are using a laptop computer, check your power settings to make sure that
the USB ports are not being turned off to conserve power.




&nbsp;You might
also check out this forum:


<a href="http://forums.ni.com/ni/board/message?board.id=180&amp;thread.id=30481&amp;view=by_date_ascending&amp;page=1" target="_blank">USB 6501
card(s) becomes unresponsive</a>
Zebraman
2008-04-01 17:40:18 UTC
Permalink
Hi Jared,
&nbsp;
Thanks for the info.&nbsp; This morning I ran my test setup again, but this time with a 1.0 hub.&nbsp; Magically, my problem goes away.&nbsp; After that, I decided to disable the USB 2.0 driver, and went back to a 2.0 hub.&nbsp; My test setup still works.&nbsp; This agreed with what you had said, because I look up the chipset, and they are the ICH version.&nbsp; Looks like my UUT is not a true 2.0 device, and thus cause the USB-6501 to loose its connection.
My current hub is a powered unit, but I won't call it a quality unit.&nbsp; What would you suggest as a quality USB 2.0 hub?&nbsp; Please advise.
&nbsp;
Thanks for the link as well.&nbsp;&nbsp; Got a lot of info out that that too.
&nbsp;
J_Thomas
2008-04-02 14:40:14 UTC
Permalink
I was glad to hear that you found the likely cause of the
problem.&nbsp; Unfortunately, I don?t have a good recommendation for a model
and manufacturer of a quality USB hub. While the USB protocol is a standard, it
is open enough that quality differences can be seen between companies that
loosely follow the standard and companies that really push for strictly
adherence.&nbsp; I would suggest following the
age old advice that ?you get what you pay for.?&nbsp;
If it were me, I would look for a manufacturer that has a reputation in
the business for quality.


If anyone else has any specific recommendations, please feel
free to post them.
mreichman
2008-05-15 02:40:06 UTC
Permalink
I have been having some trouble with a similar NI USB device.&nbsp; I had 2 devices going into a 4 port hub and one of the devices kept giving me the -50405 error.&nbsp; I finally found that it was the usb cable between the hub and the computer that was messing everything up.&nbsp; I switched to a new USB cable and everything works now.
I'm not sure what the difference in USB cables is, but I just used a brand new one that I bought.
&nbsp;
stilly32
2008-05-16 18:10:05 UTC
Permalink
Hey,
&nbsp;
Thanks for posting! You mentioned the old cable was messing eveything up - was this the cable that shipped with the USB-6501 or just one you happened to be using? If it was the one that shipped with the device - was there anything written on it (serial/part number)?
&nbsp;
If it is one of ours I'll try to look into it some more.
&nbsp;
Andrew S.
&nbsp;
Multifunction DAQ Product Support EngineerMessage Edited by stilly32 on 05-16-2008 12:57 PM
mreichman
2008-05-16 18:10:05 UTC
Permalink
No, this was a cable that I had in my lab because I needed a longer cable than what came with the USB device.&nbsp; I bought a new cable from CDW that now seems to work well.&nbsp;&nbsp;
&nbsp;
I have 2 separate boxes each with 2 USB devices hooked up to a linksys 4 port hub.
The procedure I used to load my devices was as follows:&nbsp;
I powered the first box and installed the drivers and used the self test button in Measurement and Automation.
Then I rebooted the computer and checked to make sure the devices were still there and working
Then I powered the second box and repeated the self test and reboot procedure.
I'm not sure if this actually makes a difference because I was still getting the error message when I was using the old cable.
But when I switched to the new cable everything is fine.
&nbsp;
Hope this helps.
&nbsp;
stilly32
2008-05-16 18:10:06 UTC
Permalink
Thanks for the info - if you dig up any specs on the bad cable feel free to post it so others can avoid it. I know we've had some issues with poor quality cables in the past but this is the first I've heard of them linked to this error.
Thanks!
Andrew S

Continue reading on narkive:
Loading...