USB device not detected or is malfunctioning
07-20-2006, 08:43 AM
#1
Junior Member
Thread Starter
Join Date: Jun 2006
Location: Bedford,
PA
Posts: 6
Likes: 0
Received 0 Likes
on
0 Posts
USB device not detected or is malfunctioning
When I try to install my Airtronics RD6000 Super as my sim controller using a Milehigh wings interface I get the error "USB device is not detected or is malfunctioning". I have had it working twice only to crash the machine when I start FMS or Clearview. I'm 100% sure this is a Windows XP issue! This PC is a Dell Latitude D810 laptop running XP w/SP2 3.2 Ghz with 2 Ghz of RAM. I thought it might be a BIOS issue but I disabled anything I thought it might be to no avail. I plugged the TX into another PC running Win 2000 and it worked fine! When I plug the Milehigh wings interface in, XP detects it fine, when I turn the TX on, thats when I get the error. XP is not assigning resources to this device correctly for some reason. Any ideas.....PPJoy or something? Help!!!
Steve
Steve
07-24-2006, 05:59 PM
#2
Join Date: Nov 2005
Location: Poolesville, MD
Posts: 12,624
Likes: 0
Received 0 Likes
on
0 Posts
RE: USB device not detected or is malfunctioning
I'm making guesses here so bear with...
The Milehighwings interface is sensitive to anything else sitting on the same master usb controller.
Make sure that you have only ONE device plugged into the controller (which usually has two ports in your laptop).
Additionally, because of the way the laptop is powered, you may have a power feed issue, wherein the Laptop is unable to supply sufficient power to the interface or controller.
A powered hub may fix this... although in your shoes I would first try everything out on a desktop unit to be sure everything works.
Also disable advanced power saving options for the USB controller port (they are buried in the device manager USB advanced configuration dialog... e.g. turn of "allow this device to bring the computer out of standby" and "allow the computer to turn off this device to save power", etc.).
You also may not have the proper interface cable or you may have some reversed polarities shorting the Laptop.
Check to make sure that ALL USB ports are operational on the laptop by plugging a USB mouse into each port in turn, and make sure that it works.
Finally the circuitry in the USB port/hub built in to the laptop may have been electrically damaged over time.
Usually the main symptom of this, is that your machine will suddenly seem unwilling to boot with a particular device plugged in. If you unplug the offending device the machine starts right up again, and you can then plug the device right back in... although you shouldn't.
The Milehighwings interface is sensitive to anything else sitting on the same master usb controller.
Make sure that you have only ONE device plugged into the controller (which usually has two ports in your laptop).
Additionally, because of the way the laptop is powered, you may have a power feed issue, wherein the Laptop is unable to supply sufficient power to the interface or controller.
A powered hub may fix this... although in your shoes I would first try everything out on a desktop unit to be sure everything works.
Also disable advanced power saving options for the USB controller port (they are buried in the device manager USB advanced configuration dialog... e.g. turn of "allow this device to bring the computer out of standby" and "allow the computer to turn off this device to save power", etc.).
You also may not have the proper interface cable or you may have some reversed polarities shorting the Laptop.
Check to make sure that ALL USB ports are operational on the laptop by plugging a USB mouse into each port in turn, and make sure that it works.
Finally the circuitry in the USB port/hub built in to the laptop may have been electrically damaged over time.
Usually the main symptom of this, is that your machine will suddenly seem unwilling to boot with a particular device plugged in. If you unplug the offending device the machine starts right up again, and you can then plug the device right back in... although you shouldn't.
