Changes

<!--To phone the dome from outside: 023 100 0 0230 (+27 23 100 0 0230 from outside South Africa)

* A PC on the left-hand side of the desk ("lesedi-nuc") for running the telescope and instrument control systems. * A PC on the right ("ioserver1") that runs the backend control software. '''Observers should not interact with this PC - it should only be used to display the weather page.'''

* A phone (you'll need a PIN from IT to dial out, but not for internal or standby numbers).

* '''Dome lockout switch''' beside the dome control console at the North end of the pier. '''Note that this does not lock out the telescope hardware. It disables the dome and the browser TCS functions.''' The lockout should be switched on (a red light on the box will flash) if people are working on the domeobserving floor, otherwise left off.

The Nasmyth ports are identified as left and right, defined from the point of view of someone standing behind the parked telescope, i.e. looking at the back of the primary mirror cell. SHOC Mookodi is mounted on the right-hand port, and Sibonise will be is being commissioned on the left. Future instruments (Mookodi (a low-resolution spectrograph incorporating a high-speed imager to replace SHOC) and a A future fibre-fed echelle) will be co-mounted on an instrument selector on the right-hand port. A software-controlled, motorised tertiary mirror allows an instrument on either port to be selected in seconds.

[[File:LesediAnnotatedDomeAnnotatedDome_20220216.png|250px800px|left|thumb|Labelled layout View of the telescope and observing floor from the Mobotix webcam, with telescope and dome both parked, as seen from the Mobotix webcamin their respective park positions.]]

* The [https://unifivideo.suth.saao.ac.za:7443/cameras UniFi] camera should be used to listen out for things that go bump in the night. It sees the shutters, the top half of the telescope and half the observing floor. '''The UniFi webcam must be viewed in Chrome/Chromium (not Firefox) for the sound to work.'''

If the telescope reaches an altitude limit, it will simply stop tracking and can be pointed to a new position. Note that the TCS will not warn you that the limit has been reached, but you will see the RA & Dec changing and the Alt & Az not. The azimuth rotation is limited to a range of 400° in order to avoid twisting the cables that pass through the pier. It is therefore possible to encounter an azimuth limit while tracking, but this should be rare because the limits are in the West. If a limit is reached, the telescope should automatically "unwind" by 360° in azimuth and continue tracking (if it doesn't, simply repoint the telescope). If the telescope with would land within 40° of an azimuth limit when slewed to a target, it will instead "unwind" to avoid the limit.

== Telescope Control System (TCS ) Overview ==

The user interface is a web browser that communicates with Lesedi's underlying control software. The browser-based software will be referred to as the "TCS" and the back-end software as the "SiTech software". The SiTech software consists of seven GUIs that must be running in the background for the TCS to function. Ideally, these GUIs will remain running at all times and Observers must not interact with the user will SiTech software, only interact with the TCS.

[[File:LesediTCStwoTabOverviewLesediTCStwoTabOverview_20220215.png|thumb|1200px850px|frame|left|The TCS user interface runs in a web browser. The functionality for routine observing is accessed from the Controls tab(left), while a second tab provides access to more Advanced functions(right). Warnings requiring action pop up in orange, and messages appear in white bubbles that can be cleared by clicking the "x". The emergency stop button, startup/shutdown button, LCU, timing info and dome schematic are always visible on both tabs.]]

Note that there is no hardware lockout for the telescope (except for brackets that can be fitted to hold the telescope vertical vertically for e.g. primary mirror removal). All the subsystems' motors are brushless DC motors and remain powered up all the time; powering down the motors would leave the telescope and subsystems free to move under gravity or external forces (e.g. leaning on it). There is a '''dome lockout''', which is a physical switch in the dome that prevents the shutters and dome from moving. As a safety feature, '''the TCS disables all actions when the dome lockout is on''' and displays the warning shown in the image below. Before the telescope can be used from the TCS, you must ensure that it is safe to turn off the lockout, then do so using the switch at the North end of the pier in the dome. If observing remotely, you will need to call a technician to do this for you.

Below is a screenshot of the main "Controls" tab of the TCS, where everything required for routine observing is located. There is one other tab, for more rarely used "Advanced" functions. The Controls tab is split into four main panels: command of the telescope and instrument selection on the left; the status of each subsystem in the middle; time and positional information and the LCU on the upper right; and important buttons that need to be easily accessible on the bottom right.

[[File:LesediTCScontrolsTabAnnotatedLesediTCScontrolsTabAnnotated_20220216v4.png|thumb|600px850px|frame|left|The main Controls tab of the TCS indicates the status of all subsystems; displays the time, telescope and dome position; gives access to a target catalogue; and allows the user to slew and offset the telescope, adjust the focus focus and select the required instrument.]]

Clicking on the three vertical dots beside a subsystem displays a drop down list of further subsystem status info, as can be seen below "Dome" and "Rotator 1" in the central panel of the screenshot above. The meaning behind the colour coding of subsystem status is as follows:

*'''Green''': a subsystem or state is either selected (e.g. in the screenshot above, the telescope is tracking at the sidereal rate, and the SHOC Mookodi instrument is selected), or is in the correct state for observing (e.g. mirror covers open, dome shutters open, telescope tracking, dome tracking, rotator 1 (SHOC) tracking).*'''Orange''': a subsystem is in an inappropriate state for observing. If the mirror covers or dome shutters are closed, their indicators would turn orange; likewise if the lights are switched on , their indicators would be orange. In the screenshot above, Rotator 2's indicator is orange - this is acceptable because SHOC (selected in green on the left) is mounted on Rotator 1, so only Rotator 1 needs to track with the telescope. *'''Blue''': a parameter that has a range of permissible numerical value but no right or wrong state values is indicated in blue, e.g. azimuth or , RA, airmass, etc.

It is important to note the '''Emergency Stop''' button on the lower right of the TCS display. It is always visible on both tabs, and will stop the motion of the dome, shutters, telescope, rotators and secondary mirror. It will not stop the autoguider XY-slides, the mirror covers or the tertiary mirror. The Emergency Stop button should be clicked if anything that is moving is going to cause a hazard. Once clicked, the Emergency Stop button will be toggled to read '''Reset''', and you must ensure that it is safe to reset all the subsystems before pressing this button to continue. Call a technician if necessary.

# Select SHOC Mookodi rotator

You can watch the startup procedure from the webcamby turning on the slew lights in the Advanced tab. While the procedure is running, the Startup button displays a revolving circle , and the indicators on the status panel on of the Controls tab is are updated with the appropriate colour as each subsystem is activated. Don't try to perform any other operation until the procedure is complete, when the text on the Startup button will be replaced with "Shutdown". The SHOC Mookodi rotator is automatically selected on startup to ensure that observations are not made with the tertiary mirror isn't in an unknown position, so to use Sibonise you will need to select the instrument after the startup procedure has completed.  

The Advanced tab is made up of four panels, one for telescope-related functions including mirrors , most notably telescope park/unpark and coversmirror cover control; one for the selected instrument's rotator in current use; one for the dome, including lights; and the panel containing positional position and timing time information and vital buttons, replicated on from the Controls tab.<br clear=all>[[File:LesediTCSadvancedTab_20220215.png|thumb|850px|frame|left|The Advanced tab of the TCS facilitates lesser-used functions, such as standalone opening/closing the mirror covers/dome shutters, switching lights on/off and switching subsystem motors to auto mode.]]<br clear=all>

Green buttons indicate a state appropriate for observing. Below is an explanation of the features of the Advanced tab, from top to bottom, left to right:

* Park (alt=50° az=90°) or unpark the telescope (also turns tracking on) to enable it to slew.* Slew the telescope to specified alt-az coordinates. The This is not currently operational due to a bug that prevents the telescope will then start trackingfrom reaching the required position.* Start/stop the telescope tracking. Tracking should be on while observing, otherwise off. If you have pointed to a target from the Controls tab, the telescope will track automatically.

* Put the altaz, secondary and tertiary mirror motors in Auto mode. Motors should always be in Auto unless there is a fault. If a motor will not stay in Auto mode, call a technician.* Park (alt=50° az=90°) or unpark the telescope to enable it to slew.

* Turn tracking on/off for the rotator on which the instrument currently in use selected is mounted. Tracking is automatically disabled for the other rotator. Tracking "on" does not necessarily mean that the rotator is moving, but that it will move if the telescope is tracking. Rotator status can be found on the Controls tab, where the angle will be updating if the rotator is tracking.* Put the motor in Auto for the rotator currently in use. The motor should always be in Auto unless there is a fault. If it won't switch it to Auto, call a technician.

* Stop the dome rotation or and shutter movement.

'''Position/timingtime/vital functions''' panel:* The [[#Local Control Unit (LCU)|LCU]] monitors observing conditions, and has tick boxes to override some forms of shutdown.

=== Start-up : observing in Sutherland ===Follow this procedure to prepare the telescope and dome facility for observing from the dome in Sutherland:

# Log into lesedi-nuc in the warm room (address, username & password in the User Resources google doc), open a browser and navigate to the [https://unifivideo.suth.saao.ac.za:7443/cameras webcam] and click "Live Feed". Adjust the PC's volume to ensure that you can hear the ambient noise in the dome.# Open a second browser window and navigate to the TCS (URL, username & password in the User Resources google doc).# Click the '''STARTUP''' button on the TCS. This will switch on the slew lights so you can watch it open the dome, baffle and mirror covers, and set the dome to follow the telescope, then switch off the slew lights. A blue progress circle will rotate on the button while all the commands are executed - don't try to send any other TCS commands until it disappears, indicating that the startup procedure is complete.# Select The startup procedure rotates the '''Instrument''' tertiary mirror to Mookodi, so if you require by clicking either SHOC or wish to use Sibonise click SIBONISE to the mid-left of the TCS display. The selected instrument name will turn green.# On the central panel of the TCS "Controls" tab, check for green indicators showing the status of each subsystem: Mirror covers = Open; Secondary & Tertiary mirror motors = Auto; Dome: Control = TCS and Tracking = On; and the relevant rotator for your chosen instrument Tracking = On and Motors = Auto.

=== Start-up : observing remotely ===

# If you are not working on the SAAO network (i.e. not on site at SAAO in Cape Town), enable your SAAO VPN.# '''Check the weather conditions [https://suthweather.saao.ac.za/ here]'''. If windspeed <60km/h and T-T_dew > 1.5 (see [[#Observing limits|observing limits]]), continue with step 23.# Open a Chrome or Chromium browser, navigate to the [https://unifivideo.suth.saao.ac.za:7443/cameras Unifi webcam], click "Live Feed" and check your volume level so you can hear sounds from the dome. Also # In another tab, open this [httpshttp://10.2.50.12 webcam] which gives a wider view of the observing floor.# Open another browser window and navigate to the TCS (URL, username & password in the Lesedi User Resources google doc).

# Click the '''STARTUP''' button on the bottom right of the screen. This will switch on the slew lights so you can watch it open the dome, baffle and mirror covers, and set the dome to follow the telescope, then switch off the slew lights. A blue progress circle will rotate on the button while all the commands are executed - don't try to do anything else until it disappears, indicating that the startup procedure is complete.# On the TCS "Controls" tab, check that the '''Instrument''' you require is selected (highlighted in green to the mid-left of the display), and if not, click either SHOC MOOKODI or SIBONISE. SHOC MOOKODI is automatically selected on startup.

Follow the instructions on the [https://topswiki.saao.ac.za/index.php/SHOC SHOC Mookodi Mookodi wiki] and note the [[#SHOC on Lesedi vs. other SAAO telescopes|Lesedi-specific SHOC info]] further down this page.

'''2.''' Check that the selected target is within the [[#Telescope pointing limits|pointing limits]]. If you're not sure, or want to find out the exact altaz of when your targetis visible, you can enter the coordinates into the input boxes on the upper left panel of the Controls tab, then click "Visibility...". This brings up a panel that shows the altitude and azimuth of the target at that moment , and the times at which the target rises and sets at the 30° altitude limit.

'''3(a)''' In the TCS '''Controls''' tab , in the boxes on the upper left panel, enter the RA, and Dec in sexagesimal (you can use not degrees). Use spaces for delimiters, i.e. hh mm ss, (though colons will work too) and - '''don't include any decimals'''. Then enter the Equinox into , e.g. 2000 (don't include the boxes on the upper left panel "J") and click '''Go'''.

'''3(b)''' In the TCS '''Controls''' tab click on the box labelled '''Targets''', then select the desired object from the dropdown list. To populate the dropdown list, see the [[#Target Creating a target catalogue| catalogue instructions]].

The telescope will slew to the target, and its movement will be plotted in red dots on the schematic in the right-hand panel. The "Go" button will become a "STOP" button, which you can click if you need to stop the telescope. Once it reaches the target coordinates, the telescope will start to track and yellow dots will show the track progress on the visibility plot. If nothing happens, the target is probably outside the observing window - return to step 2.

'''4.''' The telescope will track the target until you click '''STOP''', or until it reaches the lower altitude limit (note that the TCS will not warn you if this happens, so keep an eye on the visibility plot). To run SHOC, follow the instructions on the [https://topswiki.saao.ac.za/index.php/SHOC SHOC wiki].

'''5.''' Lesedi's pointing is excellent, so your target should land very close to the centre of the SHOC image. The Due to cable wrap limits that preclude a 360° instrument rotation, the '''image orientation''' with no "flips" applied in the SHOC software (check the Advanced tab of the SHOC control) is usually will vary between North up, East to the left with SHOC, but will change to ; and North down, East to the right for a short time after passing through the meridian. ,

'''6.''' The focus position is reported in the central status panel on the Controls tab. A reasonable starting point for SHOC Mookodi focus (imaging with a clear filter in the beam ) is ~2000μm, or 2380μm; ~1800μm without a filter1700μm for Sibonise. Once you're close to focus, a reasonable increment for small adjustments is ~10μm. Focus the telescope using the '''Adjust Focus...''' button, which brings up a box in which you can enter the focus incrementin microns, then click '''+''' or '''-''' to add or subtract e.g. 10μm to the focus position.

== Autoguiding = Creating a target catalogue ===

Ultimately the autoguider control If you will be integrated into observing many targets during your run, or revisiting the TCSsame targets repeatedly, but for now it has would be helpful to create a standalone GUI run on 1ms1 via the Lesedi-NUC. Connect target catalogue so that you don't have to type the NUC via remote desktop, e.g. for Linux use coordinates into the Remmina client, set the server to lesedi-nuc.suth.saao.ac.za and enter the username and password from the Lesedi User Resources Google documentTCS every time. There are two ways to do this:

Once connected # '''Add each target to Lesedi-NUC, if the autoguider GUI isncatalogue the first time you observe it.'t already running (or is not responding)'' To do this, open a terminalclick "Catalogue..." enter the target, login to 1ms1 (username & password in coordinates and equinox into the google doc) boxes and check for any autoguider jobs already running:click "Add Target". You can then select the target from the dropdown "Targets" list above the Catalogue button.

ssh -Y observer@1ms1# '''Create a catalogue file.suth''' Create a text file on the PC that is running the browser TCS (e.saaog. if you are in the dome, this will be lesedi-nuc). The file should consist of one line per target, with RA, Dec, target name & equinox as comma-separated variables, e.acg.za ps aux | grep readPLC

If there are outstanding jobs 11 12 13, the result will be something like:-14 15 16,J1112-1415,2000 22 23 24,-25 26 27,J2223-2526,2000

root 1310 99Save the catalogue with an easily identifiable filename, e.8 0g.1 39384 13016 ? R Jun21 5284:08 python readPLCandLesediV1myname.py root 14103 0txt, then on the TCS, click "Catalogue.0 0.1 39384 13040 pts/11 S+ 14:41 0:00 python readPLCandLesediV1.py root 20411 99" and "Import".9 0Navigate to the appropriate directory and select your catalogue file.1 39384 13092 ? R Jun23 1187:37 python readPLCandLesediV1.py observer 25808 0.0 0.0 14224 1032 pts/12 S+ 17:49 0:00 grep --color=auto readPLC

These processes remain "hanging" if the xyslides software was not exited properly If you are observing from the EXIT button. You dome, using lesedi-nuc, and have created your catalogue file on your own PC, you will need to kill them upload it using their IDs given above, e.g. in this case:

sudo kill scp myname.txt ccd@lesedi-9 1310 14103 20411nuc.suth.saao.ac.za:~/Targets

Then in then on the same terminalTCS, check that the Lodestar cameras are connected:click "Catalogue..." then "Import" and select your file from /home/ccd/Targets.

observer@sa1:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3If you then click on the dropdown Targets list above the Catalogue button, your targets will be available for you to select, then click "Go" to point.0 root hub Bus 001 Device 079: ID 1278:0507 Starlight Xpress Lodestar autoguider Bus 001 Device 081: ID 1278:0507 Starlight Xpress Lodestar autoguider

Once any rogue processes are killed Open a web browser and the cameras are connected, start the autoguider GUInavigate to: 10.2.2.32:5001

cd /home/observer/xyslide_lodestar_GUI_V6 sudo '''Make sure that there is only ever one autoguider window open at a time on any PC, or you will have problems./main_prog -depth 24'''

To run the finder chart software, open a new terminal The autoguider control interface looks like this:<br clear=all>[[File:lesediAutoguider.png|thumb|400px|frame|left|The web browser interface for Lesedi's autoguider (or a new window in the same terminal with CTRL-SHIFT-T) and login again click to 1ms1:enlarge).]]<br clear=all>

ssh -Y observer@1ms1The autoguider camera image is displayed on the top right, with the finderchart image below.suth There will be a green "Online" indicator at the top left if all is well; if it's red ("Offline") the autoguider control software might not be running on ioserver1.saao If it looks ok, continue reading this section, otherwise call a technician.ac.za cd /home/observer/GS_FC python genfinderLesediFeb2020.py

This brings up To acquire a finder chart and a coordinates box. To start guidingguide star, do the following:

# On In the main autoguider GUI, if using SHOC select Slide 0; or Slide 1 for Sibonise."X-Y Slides Control" section at the bottom left:# Check that "Error = 0". If the status of any of the error codes (Err, XLL, XUL, YLL or YUL) is "Error = 1, " click "RESET, then INITIALISE". # Click "FAKEINITIALISE" should always be to initialise the XY slides. Confirmation of a green "Fake successful initialisation is OFFindicated with "Initialised = 1" button while guiding - this is a test function for engineering purposes. # To start continuous exposures with From the autoguider Lodestar cameradropdown menu under "GOTO GS", enter a number Select Slide 0 if using Mookodi, or Slide 1 for Sibonise (~2 secondseach Nasmyth port has its own autoguider) in . '''Make sure the box on camera is not exposing when switching slides.'''# Enter the right, RA and click CONTINUOUSDec of your target on the two lines below "Fetch DSS image". Binning should be set to 2x2Use space delimiters, not colons. To get a workable look-up table, on # '''Slew the left-hand side of telescope to the main autoguider GUI, move target using the uppermost vertical slider ~1/6 of TCS and make sure it is tracking before pressing the way from the bottom"Fetch DSS image" button'''. Leave This is important because the other two sliders in their default positions (lower vertical slider halfway up; lower horizontal slider all autoguider software needs to know the way rotator angle relative to the left; upper horizontal slider all the way sky in order to load the right).# Enter the target coordinates (using spaces as delimiters, e.g. 12 34 56 -76 54 32) catalogue image in the separate GS_FC window and click "Set"correct orientation.# Check that a finder chart loads showing A catalogue image of your field. Guide stars are to be selected from outside the green box will load in the finder chart imagebottom right. When North is Up in the SHOC/Sibonise image, click Click on a fairly bright star in the upper top half of the image to use as a guide star.<!--, with X<20000 and Y<15000. As Y approaches 10000 it begins The closer to vignette the SHOC fieldtop of the image the better, so try to choose a guide star at low Yavoid vignetting the Mookodi field (central) with the Lodestar camera pickoff arm.--># On the XY Slide Control section of the main GUI, click Click "Goto GOTO GS". This will send the XY slides to the position you clicked on left of the finder chartfinderchart. <!--If it doesn't, read You will see the XY slide coordinates of the guide star off the image updating and enter them manually; when the position is reached click status "Pick guide starMoving = 1" and click on your chosen star in the guide camera image.--># Click In the upper-left "Pick G_StarExposure Control" button section, enter an exposure time in the milliseconds (e.g. 2000) and click "GuidingStart Continuous" panel, which will turn dark blue to indicate that it's ready to receive your guide star selection. # Choose a star in the The Lodestar image and will continuously update. Your guide star should be visible - click on it. The , then click "Pick G_StarSearch guide star" button will turn green if it recognises in the star. If the button turns grey"Guiding Control" section, your selection has been unsuccessful and you will need to click watch for the message box below it to be populated with numbers and a time stamp, beginning with e.g. "Pick G_Starzmax = 12345" button again and then try clicking . The zmax value is counts on a different the star, so make sure it isn't saturated (<65536), else reduce the exposure time.# Click "Guide". If successful, the red GUIDE guide button - it should will turn green to indicate , and the star will continuously be pulled back towards the red cross that it has started guidingappears on the image.

'''If guiding fails''' at any point during a track (e.g. due to cloud), the "Guide" button will turn red. Try increasing the exposure time (change the value and click "CONTINUOUSStart Continuous") and click GUIDE "Guide" if the star is sill near the boxred cross. If the star has drifted, you can either offset the telescope to bring it back to its original position and then click GUIDE"Guide", or if it is not important to you to keep the target in the original position on the science image, you can repeat the guide star selection procedure to resume guiding in the new post-drift position.

To stop the autoguiderat the end of the night:

# Click "STOP CONT.Stop Continuous" to stop exposing.# Click "InitializeINITIALISE" to return the XY-slides to the home position.# '''If you close Close the autoguider GUI (not necessary under normal circumstances), be sure to press the EXIT button'''; do not kill the GUI with the X in the corner or you will leave problematic hanging jobs. == SHOC on Lesedi vs. other SAAO telescopes == If you notice any funny effects with the SHOC interface running in Chrome (e.g. image not displaying, red lines being deposited in the plot area by the cursor), '''run SHOC from Firefox''' and these should be resolved. SAAO has two Andor cameras, interchangeably referred to as SHOC. The one largely dedicated to Lesedi is "shocndisbelief" ("shocnawe" is usually on the 1.9- & 1.0-m). Shocndisbelief has a roving bias issue in the 1MHz mode (a differential count level occurs, the number of rows affected varying with time) so it is recommended to operate in 3MHz readout. SHOC's field of view is larger on Lesedi than on the other telescopes (5.7x5.7 arcmin²), with a platescale of 0.33"/pixel, so the appropriate binning is usually 1x1 or 2x2. On the Advanced tab of the SHOC control browser, set both "Flip X Axis" and "Flip Y Axis" to OFF to set SHOC's image display to North up and East to the left on Lesedi.  The login for SHOC on Lesedi is given in the Lesedi User Resources google doc. === Filters === At present, SHOC has one 8-position filter wheel, containing UBVRI, a clear filter to match the focus of the Bessell filters, and two empty slots. The SHOC software identifies the filter in each position. '''Filters must not be removed from the filter wheel.''' === Data === To retrieve your data from the SHOC PC during your run, use this command from the PC on which you which to view the images:  rsync -avzP shoc1m@shoc1m.suth.saao.ac.za:/data/lesedi/shd/YYYY/MMDD/SHD_YYYYMMDD.nnnn.fits . where YYYY is the year, MMDD the month and day, and nnnn the filenumberwindow.

# Ensure that you can see the feed from one of the webcams.# Click the '''SHUTDOWN''' button on the bottom right of the TCS screen. This will switch on the slew lights so you can watch close the mirror & baffle covers close, close the dome shutters close, and park the telescope and dome park, then the slew lights switch off. A blue progress circle will rotate on the button while all the commands are executed; it will disappear once the shutdown procedure is complete.# Turn on the slew lights on the "Advanced" tab and check on the Mobotix webcam that telescope and dome are parked and closed.# On the central panel of the TCS "Controls" tab, check for grey or orange indicators showing the status of each subsystem: telescope Tracking = Off (grey); Mirror covers = Closed (orange); Dome (orange) Tracking = Off (grey) and Shutters = Closed (orange) [the arc indicating the shutters on the schematic will also turn redand settle in the West].

# '''Logout''' of the TCS and close the webcam browser windowswindow.# Stop the autoguider exposures and , initialise the XY slidesand close the autoguider browser window.# Close the webcam browser windows.# Make sure the instrument (SHOC Mookodi or Sibonise) is not exposing and turn off follow the camerarelevant instrument shutdown procedure.

# '''Logout''' of the TCS and close the webcam browser windowswindow.# Stop the autoguider exposures, initialise the XY slides and close the remote session to lesedi-nucautoguider browser window.# Close the webcam browser windows.# Make sure the instrument (SHOC Mookodi or Sibonise) is not exposing and turn off follow the camerarelevant instrument shutdown procedure.

| (i) Reload the page. (ii) Check that all SiTech GUIs are running and have no comms problems; restart all GUIs if there are any issues. (iii) Restart the lesedi server and web server by logging into observer@1ms1lesedis2.suth.saao.ac.za and running the command "commands <code>sudo systemctl restart lesedi"</code> and <code>sudo systemctl restart lesedi-web</code>, then reload the browser. If any of the SiTech software is restarted, you must also do (iii).

| The telescope spontaneously shut down (mirror covers closed, dome closed, telescope parked).| The facility was shutdown by the LCU, either due to bad weather or a loss of connection to the TCS.| Check the weather: if it's bad you must leave the telescope closed. Check the TCS: if there is a message stating that the connection has been lost, reload the page. If the weather is good, press Startup and resume observing.| Observer|-| The dome didn't open on startup, or closed by itself and won't reopen.| There may be a dome comms problem.| Call a technician to remedy.| Hannah, Electronic or IT standby.|-| The telescope does not slew when I enter coordinates and press Go, but the lockout is off, the telescope is not parked and there are no error messages.| (i) Target may not be visible. (ii) Coordinate format may be wrong. (iii) If (i) and (ii) fail, there may be a problem with the telescope.| (i) With the coordinates entered into the Controls tab of the TCS, click "Visibility" then "Calculate" to check whether your target is visible. (ii) Reload the page, then enter the coordinates again with space delimiters and no decimals. (iii) SiTech status will need checking.| (i) & (ii) Observer. (iii) Hannah, IT or electronic standby.|-| There is an error message saying "No Instrument selected".| The tertiary mirror is facing neither Mookodi nor Sibonise's Nasmyth port.| Click on either "Mookodi" or "Sibonise" in the Instrument panel of the Controls tab.

| In the main [[#Backup autoguiding procedure|backend autoguider GUI]], click the turquoise "Power Cycle Cameras" button and wait 30 seconds. Then press the red "EXIT" button to exit the guider software, before restarting it from the command line.

| The the autoguider GUI crashes.| (i) One or more of the SiTech GUIs may not be running or may have comms issues. (ii) The Icron device connected to the Lodestar cameras likely needs might need rebooting.| (i) Check that all SiTech GUIs are running and have no comms problems; restart all GUIs if there are any issues. (ii) Unplug the power cable from the Lodestar Icron device mounted on the underside of the pier, then plug it in again. If the problem persists, unplug the Lodestar Icron device from 1ms1 lesedis2 downstairs in the server room. N.B. there are separate Icron devices for the Lodestar cameras and the SiTech controllers - make be sure you to check the labels and get the right ones.

| Hannah, Electronic or IT standby(i) Observer.|-| The dome didn't open on startup.| There may be a comms problem.| Call a technician to remedy.| (ii) & (iii) Hannah, Electronic or IT standby.|-| There is an error message saying "No Instrument selected".| The tertiary mirror is facing neither SHOC nor Sibonise's Nasmyth port.| Click on either "SHOC" or "Sibonise" in the Instrument panel of the Controls tab.| You can fix this!

* Open a terminal and ssh -X observer@1ms1lesedis2.suth.saao.ac.za <br />

sudo killall CameraServer && sudo ./rts2-camd-andor --server 1ms1lesedis2.suth.saao.ac.za <br />

ssh -X observer@1ms1lesedis2.suth.saao.ac.za <br />

ssh -X observer@1ms1lesedis2.suth.saao.ac.za <br />