IviCounterBase Behavior Model
The following state diagram shows relationships between IviCounter frequency measurement capabilities (non-totalize measurements) and counter behavior.
Event Trigger Behavior Model
The following state diagram shows relationships between IviCounter totalize measurement capabilities (non-frequency measurements) and analyzer behavior.
Totalize Behavior Model
The main state in the IviCounter Class is the Idle state. The counter enters the Idle state when it is poweredon, it completes a measurement, or when you abort a previous measurement with the IviCounter Abort VI. Typically, you configure the counter while it is in the Idle state by calling the configure measurement functions. Each measurement has corresponding estimate and resolution parameters that characterize the measurement. The driver uses the estimate and resolution to calculate and set physical instrument parameters. For example, the eestimate and resolution for the IviCounter Configure Frequency Manual VI provide the necessary information for calculating instrument parameters such as gate time, averaging on or off, digits of resolution, and so on. You also can configure the IviCounter properties individually with the IviCounter Property Node.
The Measure, IviCounter Read, and IviCounter Initiate VIs cause the counter to leave the Idle state and transition to the Wait-For-End-Of-Measurement state. The Measure and IviCounter Read VIs do not return until the measurement process is complete and the counter has returned to the Idle state. The IviCounter Initiate VI returns as soon as the counter leaves the Idle state.
Use the IviCounter Fetch VI to retrieve data measurements initiated by the IviCounter Initiate VI. The measurement data returned from the Measure, IviCounter Read, and IviCounter Fetch VIs is acquired after the counter has left Wait-For-End-Of-Measurement state.