Keysight Technologies N8262A P Series User Manual page 133

–
–
–
–
–
–
–
–221
–
Keysight N8262A User's Guide
Invalid block data
A block data element was expected but was invalid for some reason. For example,
161
*DDT #15FET. The 5 in the string indicates that 5 characters should follow, whereas in
this example there are only 3.
Block data not allowed
A legal block data element was encountered but not allowed by the power meter at this
168
point.
For example, SYST:LANG #15FETC?.
Expression data not allowed
A legal expression data was encountered but not allowed by the power meter at this
178
point.
For example, SYST:LANG (5+2).
Trigger ignored
211
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.
Init ignored
Indicates that a request for a measurement initiation was ignored as the power meter
213 was already initiated.
For example, INIT:CONT ON
INIT.
Trigger deadlock
214
TRIG:SOUR was set to HOLD or BUS and a READ? or MEASure? was attempted,
expecting TRIG:SOUR to be set to IMMediate.
Parameter error; Frequency list must be in ascending order.
220
Indicates that the frequencies entered using the MEMory:TABLe:FREQuency command
are not in ascending order.
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.
Data out of range
A numeric parameter value is outside the valid range for the command.
222
For example, SENS:FREQ 2 kHZ.
Maintenance 4
133