This help file describes the USER STARTUP SEQUENCE FOR THE OVEN.
These instructions are for logging into crater or dorado remotely to monitor the oven without having pilot control capability. If you need to startup the pilot programs, use pilot_login NOT this file.
These instructions assumes that crater (or dorado) is running and that the oven network is intact. These instructions also assume that the on-board VME computers are running. Defaults only work for oven0.
From a PC on the network:
C: CD C:EM4010 C: EM
From another xterm window:
cl> rlogin crater
From another computer:
% telnet crater
The login starts with a blank screen that says: "crater login:" or "dorado login:" You must have an oven account.
After entering the username and password, this should give you a window running IRAF
To logoff, say log.
You will want to load the mirror package in each xterm window (or at least each one you plan to use).
cl> cl> mirror mi>
The "mi>" prompt indicates that the mirror package is loaded. Type "?" for a list of the tasks in the active package.
mi> ? odisp oven ovend oveng ovenw ograph ovenb ovene ovenp tcmark mi>
Check these with "ipcs". There should be 3 segments, one each for on-board computers v0, v1 and v2.
mi> !ipcs IPC status from crater as of Thu Jun 6 18:25:12 1991 T ID KEY MODE OWNER GROUP Message Queues: Shared Memory: m 300 0x00000100 --rw-r--r-- pilot other m 301 0x00000101 --rw-r--r-- pilot other m 202 0x00000102 --rw-r--r-- pilot other Semaphores: mi>
Shared memory segments must be created and initialized by pilot. If they don't exist, the oven isn't running.
If you only want to check for the oven daemons, you can say:
mi> !ps -aux | grep mirror (shows all mirror tasks) mi> mi> !ps -ax | grep N (shows all background tasks) mi>
For a brief description of the daemon's function type: help ovend In normal operation, there are 7 daemons running. Oven tasks appear as "/usr/iraf/mirror/bin.sparc/x_mirror.e" The cls in your xterm windows appear as "/usr/iraf/bin.sparc/cl.e" Background tasks will have an "N" in the STAT column. Note that each background daemon has an associated cl.
mi> oven readonly=yesThe blue window will now continue the oven program talking to the shared memory segment for v0. If the v0 computer is functioning, and ovend is running, you should get fresh data each minute.
If an oven task crashes, use flpr to flush the process cache before restarting. unlearn resets the default parameters for the task.
mi> unlearn oven mi> oven ncomp=0
Start the cron task in the purple window (border):
mi> ovenc &ograph and odisp should now display data at appropriate intervals. To stop the cron task or another daemon, use the IRAF kill command in the relevant window: kill x (where x is the job number [1-4])