5-22
Status Listings
OSA Warnings
5055 desc = “Firmware Upgrade was not successful”
help => “A firmware upgrade operation was requested. The firmware upgrade
operation cannot be done at this time due to an internal software problem. “ + <-
.serviceCenterHelp
5056 desc = “Trajectory align cannot find input signal”
help = “The trajectory align procedure cannot find a usable input signal. Make
sure you have a signal connected to the optical input.”
5057 desc = “Invalid settings for trajectory align”
help = “The external trajectory align function was requested. It cannot be
executed because the start and/or stop wavelength settings are invalid. Start
and stop wavelengths must be between 600nm and 1700nm. In addition the
difference between start and stop wavelengths (span) must be greater than
25nm. To correct this problem adjust the start and/or stop wavelength settings
to be valid.”
5058 desc = “Out of memory”
help = “The OSA has run out of execution memory. An internal function was
aborted due to lack of execution memory. The correction for this problem is to
cycle power.”
5059 desc = “Trajectory align: marginal input signal”
help = “The trajectory align procedure was aborted due to an input signal with
marginal amplitude. The input signal was large enough when the function began
it’s operation but later became too small. This usually happens when the signal
is on the edge of being too small. To correct this problem increase the input
signal level. If this is not possible then a slight increase in signal level can
sometimes be achieved by cleaning optical fiber connectors.”
5060 desc = “Trajectory align failed”
help = “The trajectory align procedure failed. The trajectory adjustments
computed were invalid. This is usually occurs after the OSA has received a large
mechanical shock. To correct this problem try the trajectory align procedu re
again. If the error persists, contact the Agilent support center nearest your
location.”
5061 desc = “Invalid marker trace”
help = “The marker could not be positioned. The marker is on a trace which does
not contain any valid data. This is sometimes caused by a trace math result
which is invalid.”
Table5-6. OSA Warnings (6 of 12)
Error Number Error Description [description/explanation/examples]