Spacepilot works.... Well kind of.

dcrawford919 · Post by **dcrawford919** » Thu May 06, 2010 7:39 am

Hello all, I've been searching for a fix for this device for awhile. I v'e tried many suggestions without resolution.
Here is my situation:
I have 12 Spacepilots (belonging to my Company), and only 3 are working properly. I am installing them on HP workstations, XW9400. I am using the latest drivers and latest BIOS on ALL workstations. I have been able to get the other 9 Spacepilots to work until the machine is rebooted. After installing, I open Device Manager and find that the Spacepilot shows up as "HP Remote Physical USB". I disable and reenable it, and then it shows up as a Human Interface Device. However, it reverts back after a reboot or the device is unplugged and replugged at the USB port. This cannot work for me because all our workstations are in security enclosures and locked with a one-use serial numbered bolt. I would have to cut and install a new bolt everytime I need to unplug/replug the Spacepilot. I can login as Admin and disable/reenable the deivce in Device Manager, but I cannot do this everyday. It's too much time wasted while other users need my assistance. Is there anyway to lock the ports in a state that keeps the USB port from reverting back to "HP Remote Physical USB"?
Thank you for any assistance you can provide.

Post by **jwick** » Mon May 10, 2010 6:54 am

Have you called tech support about these devices that don't work on reboot? They should work on reboot.

Fred · Post by **Fred** » Tue May 11, 2010 5:18 am

Sounds like the systems have a Virtual COM port (VCP)
Card installed. This would cause the device to not be recognized corectly after reboot.
Do you have any additional USB ports that are not connected to this card you can plug into?

dcrawford919 · Post by **dcrawford919** » Tue May 11, 2010 11:40 am

jwick wrote:Have you called tech support about these devices that don't work on reboot? They should work on reboot.

Jwick, No I have not called yet. I was hoping to find an answer here. Do you know who I need to contact for best results?

Thx.

Post by **jwick** » Tue May 11, 2010 11:45 am

Call Fred.

dcrawford919 · Post by **dcrawford919** » Tue May 11, 2010 11:46 am

Fred wrote:Sounds like the systems have a Virtual COM port (VCP)
Card installed. This would cause the device to not be recognized corectly after reboot.
Do you have any additional USB ports that are not connected to this card you can plug into?

Fred, No our workstations do not have USB cards installed. These are plugged into the mobo USB ports. I have followed previous advice and plugged into every USB port, with the same results. It seems to be a problem of the Spacepilot not being recognized as a HID. What is frustrating is that it only happens on some workstations. All of the workstations are identicle, in hardware & software. They are all imaged using the same Ghost image. They all have the same BIOS version and mobo revision. So I'm stumped. Also, because of our security requirements, I cannot return the devices for refund or replacement.

Fred · Post by **Fred** » Tue May 11, 2010 12:22 pm

Is HP Remote Graphics Software installed on the computers?
If it is can this be temporarily removed from one of the pc to see if the device gets recognized correctly after reboot, or disabled from starting in the startup sequence?

Post by **ngomes** » Tue May 11, 2010 12:44 pm

Hi dcrawford919,

I think Fred is correct in being suspicious of HP Remote Graphics Software. RGS supports 3D input devices (HID) in its "Remote USB" feature.

If you have the "Receive" software installed on the systems where your SpacePilots are connected, then RGS may be picking those up and creating a virtual USB connection to the "Sender" system.

Try configuring RGS so that all USB devices are "local". You may have to re-install RGS.

dcrawford919 · Post by **dcrawford919** » Tue May 11, 2010 3:14 pm

jwick wrote:Call Fred.

Thx.

dcrawford919 · Post by **dcrawford919** » Tue May 11, 2010 3:23 pm

Fred & Ngomes, I'm pretty sure we don't have RGS on our workstations. Due to the strict security requirements, we could not use software that would allow remote access. Our ISO surely would have not included that in our image. But I will verify that.

dcrawford919 · Post by **dcrawford919** » Wed May 12, 2010 12:06 pm

Well it turns out that HP Remote Graphics Service is advertised to our engineering dept & it was the cause of my problem. I uninstalled, rebooted to let the Spacepilot be properly recognized as a HID. Then I reinstalled HP RGS, rebooted and the Spacepilot remained operational.

I and a dozen or so engineers are very gratefull for your assisstance.

Post by **ngomes** » Wed May 12, 2010 3:49 pm

Great news, dcrawford919.

We're very glad to learn that you're all set. Thanks for letting us know.

3Dconnexion Forum

Spacepilot works.... Well kind of.

Spacepilot works.... Well kind of.

It was RGS!