TestStand 2019 Help
»View Product Info
The Switching panel specifies a switching action TestStand performs around the execution of the step. This feature is available only when you install NI Switch Executive software.
The Switching panel contains the following options:
- Enable Switching—When you enable this option, TestStand performs a switching action for the step.
- Switch Executive Virtual Device—An expression TestStand evaluates at run time to determine the virtual device on which TestStand performs the switching action.
||Note TestStand does not release an NI Switch Executive virtual device until all executions that use it complete and close.
- Operation—Specifies whether to connect or disconnect the specified routes or disconnect all previously connected routes. This operation returns as soon as the instrument is ready for another operation, which may occur before or after the switches involved settle. Use the Wait for Debounce before Executing Step option when you want to wait until all switches have debounced. You can choose from the following options:
- Connect—Connects the paths for the specified routes in the Route(s) to Connect control.
- Disconnect—Disconnects the paths the specified routes in the Route(s) to Disconnect control define.
- DisconnectAll—Disconnects all previously created paths.
- Connect/Disconnect—Connects the paths for the routes specified in the Route(s) to Connect control and disconnects the paths specified in the Route(s) to Disconnect control. Use the Operation Order ring control to specify whether the Disconnect operation occurs before or after the Connect operation.
- Route(s) to Connect—The routes you are connecting. The expression must be a valid route specification string as the NI Switch Executive configuration for the virtual device name you are using defines. The string can be a combination of route group alias names, route names, and physical route paths.
- Route(s) to Disconnect—The routes you are disconnecting. The expression must be a valid route specification string as the NI Switch Executive configuration for the virtual device name you are using defines. The string can be a combination of route group alias names, route names, and physical route paths.
- Multiconnect Mode—The behavior when more than one connection operation occurs on a specific route. The following options are available:
- No Multiconnect—A route can only be connected once. Any attempt to reconnect an already connected route results in an error.
- Multiconnect Routes—A route can be connected multiple times. The route must contain the same endpoints and path. NI Switch Executive automatically reference counts the routes. If you issue multiple connect operations for a specific route, the route is not physically disconnected until an equal number of disconnect operations occur. You can either issue the Disconnect operation manually or use a lifetime setting for the route. The Disconnect All operation disconnects a route even if the route reference count is greater than one.
- Use Default Setting for Route—Use the setting defined for the route in the NI Switch Executive software.
- Operation Order—Specifies whether the Disconnect operation occurs before or after the Connect operation. The following options are available:
- Disconnect before Connect—Disconnect the specified routes before connecting any routes. This is the typical mode of operation.
- Disconnect after Connect—Connect the specified routes before disconnecting any routes. Use this mode of operation when you are switching electric current and want to ensure that a load is always connected to the source.
- Connection Lifetime—The lifetime TestStand applies to the routes specified for connect/disconnect actions. You can specify whether you want the route to exist until manually disconnected later, or until the step, sequence, thread, or execution completes. When you use the Multiconnect Mode, a route can exist longer if another step specifies its own lifetime for the same route. Selecting a lifetime other than manual guarantees that the route stays connected as long as the step, sequence, thread, or execution in which you connect is executing. When you manually disconnect a route previously connected using a non-manual lifetime setting, TestStand releases the reference to the route for the last step that performed a Connect operation for that route.
- Wait for Debounce before Executing Step—When you enable this option, the operation waits for all switches to debounce before returning to TestStand. The wait for debounce occurs after both Connect and Disconnect operations are complete.
Route Specification Strings