Changes

1. If the web GUI is unresponsive for any reason , showing a status that you don't believe, or reporting errors, the first thing to try is to reload the browser. If that doesn't solve the problem, restart the web server using the following command from the command line on observer@1ms1.suth.saao.ac.za:

2. If there is a '''comms loss''' between a subsystem (rotator, secondary/tertiary mirror, dome) loses comms with and ServoSCommunicator, a red(pinkishish) red warning box button will appear in that subsystem's GUI complaining of Bad Comms. The first fix to try is to click on the relevant red warning boxbutton. If the problem is solved, the button should disappear. If it doesn't clear, navigate to the appropriate subsystem's tab in the ServoSCommunicator GUI and reselect the port from the dropdown list. The ports are as follows:

The pink warning box will disappear from the relevant GUI if the problem is resolved. If the problem persists, see point 3 below.

3. The most common issue is '''loss of dome comms'''. There is a watchdog on the dome that causes it to close after five minutes of bad comms - sometimes the warning message does not appear before the dome automatically closes. This problem isn't usually solved using the fix above and ServoSCommunicator will need to be restarted. + 3. If clicking on a "Bad comms" warning button does not fix the SiTech software was started using problem, the [[#Starting SiTech software|script]], you'll will need to close all the GUIs be stopped and start againrestarted. Otherwise you can leave SiTechExe running (you'd probably want to do this if the dome hasn't yet closed, and you want the telescope to keep tracking while the instrument It is exposing) and close everything else: first close ObservatoryControl, then vital that all the rotator, focuser and dome SiTech GUIs, then ServoSCommunicatorare closed, and restart that they are reopened in the correct order given in [[#Starting SiTech software|Step 5b]], so follow this procedure.