From 12:00 PM - 4:00 PM CST on Thursday, October 18, ni.com will be undergoing system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Table Of Contents

IviSpecAn Configure Trace Type (G Dataflow)

Version:
    Last Modified: October 24, 2017

    Configures the type of trace to acquire.

    connector_pane_image
    datatype_icon

    instrument handle

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

    Default: None

    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

    trace name ("")

    Pass the name of the trace you are configuring. This control accepts either a virtual repeated capability name or an instrument-specific trace name. Users who want to achieve interchangeability should use a virtual repeated capability name. The virtual repeated capability name should be sufficiently specific to the test system such that it is unlikely to conflict with a physical repeated capability name. Virtual repeated capability names are aliases for instrument-specific trace strings. The instrument-specific trace strings can differ from one instrument to another. Virtual repeated capability names allow you to use and swap instruments without having to change the trace names in your source code. You specify virtual repeated capability names in MAX. Default Value: ""

    datatype_icon

    trace type (Clear Write)

    The type of trace to acquire. The driver sets the IviSpecAn>>Basic Operation>>Trace Type property to this value. Valid Values: IVISPECAN_VAL_TRACE_TYPE_CLEAR_WRITE - Sets the spectrum analyzer to clear previous sweep data off the display before performing a sweep. Subsequent sweeps may or may not clear the display first, but the data array at the end of the sweep is entirely new. IVISPECAN_VAL_TRACE_TYPE_MAX_HOLD - Sets the spectrum analyzer to keep the data from either the previous data or the new sweep data, which ever is higher. IVISPECAN_VAL_TRACE_TYPE_MIN_HOLD - Sets the spectrum analyzer to keep the data from either the previous data or the new sweep data, which ever is lower. IVISPECAN_VAL_TRACE_TYPE_VIDEO_AVERAGE - Sets the spectrum analyzer to maintain a running average of the swept data. IVISPECAN_VAL_TRACE_TYPE_VIEW - Disables acquisition into this trace but displays the existing trace data. IVISPECAN_VAL_TRACE_TYPE_STORE - Disables acquisition and disables the display of the existing trace data. Default Value: IVISPECAN_VAL_TRACE_TYPE_CLEAR_WRITE

    datatype_icon

    instrument handle out

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

    Default: None

    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