Table Of Contents

IviSwtch Connect Channels (G Dataflow)

Version:
    Last Modified: October 23, 2017

    Creates a path between channel 1 and channel 2. The driver calculates the shortest path between the two channels. If a path is not available, the node returns one of the following errors: IVISWTCH_ERROR_EXPLICIT_CONNECTION_EXISTS (0xBFFA200C), if the two channels are already explicitly connected by calling either the IviSwtch Connect Channels or IviSwtch Set Path Node. IVISWTCH_ERROR_IS_CONFIGURATION_CHANNEL (0xBFFA2009) , if a channel is a configuration channel. Error elaboration contains information about which of the two channels is a configuration channel. IVISWTCH_ERROR_ATTEMPT_TO_CONNECT_SOURCES (0xBFFA200B), if both channels are connected to a different source. Error elaboration contains information about sources to which channel 1 and 2 connect. IVISWTCH_ERROR_CANNOT_CONNECT_TO_ITSELF (0xBFFA2015) , if channels 1 and 2 are one and the same channel. IVISWTCH_ERROR_PATH_NOT_FOUND (0xBFFA2011), if the driver cannot find a path between the two channels. This node applies default values to properties that have not been set by the user under the following conditions: (1) If the user has not set the value of any property in the IviSwtchScanner extension, the following default values are used: IviSwtch>>Scanning Configuration>>Scan List [SCN] - "" (Empty string) IviSwtch>>Scanning Configuration>>Trigger Input [SCN] - IVISWTCH_VAL_EXTERNAL IviSwtch>>Scanning Configuration>>Scan Advanced Output [SCN] - IVISWTCH_VAL_EXTERNAL IviSwtch>>Scanning Configuration>>Scan Delay [SCN]- 0 Notes: (1) The paths are bidirectional. For example, if a path exists from channel CH1 to CH2, then a path from channel CH2 to CH1 also exists. (2) This node performs interchangeability checking when the IviSwtch>>Inherent IVI Settings>>User Options>>Interchange Check property is set to TRUE. If the IviSwtch>>Inherent IVI Settings>>User Options>>Spy property is set to TRUE, you use the NI I/O Trace utility to view interchangeability warnings. You use the IviSwtch Get Next Interchange Warning Node to retrieve interchangeability warnings when the IviSwtch>>Inherent IVI Settings>>User Options>>Spy property is set to FALSE. For more information about interchangeability checking, refer to the help text for the IviSwtch>>Inherent IVI Settings>>User Options>>Interchange Check property.

    connector_pane_image
    datatype_icon

    instrument handle

    The instrument handle that you obtain from the IviSwtch Initialize Node. The handle identifies a particular instrument session.

    Default: None

    datatype_icon

    error in

    Error conditions that occur before this node runs.

    The node responds to this input according to standard error behavior.

    Standard Error Behavior

    Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

    error in does not contain an error error in contains an error
    If no error occurred before the node runs, the node begins execution normally.

    If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

    If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

    Default: No error

    datatype_icon

    channel 1 ("")

    You identify a path with two channels. Pass one of the virtual channel names for which you want to create a path. Pass the other channel name as the channel 2 parameter. Users who want to achieve interchangeability should use a virtual channel name. The virtual channel name should be sufficiently specific to the test system such that it is unlikely to conflict with a physical channel name. Virtual channel names are aliases for instrument-specific channel strings. The instrument-specific channel strings can differ from one instrument to another. Virtual channel names allow you to use and swap instruments without having to change the channel names in your source code. You assign a virtual channel name to an instrument-specific channel through the Configuration Utility. This control accepts virtual channel names you have assigned to the specific instrument you are using. It also accepts the instrument-specific channel names. Default Value: ""

    datatype_icon

    channel 2 ("")

    You identify a path with two channels. Pass one of the virtual channel names for which you want to create a path. Pass the other channel name as the channel 1 parameter. Users who want to achieve interchangeability should use a virtual channel name. The virtual channel name should be sufficiently specific to the test system such that it is unlikely to conflict with a physical channel name. Virtual channel names are aliases for instrument-specific channel strings. The instrument-specific channel strings can differ from one instrument to another. Virtual channel names allow you to use and swap instruments without having to change the channel names in your source code. You assign a virtual channel name to an instrument-specific channel through the Configuration Utility. This control accepts virtual channel names you have assigned to the specific instrument you are using. It also accepts the instrument-specific channel names. Default Value: ""

    datatype_icon

    instrument handle out

    The instrument handle that you obtain from the IviSwtch Initialize Node. The handle identifies a particular instrument session.

    Default: None

    datatype_icon

    error out

    Error information.

    The node produces this output according to standard error behavior.

    Standard Error Behavior

    Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

    error in does not contain an error error in contains an error
    If no error occurred before the node runs, the node begins execution normally.

    If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

    If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

    Where This Node Can Run:

    Desktop OS: Windows

    FPGA: Not supported

    Web Server: Not supported in VIs that run in a web application


    Recently Viewed Topics