Table Of Contents

IviFgen Configure Data Marker [DM] (G Dataflow)

Version:
    Last Modified: October 24, 2017

    Configures the common data marker properties. These properties are the data marker source channel, bit position, and destination.

    spd-note-note
    Note  

    This node is part of the IviFgenDataMarker [DM] extension group.

    connector_pane_image
    datatype_icon

    Bit Position

    Pass the bit position of the waveform data bit that will be output as a data marker. A value of 0 indicates the least significant bit. The driver sets the IviFgen Data Marker Bit Position [DM] property to this value. Default Value: None

    datatype_icon

    instrument handle

    The instrument handle that you obtain from the IviFgen Initialize or IviFgen 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

    Marker Name ("")

    Pass the name of data marker to configure. A data marker name is a repeated capability identifier defined by specific drivers for the data marker that corresponds to a specified index. The name uniquely identifies a data marker in the data markers collection. Call the IviFgen Get Data Marker Name [DM] VI to get the marker name for the data marker that corresponds to a one-based index. Users who want to achieve interchangeability should use a virtual data marker name. The virtual data marker name should be sufficiently specific to the test system such that it is unlikely to conflict with a physical data marker name. Default Value: "" Notes: You can specify the marker name as a string variable or as a literal enclosed in double quotes.

    datatype_icon

    channel name

    Specifies the virtual channel name that you assign to the instrument in the Configuration Utility. Users who want to achieve interchangeability should use a virtual channel name. The virtual channel name should be sufficiently specific to the test system such that it is unlikely to conflict with a physical channel name. 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.

    Default: ""

    datatype_icon

    Destination Terminal (None)

    Specifies destination terminal for the data marker. The driver sets the IviFgen Data Marker Destination [DM] property to this value. Valid Values: IVIFGEN_VAL_TRIGGER_SOURCE_NONE ("") - No trigger source IVIFGEN_VAL_TRIGGER_SOURCE_IMMEDIATE ("Immediate") - Trigger immediately IVIFGEN_VAL_TRIGGER_SOURCE_EXTERNAL ("External") - External trigger source IVIFGEN_VAL_TRIGGER_SOURCE_INTERNAL ("Internal") - Internal trigger source IVIFGEN_VAL_TRIGGER_SOURCE_SOFTWARE ("Software") - Software trigger IVIFGEN_VAL_TRIGGER_SOURCE_LAN0 ("LAN0") - LAN0 IVIFGEN_VAL_TRIGGER_SOURCE_LAN1 ("LAN1") - LAN1 IVIFGEN_VAL_TRIGGER_SOURCE_LAN2 ("LAN2") - LAN2 IVIFGEN_VAL_TRIGGER_SOURCE_LAN3 ("LAN3") - LAN3 IVIFGEN_VAL_TRIGGER_SOURCE_LAN4 ("LAN4") - LAN4 IVIFGEN_VAL_TRIGGER_SOURCE_LAN5 ("LAN5") - LAN5 IVIFGEN_VAL_TRIGGER_SOURCE_LAN6 ("LAN6") - LAN6 IVIFGEN_VAL_TRIGGER_SOURCE_LAN7 ("LAN7") - LAN7 IVIFGEN_VAL_TRIGGER_SOURCE_LXI0 ("LXI0") - LXI Trigger Bus Line 0 IVIFGEN_VAL_TRIGGER_SOURCE_LXI1 ("LXI1") - LXI Trigger Bus Line 1 IVIFGEN_VAL_TRIGGER_SOURCE_LXI2 ("LXI2") - LXI Trigger Bus Line 2 IVIFGEN_VAL_TRIGGER_SOURCE_LXI3 ("LXI3") - LXI Trigger Bus Line 3 IVIFGEN_VAL_TRIGGER_SOURCE_LXI4 ("LXI4") - LXI Trigger Bus Line 4 IVIFGEN_VAL_TRIGGER_SOURCE_LXI5 ("LXI5") - LXI Trigger Bus Line 5 IVIFGEN_VAL_TRIGGER_SOURCE_LXI6 ("LXI6") - LXI Trigger Bus Line 6 IVIFGEN_VAL_TRIGGER_SOURCE_LXI7 ("LXI7") - LXI Trigger Bus Line 7 IVIFGEN_VAL_TRIGGER_SOURCE_TTL0 ("TTL0") - TTL Interface 0 IVIFGEN_VAL_TRIGGER_SOURCE_TTL1 ("TTL1") - TTL Interface 1 IVIFGEN_VAL_TRIGGER_SOURCE_TTL2 ("TTL2") - TTL Interface 2 IVIFGEN_VAL_TRIGGER_SOURCE_TTL3 ("TTL3") - TTL Interface 3 IVIFGEN_VAL_TRIGGER_SOURCE_TTL4 ("TTL4") - TTL Interface 4 IVIFGEN_VAL_TRIGGER_SOURCE_TTL5 ("TTL5") - TTL Interface 5 IVIFGEN_VAL_TRIGGER_SOURCE_TTL6 ("TTL6") - TTL Interface 6 IVIFGEN_VAL_TRIGGER_SOURCE_TTL7 ("TTL7") - TTL Interface 7 IVIFGEN_VAL_TRIGGER_SOURCE_PXI_STAR ("PXI_STAR") - PXI Star Interface IVIFGEN_VAL_TRIGGER_SOURCE_PXI_TRIG0 ("PXI_TRIG0") - PXI Trigger Bus Line 0 IVIFGEN_VAL_TRIGGER_SOURCE_PXI_TRIG1 ("PXI_TRIG1") - PXI Trigger Bus Line 1 IVIFGEN_VAL_TRIGGER_SOURCE_PXI_TRIG2 ("PXI_TRIG2") - PXI Trigger Bus Line 2 IVIFGEN_VAL_TRIGGER_SOURCE_PXI_TRIG3 ("PXI_TRIG3") - PXI Trigger Bus Line 3 IVIFGEN_VAL_TRIGGER_SOURCE_PXI_TRIG4 ("PXI_TRIG4") - PXI Trigger Bus Line 4 IVIFGEN_VAL_TRIGGER_SOURCE_PXI_TRIG5 ("PXI_TRIG5") - PXI Trigger Bus Line 5 IVIFGEN_VAL_TRIGGER_SOURCE_PXI_TRIG6 ("PXI_TRIG6") - PXI Trigger Bus Line 6 IVIFGEN_VAL_TRIGGER_SOURCE_PXI_TRIG7 ("PXI_TRIG7") - PXI Trigger Bus Line 7 IVIFGEN_VAL_TRIGGER_SOURCE_PXIE_DSTARA ("PXIe_DSTARA") - PXI Express DStar Line A IVIFGEN_VAL_TRIGGER_SOURCE_PXIE_DSTARB ("PXIe_DSTARB") - PXI Express DStar Line B IVIFGEN_VAL_TRIGGER_SOURCE_PXIE_DSTARC ("PXIe_DSTARC") - PXI Express DStar Line C IVIFGEN_VAL_TRIGGER_SOURCE_RTSI0 ("RTSI0") - RTSI Bus Line 0 IVIFGEN_VAL_TRIGGER_SOURCE_RTSI1 ("RTSI1") - RTSI Bus Line 1 IVIFGEN_VAL_TRIGGER_SOURCE_RTSI2 ("RTSI2") - RTSI Bus Line 2 IVIFGEN_VAL_TRIGGER_SOURCE_RTSI3 ("RTSI3") - RTSI Bus Line 3 IVIFGEN_VAL_TRIGGER_SOURCE_RTSI4 ("RTSI4") - RTSI Bus Line 4 IVIFGEN_VAL_TRIGGER_SOURCE_RTSI5 ("RTSI5") - RTSI Bus Line 5 IVIFGEN_VAL_TRIGGER_SOURCE_RTSI6 ("RTSI6") - RTSI Bus Line 6 Default: IVIFGEN_VAL_TRIGGER_SOURCE_NONE ("") - No trigger source

    datatype_icon

    instrument handle out

    The instrument handle that you obtain from the IviFgen Initialize or IviFgen 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