Why Does niSE Open Session.vi Disconnect Previously Connected Routes? Primary Software: Switch ExecutivePrimary Software Version: 2.0 Primary Software Fixed Version: N/A Secondary Software: LabVIEW Development Systems
Problem: I'm programming an application using NI Switch Executive, but every time I close out the NISE Session, and open a new session, I hear switches opening. Why does this happen? Shouldn't I be able to open a new session without making any changes to previously connected routes? Is there a way around this? Solution: niSE Open Session.vi initializes the switches associated with the NISE Session to a known state; that is, it is designed to disconnect previously connected routes when called. This is most likely encountered in a setup similar to that in Figure 1, where a session is opened with a NI Switch Executive Virtual Device (NISE_Example), and then closed, and then opened again later in the program. Figure 1:
If you do not want connections to be severed, simply don't close out NISE Sessions. There are several ways you could go about doing this. Figure 2 is one possible solution just using wires and would function just the same as Figure 1, except it would allow RouteGroup0 to remain connected as desired. Figure 3 shows another way to do this using Local Variables created from the indicators in Frame 0, namely NISE Session (out) and Error Out. Figure 2:
Figure 3:
Related Links: Attachments:   
Report Date: 10/27/2004 Last Updated: 11/03/2004 Document ID: 3EQ9IULZ |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
