LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Logitech Game Controller for use in Labview and dealing with possible disconnects

Hello all, I would like to see if there are any suggestions on the following issue. In effect I am using a Logitech game controller to manipulate large scale robots. During operation with these robots I need to plan for the inevitable "accidental" disconnection of the game controller from the computer running labview while it is under operation. Simple to say I can throw the system into standby upon the "ERROR" messages I get, but I want to programmatically be able to "reset" the controller (ie wait for it to be plugged back in) and have the program continue working. However with my work and research thus far that isn't the case. I end up with the same error (even when reconnected, attempted re-initialize, closing the connection, with time delays, and re-initailizing after closing all connections). Nothing seems to work other than closing the program and restarting it (which for the consumer this would be quite frustrating). Suggestions?

Also on a similar note if anyone has any ideas on how to scan for devices prior to using them would be helpful too.

I currently am running Labview 2009 in windows 7. I do realize windows has its unique way of dealing with plug and play devices, and suspect that I may have to play with these features, but I don't know this topic very well.

Thank you all in advance!

0 Kudos
Message 1 of 3
(2,608 Views)

Hey Dashiva,

 

I am assuming that the Game Controller that you are using is connected via USB. Does it show up in the computer's Windows menu when it is plugged in? If so, you can make calls to it using .NET controls that could access the device once it is re-connected. I would also try simply hitting F1 and see if that allows the program to reset the controller.

 

Good Luck,

 

Doug B

National Instruments

Applications Engineer

Applications Engineer
National Instruments
0 Kudos
Message 2 of 3
(2,573 Views)

That certainly is an option, but I got contacted by another ni rep who said that there is a problem in the dll file of the joystick vis.  I am currently awaiting an update on that situation.  Thank you for your input!

0 Kudos
Message 3 of 3
(2,548 Views)