Last changed:
IS 2012-03-19 Last notification at kill is from SendToSysLog, some minor improvements.
IS 2019-07-03 Using John's suggestion.
IS 2019-08-19 Additional explanation about the mirror.
GC 2023-06-01 Added part about reseting the safety system and telescope alignment.

How to Reboot the NEW TCS

FAST VERSION:

If TCS UI is updating time at upper left then type 'kill y' and wait at least one minute, then press the RED reset button.
else if TCS UI is not updating then press the RED reset button.
You have to stop and restart observing system.

STANDARD VERSION:
Please read the two sections before pressing the RESET button! In the first case a controlled lowering of the mirror is made, in the second case it will fall down as the air is pressed out of the mirror bellows.
The reboot is made by just pressing the RESET button so it can be made also by an observer after clearance from a staff member if shown during the introduction.

If the alarm buzzer (not the NOTCam buzzer) in the control room is sounding to shut it up reset the safety system by turning the two key at the switch board. If it is not possible to reset the safety system then the telescope maybe misaligned, see Recovering from a Building Crash on how to check for this and realign the telescope if necessary. Note the part in green about TCS messages will not be relevant.

... there is a 'light' TCS crash, UT is updating and the TCS is still guiding:

The ongoing exposure can be finished before TCS reboot. Note that dither steps (teloffset) wont work.

When the ongoing exposure has finished, abort any ongoing observing script with CNTR-C on the observing system.
TCS UIF: zenith and wait, pow-off and wait, kill y and wait until the message 'SendToSysLog: SysLog is no longer logging our logs.' appears on the TCS error device screen after about 30s or wait at least 1 minute.
Press the TCS Reboot button.
While the TCS is rebooting: shutdownobssys on the observing system.
Wait for TCS UI to start.
Find the accesscode with show-page 1 on TCS UI.
Restart the obssystems with new TCS accesscode.
While the obssystems are restarting:
- reset safety system with keys
- power-on y on TCS UI.
Once TCS power is on and the obssystem is running:
- setup-tel- on observing system.

... there is a 'hard' TCS crash, no update on UI and no reaction to keys, the TCS is not guiding:

The ongoing exposure has to be aborted and TCS rebooted asap.

Press the TCS Reboot button.
While the TCS is rebooting:
- Abort or readout the ongoing exposure (eg alfosc.abort or alfosc.readout).
- Then abort any ongoing observing script with CNTR-C.
- Shutdownobssys.
If the TCS is still rebooting, wait for it to start and then get the TCS new accesscode to appear with show-page 1 on TCS UI.
Restart the obssystems with new TCS accesscode.

While the obssystems are restarting:
- reset safety system with keys
- power-on y on TCS UI.
Once TCS power is on and the obssystem is running:
- setup-tel- on observing system.