What about using the Win system DLL call from inside the Query Input Devices VI to build your own piece of code to continuously monitor whether an input device is connected? I believe it might be caused by that shift register inside of the function.
The only DLL call I see in the Query Input Devices VI that's associated with a joystick is "C:\Program Files\National Instruments\LabVIEW 7.1\resource\lvinput.*" and that is not a DLL that ships with windows. NI would appear to be the source of it. What's more, there appears to a shift-register equivalent data store within the DLL code because, with execution highlighting turned on, it's easy to see that the DLL call will return the same initial call's information over & over again regardless of the subsequent attachment state of the joystick. Yes there is a shift register in the VI, but that does not appear to be the source of my "problem" at the moment.
Thanks for the thought though...
I don't suppose there are any other routines within the lvinput library which I could call to reset the state? Got (lvinput) documentation?
Message Edited by Warren Massey on 07-25-2007 07:20 AM
Has a solution to this "problem been found" I would very much like to know the answer as well.
Since the communication is in the user's hands, a "missing" joystick can be re-scanned and re-opened programatically.
Let me know if this helps.