:LTESt:MEASure:MLIMit:UPACtion

Command Syntax

:LTESt:MEASure:MLIMit{1:16}:UPACtion {FAIL | PASS | IGNore}

Where {1:16} identifies one of sixteen limit tests.

Query Syntax

:LTESt:MEASure:MLIMit:UPACtion?

Description

Selects an action to be taken if the measurement limit test cannot be performed. Use one of the following arguments:

FAIL

If the measurement cannot be made, for example when an edge is expected to be present and is not found, the total number of waveforms is incremented and the total number of failures is incremented. This is the mode to use for most applications.

PASS

If the measurement cannot be performed, pass the measurement and do not count it as a failure. You might use PASS when triggering on one event and measuring another event which may not occur for every trigger. For example, in a communications test system, you might want to trigger on the clock and test the risetime of edges in the data stream. However, there may be no way to guarantee that a rising edge will be present to measure in the data stream at every clock edge. By using the PASS parameter, the limit test will not log a failure if there is no edge found in the data stream. If the measurement cannot be made, the total number of waveforms measured is incremented, but the total number of failures is not.

IGNore

If the measurement cannot be performed, ignore the measurement and do not count it as a pass or fail. IGNore is similar to PASS, except the totals for the number of waveforms and failures are not incremented. Therefore, the total indicates the number of tests when the measurement was made.

Use the :STATe sibling command to start the limit test.