Table Of Contents

IviSwtch Can Connect Channels (G Dataflow)

Version:
    Last Modified: October 23, 2017

    Verifies that the switch module is capable of creating a path between the two channels you specify with the channel 1 and channel 2 parameters. If the switch module is capable of creating a path, this node indicates whether the path is currently available given the existing connections. If the path is not available due to currently existing connections, but the implicit connection between the two channels already exists, the node returns the warning IVISWTCH_WARN_IMPLICIT_CONNECTION_EXISTS (0x3FFA2002).

    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.
    datatype_icon

    path capability

    Indicates whether a path is valid. Possible values include: IVISWTCH_VAL_PATH_AVAILABLE - 1 IVISWTCH_VAL_PATH_EXISTS - 2 IVISWTCH_VAL_PATH_UNSUPPORTED - 3 IVISWTCH_VAL_RSRC_IN_USE - 4 IVISWTCH_VAL_SOURCE_CONFLICT - 5 IVISWTCH_VAL_CHANNEL_NOT_AVAILABLE - 6 Notes: (1) IVISWTCH_VAL_PATH_AVAILABLE indicates that the driver can create the path at this time. (2) IVISWTCH_VAL_PATH_EXISTS indicates that the explicit path between the channels already exists. (3) IVISWTCH_VAL_PATH_UNSUPPORTED indicates that the instrument is not capable of creating a path between the two channels. (4) IVISWTCH_VAL_RSRC_IN_USE indicates that although the path is valid, the driver cannot create the path at this moment because the switch module is currently using one or more of the required channels to create another path. You must destroy the other path before creating this one. (5) IVISWTCH_VAL_SOURCE_CONFLICT indicates that the instrument cannot create a path because both channels are connected to a different source channel. (6) IVISWTCH_VAL_CHANNEL_NOT_AVAILABLE indicates that the driver cannot create a path between the two channels because one of the channels is a configuration channel and thus unavailable for external connections.

    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