Operator Terminal Error Messages

BAD CONTINUUM V/F DUMP DETECTED
The continuum V/F hardware has failed.

BEAM CHOPPER MUST BE RUNNING TO
MAKE A VSYNCH OBSERVATION
The user is in CONTinuum mode with the VSYNCH option selected, but has neglected to actually start the beam chopper with the CSTART command. The user must start the beam chopper and then start the desired data collection routine.

BEAM CHOPPER SHOULD BE OFF TO MAKE A
DVM/VTOF/CPOL OBSERVATION
The user is in CONTinuum mode with any but the VSYNCH option selected and has left the beam chopper running. The user should stop the beam chopper with the CMAIN command and then start the desired data collection routine.

CANNOT MAKE A SPEC LINE OBSERVATION WHILE BEAM CHOPPER IS RUNNING
The user is in SPEC mode, but has left the beam chopper running. The beam chopper should be stopped with the CMAIN command. Then the user can start the desired data collection routine.

CANNOT MAKE A TOTAL POWER OBSERVATION WHILE FREQUENCY SWITCHING
The user is in SPEC mode, but is attempting to use a data collection program that is not compatible with frequency switching (ON, OFF, PS, DPS, FIVE). The user should turn off frequency switching with the FSOFF command and then start the desired data collection routine.

CANNOT MAKE FS OBSERVATION IN CONTINUUM MODE
The user has left frequency switching running in CONTinuum mode. The user should turn off frequency switching with the FSOFF command and then start the desired data collection routine.

CANNOT TAKE AN FS OBSERVATION WITHOUT ACTUAL FREQUENCY SWITCHING
The user has forgotten to turn on frequency switching before attempting to start the "FS" data collection routine. The user should enter the command FSON and then start FS.

CAUTION-DISK EPHEMERIS INADEQUATE FOR TRACKING BEYOND DATE CHANGE
The disk planet/sun/moon ephemeris is nearly out-of-date. It must be updated (see Chapter 5.6).

CHECK DATE COVERAGE OF DISK EPHEMERIS
Check the planet/sun/moon disk ephemeris coverage by typing PLANET and updating the disk if necessary (see Chapter 5.6).

COMMANDED POLARIZER POSITION OUT OF
LIMITS (ALARM 20)
The polarizer position angle has been set to an illegal value. The polarizer has not really been moved there. Either command a legal angle (in the range 10 to 350 ) or turn off alarm 20.

COMMAND PROCESSING HAS ABORTED-
REENTERING KEYBOARD MODE
The operator communication task has aborted during processing of the most recent line. The system has reset a number of pointers and returned itself to the KEYBOARD mode. The user will have to restart any operations that were pending.

DATA-STORING PROGRAM HAS ABORTED-
ATTEMPTING TO CONTINUE
In the process of storing spectral line mode data, the storage program has bombed. Try a short scan to see if the problem recurs. If it does call for help.

DATA-TAKING HAS HUNG UP-ATTEMPTING TO RECOVER
If an illegal interrupt wanders into the software, it can stop data- taking. If data-taking stops for no good reason, the system starts it up again and prints this informative message.

DVM READ ERROR-DATA INVALID
The dvm status never indicates that the reading is valid. This may happen while the dvm is overloading. Data-taking may continue, but the data stored will be invalid. Controlled by ALARM 11.

EPHEM. OUT OF DATE-MOUNT EPHEM. TAPE AND TYPE START EPH
The user has attempted to use the sun/moon/planet coordinate library, and the library is out-of-date. It must be updated using the ephemeris update program (see Chapter 5.6).

ERROR DURING CARD/LST/UTC STARTUP
The user has attempted to enter one of the non- KEYBOARD modes of observing and tried to start with an illegal or non-existent disk record. Check that the files are all right (via program CARD ) and that the user has typed in the correct sequence of keywords and arguments for the mode desired.

ERROR DURING DATA-TAKING ROUTINE STARTUP. CODE=
The user has attempted to make continuum measurements using synchronous detection, but there was an error. Save the error code that follows the message, but a possible fix is to remove any non-essential programs that might have been running when data-taking was begun.

