This is a list of miscellaneous commands that could prove helpful in certain circumstances. The commands aren't part of the standard documented TCS command vocabulary, but they have certain specialized uses that may get you out of a hole or quickly accomplish something for which there is no easy answer.
This list will be expanded as I or the telescope operators think of things, or experience a need.
Displays the three pointing coefficients Ih, Id, and Ch. Don't overlook the starting dot character.
Displays the type of currently active pointing data set: CASS or COUDE.
Displays the running software's version number. This is NOT (necessarily) the version on any diskettes in the drives. (1996-C or later)
Compares the running software's version number with that on the diskettes in the drives. Replies -OK if they match, otherwise, error message. Put some old disks in the drives (don't boot them, please) and try it. Replace the old disks with the proper ones. (1996-C or later)
Resets the three pointing coefficients to zero WITHOUT MOVING THE TELESCOPE. Use this if one or more of the coefficients becomes huge, for example because of pressing PB5 at the wrong time. Before this command was implemented, clearing the coefficients would cause the telescope to displace the former amount of the coefficients. (Useage note: even though there are three coefficients, this command is singular; if made plural, it would conflict with another definition.)
n is the number of seconds for the dome vignetting warning interval. The default is currently 10. The default is restored on reboot.
Sets up the function keys for use with an HDS terminal as a backup to Max.
Displays the startup messages including the software version and date and features of this revision. Takes no action, only displays stuff. NOTE: This displays a text block from the diskette that is currently in Drive 0 and may not reflect what is in memory, if the last boot wasn't done from this diskette. (Most of the time, booting probably occurred from the diskettes currently in the drives.)
The name of the TCS application vocabulary. Once in a while the software may get derailed from this vocabulary and not recognize the usual typed commands. Typing PROG restores the command vocabulary. You don't want to know why it's named PROG. Don't even ask.
The operator's terminal interface card or the software driver at the LSI-11 end may get reset or otherwise go off-line. This command does a re-initialization of the software and hardware. It can't control very well the interface and software at the other end.
Planck interfaces with the LSI-11 for on-line commands to the TCS from application software. The terminal interface card or the software driver at the LSI-11 end may get reset or otherwise go off-line. This command does a re-initialization of the software and hardware. It can't control very well the interface and software at the other end.
The autoguider interfaces with the LSI-11 for on-line commands to the TCS. The terminal interface card or the software driver at the LSI-11 end may get reset or otherwise go off-line. This command does a re-initialization of the software and hardware. It can't control very well the interface and software at the other end.
This is the equivalent of typing GO, if the absolute encoders are down. The telescope will probably be at either the zenith or the stow position; in both cases, you know what the coordinates are, so enter them with the command. You MUST enter a set of coordinates, exactly in this format, or the command will fail.
In case the function keys don't work directly, just type their names.
The "stack" is a repository of numbers to be used by commands expecting arguments, which eat the number(s) off the stack as they use them. Some commands (EPOCH for example) expect either a number on the stack or nothing on the stack (no numerical entry before the command name). If there is nothing on the stack, the command simply displays the current value of whatever item the command is involved with (year in the case of EPOCH). Sometimes, numerical junk may accumulate on the stack without your knowing it, resulting in unexpected behavior by the command. To inspect the stack, type DUS which stands for "DUmp Stack". If there is nothing on the stack, you just get -OK. Otherwise, the first number displayed is the address of the top of the stack; the following number(s) are the values on the stack. The stack is not altered by this command.
There are a number of ways to clear the stack. This command is one. Typing a series of periods separated by spaces is another. Any error clears the stack; type an unrecognized command, such as XXX.
On the IRTF net, at any workstation, switch to directory /benchmark/skymap/ for this command. Use "tcscomm" at the Unix prompt to check the communications link between the observing computer (stefan) and the TCS. If the comm link is working correctly, pressing the Enter key will produce an -OK response from the TCS. You can enter Forth TCS commands also, and the response from the TCS (one line only) will be displayed. Exit with >ESC<->ENTER<. If the comm link is broken, check all cables and A/B switches in the path between stefan and the TCS. The "tcsd" daemon may be inoperative on stefan. See http://irtf.ifa.hawaii.edu/irtf/to_tips/index.html item #2 (Telescope Operator's Tips and Tricks page, left pane) for information about the TCS communications daemon.
Occasionally, a change to the default slew limits is needed. These limits are carried as Forth constants and are defined as follows:
|
+DLIM |
69:56:00.0 |
|
-DLIM |
-59:00:00.0 |
|
HLIMIT |
5:04:47.00 |
To change a limit, type the new limit in one of the following strings:
dd:mm:ss.s D.S ' +DLIM 2!
dd:mm:ss.s D.S ' -DLIM 2!
hh:mm:ss.ss D.SS ' HLIMIT 2!
Note that the default limits will be restored on reboot.
To check on the limits, type this:
+DLIM HH:MM:SS.S
-DLIM HH:MM:SS.S
HLIMIT HH:MM:SS.SS