Table Of Contents

Send Launch Nested Actor Msg (G Dataflow)

Version:
    Last Modified: April 27, 2020

    Sends a Message containing an Actor to another Actor. The Actor receiving the Message launches the payload Actor as a nested Actor. Use this VI only to send a Message from an Actor to itself. NI recommends you use Send Launch Nested Actor Msg only for an Actor sending a Message to itself because LabVIEW NXG cannot specify a run-time dependent scope.

    connector_pane_image
    datatype_icon

    message priority

    Order in which the Actor processes Messages in the Message queue.

    Name Description
    Low Specifies that the Actor processes the batch after Messages of all other priorities.
    Normal Specifies that the Actor processes the batch after critical- and high-priority Messages but before low-priority ones.
    High Specifies that the Actor processes the batch first. Only emergency stop and last ack Messages supersede high priority Messages.

    Default: Normal

    datatype_icon

    self enqueuer in

    Reference the Actor uses to send Messages to itself.

    datatype_icon

    nested actor

    Initial state of the Actor you want to launch.

    datatype_icon

    auto-stop

    Value that indicates whether the nested Actor stops when the calling Actor stops. The default value is True. If you set the value of this input to False, you must manually override the Stop Core VI on the caller Actor to specify stop behavior for the nested Actor.

    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

    self enqueuer out

    Reference the Actor uses to send Messages to itself.

    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