Text Size:
Smaller Text Normal Text Larger Text


Follow us on Twitter

Last changed:
IS 2009-09-29 Quite revised.
IS 2012-03-19 TA's fast method at top, unnecessary details at network loss removed.

What to do if TCS crashes

There are two types of TCS crashes that might occur, one where network contact disappears (severe) and the control continues, and one where TCS goes into coma (fatal).

  • Coma:
    Results in nothing beeing updated on the User Interface terminal, no reaction to key strokes. The sequencer might complain about no response from TCS. No updates on signals to hardware, especially critical if it happens during a move at full speed. The alarm buzzer might also go on.
    What to do:(takes 10 minutes)
    Push TCS reset button.
    On obssys: shutdownobssys alfosc (or the instrument used)
    Wait for TCS to start, UT updates and is same as red display, <2 minutes
    On TCS: show 1
    Reset safety system
    On TCS: pow-on y
    On obssys: startobssys alfosc (or the instrument used)
    On obssys: tcs.setup-tel-alfosc (or the instrument used)
    Point to Your target and start observing again.

  • Network loss:
    The TCS continues to work without contact with other systems but it can be controlled from the UI. The sequencer should give error messages about lost contact to TCS.
    The network loss results in a number of messages about no connection with servers for guide stars, temperatures, weather stations and data base, seen on the error device terminal and as warning messages on the User Interface terminal.
    If this was no TCS crash but a network failure in the service building there should be no error messages about the data base server or complaints from the sequencer.
    No data is updated in the data base so file headers will not get proper contents. No reaction to teloffsets and other requests from sequencer.
    Since no data in the data base is updated, finish the ongoing exposure.
    shutdownobssys, Reboot TCS, see Reboot TCS

  • Back to top Last modified: 03-Oct-2008