10 Maintenance
270 Keysight N1911A/1912A User’s Guide
–
211
Trigger ignored
Indicates that <GET> or *TRG, or TRIG:IMM was received and recognized by the device but was ignored
because the power meter was not in the wait for trigger state.
–213
Init ignored
Indicates that a request for a measurement initiation was ignored as the power meter was already initiated.
For example, INIT:CONT ON
INIT.
–214
Trigger deadlock
TRIG:SOUR was set to HOLD or BUS and a READ? or MEASure? was attempted, expecting TRIG:SOUR to be
set to IMMediate.
–220
Parameter error;Frequency list must be in ascending order.
Indicates that the frequencies entered using the MEMory:TABLe:FREQuency command are not in ascending
order.
–221
Settings conflict
This message occurs under a variety of conflicting conditions. The following list gives a few examples of
where this error may occur:
If the READ? parameters do not match the current settings.
If you are in fast mode and attempting to switch on for example, averaging, duty cycle or limits.
Trying to clear a sensor calibration table when none is selected.
–222
Data out of range
A numeric parameter value is outside the valid range for the command.
For example, SENS:FREQ 2 kHZ.
–224
Illegal parameter value
A discrete parameter was received which was not a valid choice for the command. You may have used an
invalid parameter choice.
For example, TRIG:SOUR EXT.
–226
Lists not same length
This occurs when SENSe:CORRection:CSET[1]|CSET2:STATe is set to ON and the frequency and calibration/
offset lists do not correspond in length.
–230
Data corrupt or stale
This occurs when a FETC? is attempted and either a reset has been received or the power meter state has
changed such that the current measurement is invalidated (for example, a change of frequency setting or
triggering conditions).