:LTESt:MEASure:AMPLitude:LOCation:FREGion
Removed command for revision A.03.00 and above. This command is no longer available. Use :LTESt:MEASure:MLIMit:FREGion
insead.
Command Syntax
:LTESt:MEASure:AMPLitude:LOCation{1:32}:FREGion {INSide | OUTSide | ALWays| NEVer}
Query Syntax
:LTESt:MEASure:AMPLitude:LOCation{1:32}:FREGion?
Description
Defines when to fail an amplitude measurement limit test in Jitter/Noise mode. The amplitude measurement is identified by a number, from 1 to 32, that is appended to the :LOCation
portion of the command. Refer to the :MEASure:AMPLitude:LOCation:STATe command to learn how to identify the measurement and to turn the measurement limit test on or off.
- 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 theLTESt:MEASure:SIMage:STATe
,LTESt:MEASure:SSUMary:STATe
, orLTESt:MEASure:SWAVeform:STATe
commands. You can also useNEVer
to observe one measurement but determine a failure from a different measurement.
Use the following sibling commands to configure the measurement:
:FAILures
defines the number of failures for stopping a limit test:LLIMit
defines the lower limit for failing a measurement:ULIMit
defines the upper limit for failing a measurement:UPACtion
selects an action if the measurement cannot be performed
FlexDCA must be in Jitter/Noise mode with amplitude measurements enabled.
Requires Jitter Mode with additional Advanced Amplitude Analysis/RIN/Q-Factor license .