How do I un-mis-identify a USB device?
sylvie369
Posts: 1,622
(Cursing Microsoft quietly under his breath...)
I'm working on an XBee project, and got most of it set up, and then ran into a problem. I attached my new Parallax XBee USB board - which had been working fine so far - to a USB port, and all of a sudden up popped a "Installing Device Driver" message, followed fairly quickly by a message to the effect of "Congratulations! Your new MS Trackball is installed and ready for use! I'll bet you're SO happy!". Er, thanks.
It then would not let me connect to the XBee through XCTU ("Unable to communicate with modem"), and as long as it was plugged in, my mouse pointer was jumping all over the screen. I rebooted, but with no luck. I uninstalled the Trackball thing from the Device Manager, but when I plugged the XBee USB board back in, it just installed it again. I don't see any way to stop it.
Just now I apparently did something that helped, and XCTU is working fine at the moment, but I have no faith that it's not going to happen again. What's the secret to keeping Windows from deciding that your device of type X is actually a device of type Y?
==============================
In happier news, it's working! What I'm working on is a board to mount in a rocket, connected to a battery and a serial "hockey puck" GPS·that will use an XBee to send the rocket's position down to the ground. At this very moment I'm happily receiving valid NMEA strings from the board. It's a bit jury-rigged, as I ran out of 5V regulators, so I have a couple of wires from an external 5V supply running to two of the pads where the regulator will go when I get it in a day or two. But it's properly powering the GPS through a DB9 connector, and powering the XBee (3.3V), un-inverting the GPS data using a little transistor circuit that I got from this forum...in short, working as it's supposed to. With two regulators, the inverting circuit, the XBee connections and the GPS connection, this is the most complicated circuit board I've designed so far (I just started about two months ago). I'm thrilled that it works properly. Next step will be to set up a Propeller-based receiver that parses the NMEA strings, extracts the position and valid signal data, and then sends them to an LCD screen and as a waypoint to a handheld GPS. That should be mostly just a matter of programming.
I'm working on an XBee project, and got most of it set up, and then ran into a problem. I attached my new Parallax XBee USB board - which had been working fine so far - to a USB port, and all of a sudden up popped a "Installing Device Driver" message, followed fairly quickly by a message to the effect of "Congratulations! Your new MS Trackball is installed and ready for use! I'll bet you're SO happy!". Er, thanks.
It then would not let me connect to the XBee through XCTU ("Unable to communicate with modem"), and as long as it was plugged in, my mouse pointer was jumping all over the screen. I rebooted, but with no luck. I uninstalled the Trackball thing from the Device Manager, but when I plugged the XBee USB board back in, it just installed it again. I don't see any way to stop it.
Just now I apparently did something that helped, and XCTU is working fine at the moment, but I have no faith that it's not going to happen again. What's the secret to keeping Windows from deciding that your device of type X is actually a device of type Y?
==============================
In happier news, it's working! What I'm working on is a board to mount in a rocket, connected to a battery and a serial "hockey puck" GPS·that will use an XBee to send the rocket's position down to the ground. At this very moment I'm happily receiving valid NMEA strings from the board. It's a bit jury-rigged, as I ran out of 5V regulators, so I have a couple of wires from an external 5V supply running to two of the pads where the regulator will go when I get it in a day or two. But it's properly powering the GPS through a DB9 connector, and powering the XBee (3.3V), un-inverting the GPS data using a little transistor circuit that I got from this forum...in short, working as it's supposed to. With two regulators, the inverting circuit, the XBee connections and the GPS connection, this is the most complicated circuit board I've designed so far (I just started about two months ago). I'm thrilled that it works properly. Next step will be to set up a Propeller-based receiver that parses the NMEA strings, extracts the position and valid signal data, and then sends them to an LCD screen and as a waypoint to a handheld GPS. That should be mostly just a matter of programming.
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Tia'Shar Manetheren