Table Of Contents

IviCounter Configure Duty Cycle (G Dataflow)

Last Modified: October 24, 2017

Configures the IviCounter Duty Cycle Estimate and IviCounter Duty Cycle Resolution properties for a duty cycle measurement.

connector_pane_image
datatype_icon

resolution (1.0 Hz)

Specifies the resolution of the duty cycle measurement. It is the quantization size, or the smallest delta value that can be detected. The driver sets the IviCounter Duty Cycle Resolution property to this value. Units: hertz Default Value: 1.0

datatype_icon

instrument handle

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

channel ("")

Specifies the name of the channel to configure. Pass 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 Value: "" Notes: You can specify the channel name as a string variable or as a literal enclosed in double quotes.

datatype_icon

frequency estimate (300 MHz)

Specifies the estimated measurement frequency. The driver sets the IviCounter Duty Cycle Frequency Estimate property to this value. Units: hertz Default Value: 300000000.0

datatype_icon

instrument handle out

The instrument handle you obtain from IviCounter Initialize or IviCounter Initialize With Options. 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