'''It is vital to ensure that no parameter is changed in any of these GUIs.'''
== Starting SiTech software ==
The software should be opened on lesedi-nuc, by connecting by ssh to 1ms1 and running the software using the mono library. If working remotely from Cape Town, VNC to lesedi-nuc:
6. 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.
== Troubleshooting ==
# If a subsystem (rotator, secondary/tertiary mirror, dome) loses comms with ServoSCommunicator, a (pinkish) red warning box will appear in that subsystem's GUI complaining of Bad Comms. The first fix to try is to navigate to the appropriate subsystem's tab in the ServoSCommunicator GUI and reselect the port from the dropdown list. The ports are as follows:
. Rotators: /dev/ttyUSBRot2
. Secondary & tertiary mirrors: /dev/ttyUSBFoc3
. Dome: /dev/ttyUSBDom4
The most common issue is '''loss of dome comms'''. This does not typically respond to the fix above, and ServoSCommunicator will need to be restarted. First close ObservatoryControl, then the rotator, focuser and dome GUIs, then ServoSCommunicator, and restart in the order given in Step 5b of