ERROR IN LINE-ATTEMPTING TO CONTINUE
A line image contains a sequence of keywords and arguments that is incorrect. Processing will attempt to continue.

ERROR IN READING DISK EPHEMERIS
There was some sort of I/O problem while checking the ephemeris disk file. If problem persists, check that disk partition is online (see if an 'offline' message for PLN is on the Lear-Siegler terminal, and correct if present). If it is, try replacing the ephemeris disk file (see Chapter 5.6).

ERROR IN READING-INDUCTOSYN
The tracking programs are having difficulty reading either the AZ or EL shaft encoder. If problem persists, inform staff. Controlled by ALARM 13,

FSYN (COMPUTED) BEYOND LIMITS
The computed synthesizer frequency is not within preset tolerances. Another HARM , FSBAND combination must be used. Check screen 8 for a list of valid combinations. Until a correct combination is entered, the alarm will go off, and the last legal synthesizer frequency will continue to be sent out. Controlled by ALARM 3.

FUNCTIONS NESTED DEEPER THAN 5 LEVELS-
LOWER LEVELS IGNORED
The user has defined functions that call functions that call functions that . . . . The nesting was too deep. This error is caught when the function is executed, not when the function is defined.

GUN OSCILLATOR OVERHEATING
The Gunn oscillator in the 3 mm cooled mixer receiver is overheating. Call the staff. This message is controlled by ALARM 17 and the sensor is controlled by sensor 17.

I.F. CHAIN OVERHEATING
The IF chain in the 3 mm cooled receiver is overheating. Call the staff. This message is controlled by ALARM 18 and the sensor is controlled by sensor 18.

IS A BASIC KEYWORD-IT CANNOT BE A FUNCTION
The user has attempted to define or query a function whose name is already a basic keyword.

JUST ATTEMPTED TO RESTART WATCH
The data taking programs hung up and automatic restart was employed to get things going again.

KEYBOARD INPUT WAS ONLY PROCESSED TO FIRST WAIT-TYPE FUNCTION
The user has attempted to input a series of commands through the keyboard while another command line image (input from disk) had been partially processed and was waiting for some action to be completed. All keyboard commands up through the first wait-type command were processed.

LEVELS BEYOND TOLERANCE
The electronic levels used to aid in pointing corrections have exceeded preset tolerances. Watch out for earthquakes. Controlled by ALARM 7.

LINE NOT FOUND IN LIST
The user has attempted to enter a line frequency via the LINE keyword, and the named line was not found in the list.

MORE THAN 1024 CHANNELS REQUESTED
The user has attempted to configure the backends such that more than 1024 channels of data would result. The allowed upper limit is 1024.

NO MORE ROOM FOR FUNCTION DEFINITIONS
The user has attempted to add a 21st function (in addition to FNA, FNB). Only 20 are allowed.

NON-EXISTENT FILTERBANK REQUESTED
The user has attempted to configure backends using an illegal filterbank device identifier (only F1, F2, F3, F4, F5, F32, and F51 are allowed).

NO SUCH FUNCTION
The user has attempted to query a function that does not exist.

NOT ENOUGH MEMORY TO RUN DATA-TAKING PROGRAM
There was not enough computer memory to load the data-collection program. Try reducing the amount of computer activity (stop SPA) and then try restarting data-collection.

POLARIZATION SWITCHING SHOULD BE OFF FOR ALL BUT PLSW OBSERVATIONS
The user has left the polarizer in a switching mode, and should enter the command POLS 0 to terminate polarization switching before attempting to start any data collection programs.

POSSIBLE RADOME HUMIDITY PROBLEM
The radome dewpoint temperature equals or exceeds the outdoor air temperature. This message is controlled by ALARM l4. Check that the dehumidifier is running and/or that the dewpoint/outdoor temperature sensor unit (in the annex) is on.

RECEIVER OUT OF LOCK
The S-band receiver has gone out of lock. Controlled by ALARM 5.

SOURCE NOT IN CATALOG
The user has attempted to enter the coordinates of a source from either the FCRAO or USER catalogs, and the source was not found.

