Changes

== Starting SiTech & Autoguider software ==

''''N.B. These instructions have been updated in Feb 2023 - changes include the switch from 1ms1 to lesedis2 and setting up the autoguider for Mookodi.'''' The software should be opened on ioserver1, by connecting by ssh to lesedis2 and running the software using the mono libraries. If in Sutherland, you can do this from the ioserver1 PC in the warm room, else if working remotely from Cape Town, VNC to ioserver1(VNC does not currently work for all users for this PC, in which case use Teamviewer):

3. Then run this command to get the display to work:  sudo xauth merge ~/.Xauthority 4. Check for existing instances of the software already running:

45. If any existing jobs are listed -- and you are sure they are not in use by someone working elsewhere -- kill them all. Note that there will be two jobs each to kill for SiTechExe and ServoSCommunicator, so nine jobs in total if all GUIs are running:

56.(a) All the SiTech software can be opened using a startup script in the home directory, then leave the terminal running:

56.(b) or opened individually in the following order, putting each task in the background (the first two must use "sudo", and don't respond well to "&"):

sudo mono SiTechExe.exe ''(always open this one first, and wait until the GUI has loaded and the message window has closed)''

sudo mono ServoSCommunicator.exe ''(always open this one second, and wait for the GUI to fully populate and values start updating)''

mono ObservatoryControlSAAO.exe & ''(always open this one lastas it has to connect to all the others)'' 7. '''Important''': every time the SiTech software is restarted, you also need to restart Lesedi's web server and backend.

6. '''Important''': every time the SiTech software is restarted, you also need to do the following:* Navigate to the Dome tab of ServoSCommunicator and tick the box called "Read PLC Comms" (this logs dome comms to help us track down an ongoing & evasive bug).* In a new terminal, restart Lesedi's web server and backend:

exit ''(to leave the ssh session)'' exit ''(to close the terminal)''

kill -9 xxxxx ''(where xxxxx is the process ID reported from the ps aux task - kill all such processes)''

78. If you ever need to restart either ServoSCommunicator or SiTechExe, you will first need to close all the other subsystem GUIs, and reopen them in the order above(or just run the start-up script).

89. If working in the dome, bundle all the GUIs onto the left-hand monitor (it makes it easier to find them if someone needs to VNC from a smaller screen) then minimise them - they won't need to be accessed during the night unless something goes wrong. If working in Cape Town, you can close the VNC session with ioserver1 by clicking the right-hand "Disconnect" button on the Remmina tool bar(or by pressing the X in the Teamviewer menu).