Table Of Contents

Dequeue (G Dataflow)

Version:
    Last Modified: April 27, 2020

    Reads a Message that a top-level Actor sent to its caller. Use this VI to interact with code that is not in a VI that belongs to an Actor.

    connector_pane_image
    datatype_icon

    message dequeuer in

    Reference needed to read Messages from a top-level Actor.

    datatype_icon

    timeout in milliseconds

    Time, in milliseconds, this VI has to read the Message. The default is -1, which specifies no timeout.

    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

    message dequeuer out

    A duplicate of message dequeuer in.

    datatype_icon

    message

    Message read from the queue. If timed out? returned True, message returns the default Message class.

    datatype_icon

    timed out?

    Boolean value that represents whether this VI did not read the Message within the specified time.

    True This VI did not read the Message before timeout in ms elapsed.
    False This VI read the Message before timeout in ms elapsed.
    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

    priority

    Priority level at which LabVIEW NXG sent the Message.

    Name Description
    Low Specifies that the Actor processes the Message after Messages of all other priorities. The Actor processes multiple low-priority Messages in the order it receives them.
    Normal Specifies that the Actor processes the Message after critical- and high-priority but before low-priority ones. The Actor processes multiple normal-priority Messages in the order it receives them.
    High Specifies that the Actor processes the Message first. The Actor processes multiple high-priority Messages in the order it receives them. Only emergency stop and last ack Messages supersede high priority Messages.

    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