02-10-2005 12:34 PM
02-10-2005 01:56 PM
02-10-2005 03:08 PM
02-10-2005 03:12 PM
07-11-2006 09:28 AM
I am using the niSwitch API in Visual Basic and I recently ran into this same problem. I wrote a single function that would connect two channels together when I called it. However, this function would open the session (reset the device), make the connection, debounce, then close. However, the reset is not desired since I want more than just two channels conencted at a time, and the number of channels to be connected varies. None of the niSwitch init functions support a VI_FALSE value for the resetDevice parameter.
So I just wrote my visual basic code so that one session is opened to the switch and remains open for the life of the application. When the code is terminated, so is the session.
Is there any danger in leaving a session open for extended periods of time? And what kinds of errors do you need to check for? If I tell two channels to connect that are already connected it just says they are already connected and no harm is done... so I am not worried about that...
JPO
07-11-2006 09:54 AM