| [ Home | Telescope | Observing System | Alert | Faults | Commands | Quick Check-List] |
|
In General Most of the faults can be cleared by typing: SYS> startobssys Try to avoid 'shutdownobssys' followed by 'startobssys' as in most cases such a drastic measure isn't needed. SYS> shutdownobssys should only be used to shutdown the observing system at the end of the night.
If a sub-system (DAS, TCS or Autoguider) is corrupted 'shutdownobssys' wont
help. First the sub-system has to be brought back, then
No guide stars, bad pointing
First repeat ZEROSET at zenith in engineering mode followed by:
Check pointing with a pointing grid star and the TV:
If no bright star is seen may be the last pointing solution is wrong or got
corrupted somehow. Before calling for help try this: To recalibrate the telescope pointing follow this commands.
The TCS disconnects
Most likely the TCS TELD task has died. To restart go to the xterminal were
the TCS user interface and info display are running. Open a LAT terminal
and log on to lpas2 (see label on screen for uid and passwd). From the main
menu then select 'options' and 'teld' from the options menu, afterwards
Data acquisition problems By Data acquisition we mean the management of an exposure, reading of data from the CCDs and saving to disk. This may fail in one of several stages, for example:
SYS>dasreset IDS (i.e. startobssys is unnecessary) When this completes, try a new Run and see if the above fault recurs.
If it does, then a lower-level reset of the CCD controller may necessary and
you might need to move the telescope to zenith. Power cycle the SDSU CCD controller, attached to IDS, followed by:
If you are unsure about any of the recovery procedures or if they fail, call for WHT TO, SA or DT/IO support. |
| [ Home | Telescope | Observing System | Alert | Faults | Commands | Quick Check-List] |