ICIMACS for TIFKAM: Software Notes

9/17/99 : JAM


STARTUP PROBLEMS

WC Startup Fails

Symptom: WC startup hangs for 30 seconds or so on the line beginning "TCPPORT.EXE .....", followed by the message "Unable to open", followed by several commented out lines scrolling down the screen.

Solution: Try restarting several times by typing "WC" on the WC keyboard. If by the sixth try or so it still won't start, wait ten minutes and try again. While waiting, try logging into the prospero machine from another network machine, to make sure that it is accepting telnet sessions.

Prospero Startup Fails

Symptom: After typing "startup" on prospero, prospero reports errors

Solution: Try typing "startup" several times in succession. If this doesn't work, try typing "WC RESTART", followed by two more "startup"s. If the problem is disk synchronization, follow the directions below.

Disk Synchronization

Symptom: prospero reports "-Synch" in its status screen.

Solution: Users occasionally note that they are having difficulty getting the data disks between the WC and IC to synchronize on startup. If full reboots are not solving the problem, you can attempt to force synchronization of the disks manually: Check the WC status screen. Near the middle of the screen is a box with disk synchronization information. If any of the machines' names are followed by the word "-SYNCH", follow the directions below.

CB -SYNCH:
Make sure that caliban is running on the sparc station, then type

>WC REQ INITDISK

in the caliban console window.

IC -SYNCH:
On the WC keyboard, type

>IC REQ INITDISK

Note: If the instructions above don't help, then it may be the case that the WC was not able to detect the IC disks on startup. The only fix is to follow the TIFKAM startup procedure.


CRASHES

The TIFKAM IC at the 1.3m occasionally crashes without warning during image acquisition. If you suspect that the IC has crashed, first check the status string in the upper right hand corner of either IC display. This string will read "OFFLINE" if the IC has crashed; if this is the case, go to the IC keyboard, type IC and press enter to restart the IC program, then type "startup" at prospero (several times if necessary) to reinitialize the system, then restart the interrupted observation. The ISL is working to solve this problem, and will distribute repaired code as soon as it is available.

There is some scant evidence that attempting to change readout parameters during readout may cause these crashes to occur more frequently. You may want to avoid doing commands like EXP, ICSCALE, or moving mechanisms while acquiring images.

There is even scanter evidence that rebooting the IC may be more effective in preventing these crashes then simply restarting the IC as described above.


Imaging Sciences Laboratory
Revised: September 17, 1999 [jam]