Technical data
SYSTem Subsystem 12
N1911A/1912A P-Series Power Meters Programming Guide 519
–168 Block data not allowed
A legal block data element was encountered but not allowed by the power meter at 
this point.
For example SYST:LANG #15FETC?.
–178 Expression data not allowed
A legal expression data was encountered but not allowed by the power meter at 
this point.
For example SYST:LANG (5+2).
–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 2KHZ. 
–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.










