Table Of Contents

XNET Disconnect Terminals (G Dataflow)

    Last Modified: March 13, 2017

    Disconnects terminals on the XNET interface.


    session in

    The session to use for the connection. This session is selected from the LabVIEW project or returned from XNET Create Session.


    source terminal

    The connection source.


    destination terminal

    The connection destination.


    error in

    Error conditions that occur before this node runs. The node responds to this input according to standard error behavior.

    Default: No error


    session out

    A duplicate of session in, provided for simpler wiring.


    error out

    Error information. The node produces this output according to standard error behavior.


    This node disconnects a specific pair of source/destination terminals previously connected with XNET Connect Terminals.

    When the final session for a given interface is cleared (either by the node going idle or by explicit calls to XNET Clear), NI-XNET automatically disconnects all terminal connections for that interface. Therefore, XNET Disconnect Terminals is not required for most applications.

    This node typically is used to change terminal connections dynamically while an application is running. To disconnect a terminal, you first must stop the interface using XNET Stop node with the Interface Only scope. Then you can call XNET Disconnect Terminals and XNET Connect Terminals to adjust terminal connections. Finally, you can call XNET Start with the Interface Only scope to restart the interface.

    You can disconnect only a terminal that has been previously connected. Attempting to disconnect a nonconnected terminal results in an error.

    Where This Node Can Run:

    Desktop OS: Windows

    FPGA: Supported

    Recently Viewed Topics