Table Of Contents

Is Connected (G Dataflow)

Version:
    Last Modified: September 16, 2017

    Checks to see whether the specified routes or route groups are connected.

    connector_pane_image
    datatype_icon

    session in

    Handle that identifies your Switch Executive virtual device session previously allocated by Open Session.

    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

    route specification

    String defining any routes and route groups to be checked.

    Requirements for Route Specification Strings

    • Any channel, other than an endpoint, within a route specification string must be reserved for routing or directly hardwired to one of the endpoint channels.
    • Channels used as endpoints must not be reserved for routing channels.
    • When connecting a route, the list of channels must obey the exclusion rules both explicitly in the route specification string as well as implicitly by any previous connections. Exclusion violations result in an error.

    Syntax for Route Specification Strings

    Route specification strings are the paths connecting two channels and are composed of one or more routes delimited by ampersands (&). For example, in the following line of syntax, there are three defined routes or route groups: routeOrGroup & routeOrGroup & routeOrGroup . . .

    where routeOrGroup can be any of the following:

    • Route name
    • Route group name
    • Two endpoint channels to be connected that are delimited by ->, for example channel -> channel. Switch Executive dynamically determines the path between the endpoints. A hardwire alias name can be substituted for the endpoints.
    • Fully specified path enclosed in square brackets consisting of one or more endpoint channels delimited by ->, for example [channel -> channel -> channel . . .]

      where channel can be the following:

      • A channel alias name
      • A unique name created by combining the IVI device logical name and IVI channel name separated by a slash (/) delimiter, for example device/iviChan
      spd-note-note
      Note  

      Switch Executive has the option of finding an available path at run time by slightly modifying the syntax. Remove the square brackets and enter the two endpoints of a route delimited by a ->.

    Examples of Route Specification String Syntax

    The following are samples of route specification strings for a matrix:

    String Route Specification Description
    A->B Connect channel A to channel B. Switch Executive automatically determines the path between the two channels.
    [SampleMatrix1/c0->SampleMatrix1/r1->SampleMatrix1/c4] A fully specified path between column 0 and column 4 of SampleMatrix1. Row 1 must be marked as reserved for routing.
    [Scope->R3->SampleMatrix1/c6] A fully specified path between the channel named "Scope" and column 6 of SampleMatrix1. Row 3 must be marked as reserved for routing.
    Scope->SampleMatrix1/c6 Connect the channel named "Scope" to column 6 of SampleMatrix1. Switch Executive automatically determines the path between the two channels.
    ArbToInput & ScopeToOutput Complete the connections for route group ArbToInput and ScopeToOutput.
    PowerDevice & [Scope->R3->UUT_Out] Complete the connections for route group PowerDevice and complete the fully specified path between the channel named "Scope" and the channel named "UUT_Out". R3 must be marked as a reserved for routing.
    datatype_icon

    session out

    Reference to your virtual device session to wire to the next node.

    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

    connected?

    Boolean value that returns whether any specified routes or route groups are connected.

    True The specified routes or route groups are connected.
    False The specified routes or route groups are not connected.

    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