STATION CLOCK JUMPED XXXX SECONDS
The station clock has glitched. This alarm will continue to sound until it is turned off and then on again. Controlled by ALARM 15.

SUBR BEYOND LIMTS: SA= SB= SC=
The command position is beyond the subreflector's physical limits. Until the subreflector is commanded to a position it can reach, it will not move under computer control. Controlled by ALARM 1.

SUBR NOT AT COMMAND POSITION:
Unless the subreflector screws are within a fixed tolerance of the commanded position, this alarm will sound. Controlled by ALARM 2.

SUBR-READ PROBLEM
The tracking programs are having difficulty reading the A, B, C, or Y axis subreflected dvm's. If problem persists, inform staff. Controlled by ALARM 12.

SYNTAX ERROR
The user has made a syntax error of some sort (illegal characters, too many characters, illegal separators) while configuring the backends. Read the manual description of how to configure the backends.

TELESCOPE HALTED NEAR AZ LIMIT-BACK OUT MANUALLY
The telescope has approached either the lower (AZ=38$^\circ$ ) or upper (AZ=680$^\circ$ ) cablewrap limit, and the computer has attempted to halt the telescope. IT WILL ONLY SUCCEED IF THE TELESCOPE IS UNDER COMPUTER CONTROL. To get out of this situation, assuming the telescope has not hit a limit switch:

1. put telescope under manual control
2. move it away from limit until alarm stops sounding
3. command telescope to an accessible position
4. put telescope back under computer control and type POINT . Controlled by ALARM 4.

TODAY NOT FOUND IN DISK EPHEMERIS
In the process of starting up planet/sun/moon tracking, the disk ephemeris was read, but the current date was not found. Check the disk ephemeris coverage by typing PLANET , and update the disk if necessary.

TOTAL POWER DRIFTING
During an observation, the total power has drifted more than a preset amount from the start of the observation. Either stop the observation or increase the tolerance. Controlled by ALARM 6.

TRACKING IS DEAD-
RESTART IT OR CHANGE SOURCE NAMES
Either the sun/moon/planets tracking program is dead or else the user has changed sources but has failed to change both the MAIN and REF source names. Controlled by ALARM 10.

UNDEFINED FUNCTION: -PROCESSING CONTINUES
The user has made a non-existent function into part of a non-keyboard mode command line image. The junk word is ignored and processing continues.

VCO OUT OF LOCK:
Part of the LO system is out of lock. Controlled by ALARM 8 and SENSOR 15.

WARNING - ADJUSTED DATA-TAKING PARAMETERS TO ACHIEVE CONSISTENCY.
TO SEE CHANGES, DISPLAY SETTINGS FOR CURRENT
MODE OF OBSERVATION
The user has started a data-collection program with a set of parameters that are not quite correct. The program has made adjustments to them so that data collection can proceed. The user should enter the keyword associated with the data-collection program (e.g., DPS) in order to see what the current parameters are.

WWVB CLOCK: HARDWARE PROBLEM???
The WWVB clock always appears to have valid data. It should not. Something is wrong. Controlled by ALARM 15.

WWVB CLOCK: LEAP YEAR SWITCH WRONG
On the back of the clock is a switch to inform the clock that it is, or is not, a leap year. If the computer senses the setting to be wrong, the alarm goes off. Controlled by ALARM 15.

WWVB CLOCK: LOST TIME SYNC
The clock has lost synchronization with WWVB. Controlled by ALARM 15.

WWVB CLOCK: TIME NOT VALID
The "data valid" signal has not been set in the past 2 seconds. Something is wrong. Controlled by ALARM 15.

WWVB CLOCK: TIME ZONE SWITCH WRONG
On the back of the clock are some digi-switches used to determine the time zone for the displayed time. These should always be set to zero. Controlled by ALARM 15.

Y-AXIS ERROR=
The actual subreflector Y-axis position differs from the commanded position by more than a preset amount. Controlled by ALARM 9.

YOU LEFT OFF THE ALERT TIME
The user has attempted to set or reset the data-taking alarm without the necessary numerical argument.