:MEASure:AMPLitude:PIZeros

Deprecated command. For FlexDCA revision A.05.60 and above, use the :MEASure:AMPLitude:PI command instead.

Command Syntax

:MEASure:AMPLitude:PIZeros

Query Syntax

:MEASure:AMPLitude:PIZeros?

Description

Moves the dual-dirac periodic interference (PI) measurement for logic level zero to the top of the table. Displays the measurement if it is not already shown on the table. The query form of the command returns the measured value.

The following measurement commands are also available:

PI δ-δ for one levels
PI rms for one levels
PI rms for zero levels

BUI and Periodic Jitter (PI) are one component of Deterministic Jitter (DI). Whether PI or BUI is reported depends on the spectral method used to separate any BUI from the Random Noise (RN). This setting is made with the :MEASure:JITTer:DEFine:SMEThod command and can be one of the following three choices:

Auto: BUI or PI is reported in the results table. On each data acquisition cycle, both the spectral and tail-fit methods can be used to separate the BUI values from the RN. The decision to use the spectral or tail-fit method is made on a per-edge basis. So, the result may be a combination of spectral and tail-fit results. If tail fit is used in any case, the TF annotation is displayed in the heading of the Jitter results table. Otherwise, no annotation is displayed. Use the :MEASure:AMPLitude:SMEThod? query to determine the actual method used for the current data acquisition.
Spectral: PI is reported in the results table. This is the standard method used in all FlexDCA versions previous to revision A.02.50 to decompose the jitter and interference components. This method is best used when it is known that BUI is not present on the signal. This is the default method used.
Tail Fit: BUI is reported in the results table. The tail-fit method is exclusively used to separate the BUI from the RN directly from the histogram. The TF annotation is displayed in the heading of the Jitter results table. Unless troubleshooting, do not select this method as it is less accurate than using Auto or Spectral.

Use the :MEASure:DEFine:LEVel command to specify whether the zerp levels are defined as the average zero levels or whether they are specified in terms of a minimum number of consecutive identical digits (CID).

Requires Jitter Mode with additional Advanced Amplitude Analysis/RIN/Q-Factor license .

Amplitude analysis must be turned on before the first interference measurement can be made. Use the :MEASure:AMPLitude:DEFine:ANALysis command.

Common Measurement Child Queries

Common measurement queries. :COUNt?, :LOCation?, :MAXimum?, :MINimum?, :MEAN?, and :SDEViation?.

Example Command Sequence

:MEASure:AMPLitude:DEFine:ANALysis ON
:MEASure:AMPLitude:PIZeros:SOURce CHAN1A
:MEASure:AMPLitude:PIZeros
:MEASure:AMPLitude:PIZeros?