Filter
Top Products
Error Messages 31
ESG Family Signal Generators -299 to -200: Execution Errors
Data out of range; value clipped to upper limit.
An input value is above the maximum value allowed. Examples: frequency
setting, reference, or offset; output power; power reference and offset;
modulation depth, deviation, or modulation source frequency; number of
points and start/stop values for list mode; start/stop values for internal I/Q
calibration; sequence or register values (save/recall); dwell time.
-221 Settings conflict
A legal program data element was parsed but could not be executed due to
the current device state (see IEEE 488.2 11.5.1.1.5).
Settings conflict; At least one of the channels must be on in
order to turn the mode on. CDMA2000 has been turned off.
To output a valid RF signal, at least one channel must be turned on. Since
all channels are off, CDMA2000 mode has been turned off to avoid
undefined behavior.
Settings conflict; At least one of the channels must be on in
order to turn the mode on. WCDMA has been turned off.
To output a valid RF signal, at least one channel must be turned on. Since
all channels are off, W-CDMA mode has been turned off to avoid undefined
behavior.
Settings conflict; BBG Data Clock is fixed to EXTernal to
synchronize Data Gen to Demodulator.
With both the GSM format and the BERT GSM activated, an attempt was
made to toggle the baseband data clock from external to internal. The
baseband data clock is fixed to external in order to synchronize the data
generator to the demodulator.
Settings conflict; Cannot have a secondary frame with a
non-framed data pattern. The secondary frame is unchanged.
The secondary frame feature has many potential conflicts. Some of the
conflicts leave the secondary pattern and its state as they were prior to the
command that led to the error message, and some turn off the secondary
state, since the primary state is not compatible and it has priority.
Settings conflict; Cannot have a secondary frame with all
timeslots off. The secondary frame is unchanged.
The secondary frame feature has many potential conflicts. Some of the
conflicts leave the secondary pattern and its state as they were prior to the
command that led to the error message, and some turn off the secondary
state, since the primary state is not compatible and it has priority.