Table Of Contents

IviScope Is Invalid Waveform Element (G Dataflow)

Version:
    Last Modified: October 24, 2017

    After the read and fetch waveform nodes execute, each element in the waveform array contains either a voltage or a value indicating that the oscilloscope could not sample a voltage. This node determines whether a value you pass from the waveform array is invalid. The driver uses an IEEE defined NaN (Not a Number) value to mark as invalid each element in the waveform array for which the oscilloscope could not sample a voltage.

    connector_pane_image
    datatype_icon

    is invalid

    Returns whether the Element Value is a valid voltage or a value indicating that the oscilloscope could not sample a voltage. Valid Return Values: TRUE (1) - The Element Value indicates that the oscilloscope could not sample the voltage. FALSE (0) - The Element Value is a valid voltage.

    datatype_icon

    element value (0.0)

    Pass one of the values from the waveform array returned by the read and fetch waveform nodes. The driver determines whether the value you pass is invalid. The driver uses an IEEE defined NaN (Not a Number) value to mark as invalid each element in the waveform array for which the oscilloscope could not sample a voltage.

    Default: None

    datatype_icon

    instrument handle out

    The instrument handle that you obtain from the IviScope Initialize or IviScope Initialize With Options node. The handle identifies a particular instrument session.

    datatype_icon

    instrument handle

    The instrument handle that you obtain from the IviScope Initialize or IviScope Initialize With Options node. The handle identifies a particular instrument session.

    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

    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

    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