Table Of Contents

IviScope Configure Edge Trigger Source (G Dataflow)

Version:
    Last Modified: October 24, 2017

    Configures the edge trigger. An edge trigger occurs when the trigger signal passes through the voltage threshold that you specify with the Trigger Level parameter and has the slope that you specify with the Trigger Slope parameter.

    spd-note-note
    Note  

    This node affects instrument behavior only if the trigger type is IVISCOPE_VAL_EDGE_TRIGGER. Call the IviScope Configure Trigger and IviScope Configure Trigger Coupling nodes to set the trigger type and trigger coupling before calling this node.

    spd-note-note
    Note  

    If the trigger source is one of the analog input channels, you must configure the vertical range, vertical offset, vertical coupling, probe attenuation, and the maximum input frequency before calling this node.

    connector_pane_image
    datatype_icon

    trigger level (0.0 V)

    Pass the voltage threshold you want the oscilloscope to use for edge triggering. The driver sets the IviScope>>Trigger>>Trigger Level property to this value. The oscilloscope triggers when the trigger signal passes through the threshold you specify with this parameter and has the slope you specify with the Trigger Slope parameter. Units: volts.

    spd-note-note
    Note  

    This parameter affects instrument behavior only when you select a channel or the external trigger input as the Trigger Source. You may not configure the trigger level that the oscilloscope uses for other trigger sources, such as VXI TTL trigger lines.

    Default: 0.0

    datatype_icon

    trigger source

    String you pass to specify the source you want the oscilloscope to monitor for a trigger. The driver sets the IviScope>>Trigger>>Trigger Source property to this value.

    Nodes Associated with Trigger Source

    Virtual Channel Names

    Virtual channel names are aliases for instrument-specific channel strings. The instrument-specific channel strings can differ from one instrument to another. Virtual channel names allow you to use and swap instruments without having to change the channel names in your source code. You assign a virtual channel name to an instrument-specific channel through the Configuration Utility. This control accepts virtual channel names you have assigned to the specific instrument you are using. It also accepts the instrument-specific channel names.

    Additional Trigger Sources

    This control accepts one of the valid channel names or additional trigger sources listed below. Additional Trigger Sources: IVISCOPE_VAL_EXTERNAL - External IVISCOPE_VAL_TTL0 - PXI TRIG0 or VXI TTL0 IVISCOPE_VAL_TTL1 - PXI TRIG1 or VXI TTL1 IVISCOPE_VAL_TTL2 - PXI TRIG2 or VXI TTL2 IVISCOPE_VAL_TTL3 - PXI TRIG3 or VXI TTL3 IVISCOPE_VAL_TTL4 - PXI TRIG4 or VXI TTL4 IVISCOPE_VAL_TTL5 - PXI TRIG5 or VXI TTL5 IVISCOPE_VAL_TTL6 - PXI TRIG6 or VXI TTL6 IVISCOPE_VAL_TTL7 - PXI TRIG7 or VXI TTL7 IVISCOPE_VAL_ECL0 - VXI ECL0 IVISCOPE_VAL_ECL1 - VXI ECL1 IVISCOPE_VAL_PXI_STAR - PXI Star IVISCOPE_VAL_RTSI_0 - RTSI line 0 IVISCOPE_VAL_RTSI_1 - RTSI line 1 IVISCOPE_VAL_RTSI_2 - RTSI line 2 IVISCOPE_VAL_RTSI_3 - RTSI line 3 IVISCOPE_VAL_RTSI_4 - RTSI line 4 IVISCOPE_VAL_RTSI_5 - RTSI line 5 IVISCOPE_VAL_RTSI_6 - RTSI line 6
    spd-note-note
    Note  

    IVISCOPE_VAL_EXTERNAL - The oscilloscope waits for a trigger on the external trigger input.

    Default: CHANNEL1

    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