:LTESt:MEASure:MLIMit:FREGion

Command Syntax

:LTESt:MEASure:MLIMit{1:16}:FREGion {INSide | OUTSide | ALWays | NEVer}

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

Query Syntax

:LTESt:MEASure:MLIMit:FREGion?

Description

Defines when to fail a measurement limit test. Use one of the following arguments:

INSide

A measurement is counted as a failure if it is within the lower and upper limits, which are set by the :LLIMit and :ULIMit sibling commands.

OUTSide

A measurement is counted as a failure when the measurement results exceed the parameters set by :LLIMit and :ULIMit sibling commands.

ALWays

A measurement is counted as a failure every time the measurement is executed, and the parameters set by the :LLIMit and :ULIMit sibling commands are ignored.

NEVer

Logs the action each time the measurement is executed and can be used to monitor measurements. For example, you can use NEVer to track a measurement trend during an environmental test while running a measurement for a long time as the temperature or humidity is changed. Each time the measurement is executed, the results can be logged as determined by the fail action set with the following commands:

• LTESt:MEASure:SIMage:STATe
• LTESt:MEASure:SSUMary:STATe
• LTESt:MEASure:SWAVeform:CHANnel:STATe
• LTESt:MEASure:SWAVeform:DIFF:STATe
• LTESt:MEASure:SWAVeform:FUNCtion:STATe

You can also use NEVer to observe one measurement but determine a failure from a different measurement.

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

Example

:LTESt:MEASure:MLIMit2:FREGion INSide  //  Limit test 2 fails for inside violations.