Things to be aware of at the current time:
# If you encounter a loss of dome or shutter function, please report the symptoms and the time it occurred so we can check the logs for the cause. The fix will be to ask the IT technician/electronics technician/Hannah to restart the SiTech software. The shutters can be closed manually from the dome floor (with lockout switched on) if you need to close up in a hurry and it turns out to be quicker to find someone to press a button than restart the software.# The alt-az slew command has a liiittle bug and can't be used from the browser TCS just yet (the RA-Dec slew command is fine, so this doesn't affect observations).
== Contact numbers ==
Extension number: 9109 (to phone from within the observatory)
<!--To phone the dome from outside: 023 100 0 0230 (+27 23 100 0 0230 from outside South Africa)
-->
The control room, or "warm room", is the door on the right-hand side, opposite the kitchen. It contains an air-conditioned server room and has the following resources at your disposal:
* 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.'''
* Several network cables and power sockets for use with laptops.
* Lights on a dimmer switch (push and hold to adjust the brightness) and a desk lamp.
* An air conditioner to heat or cool the room.
* A stereo compatible with iPods and iPhones, and plays CDs, MP3s from DVDs and USB devices, and has a radio.
* A phone (you'll need a PIN from IT to dial out, but not for internal or standby numbers).
=== The Observing Floor ===
* '''Dome control console''' at the North end of the pier.
* '''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 Telescope ===
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. Mookodi is mounted on the right-hand port, and Sibonise is being commissioned on the left. 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.
The telescope is parked facing East, the dome to the West. There shouldn't be any need for manual interaction with the telescope during the night, but you should ensure that the observing floor is clear of ladders and other obstacles before moving the telescope, and that the mirror covers are closed before opening the dome.
* The [http://10.2.50.12 Mobotix] camera sees the full observing floor, but has no sound.
* 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.'''
Both webcams are mounted on the dome, which can be rotated to view specific areas of the observing floor.
* DIMM seeing data and all the weather stations on the plateau are summarised on [http://suthweather.saao.ac.za this page]
* For assessing sky conditions, SALT and LCO operate '''all-sky cameras''', also available on the website above.
* ATLAS has an [https://fallingstar.com/weather/ excellent all-sky camera], which is much more effective than the others during twilight. (Scroll right on their page to the section labelled "STH".)
== Telescope pointing limits ==
== 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.
<br clear=all>
[[File:LesediTCStwoTabOverview_20220215.png|thumb|1800px850px|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.]]
<br clear=all>
There is a local control unit (LCU) that has the ability to shutdown the facility under certain circumstances:
* '''Weather''': the telescope will shutdown if meteorological limits are reached. Note that the LCU currently ignores the cloud monitor, which doesn't always give an accurate indication of cloud cover, so it is especially important to monitor for cloud yourself using the [https://fallingstar.com/weather/ all-sky cameracameras]. You won't be able to startup the telescope again until the weather is good again. * '''TCS connection''': the LCU will close up the telescope if the connection to the user's TCS browser is lost for more than 10 minutes. Therefore '''it is essential to reload the browser if you see a message informing you that the connection has been lost, else the telescope will shutdown in the middle of your observationits own accord''', potentially ruining an observation.
* '''LCU connection''': if the LCU drops out, then the telescope will also shutdown.
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.
<br clear=all>
[[File:LesediTCScontrolsTabAnnotated_20220216v4.png|thumb|1000px850px|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.]]
<br clear=all>
*'''Green''': a subsystem or state is either selected (e.g. in the screenshot above, the telescope the 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 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.
*'''Blue''': a parameter which that has a range of permissible numerical values is indicated in blue, e.g. azimuth, RA, airmass, etc.
==== Emergency Stop ====
# Switch off the slew lights
You can watch the startup procedure from the webcam by 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 of the Controls tab 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 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 Shutdown button ====
The Advanced tab is made up of four panels, one for telescope-related functions, most notably telescope park/unpark and mirror cover control; one for the selected instrument's rotator; one for the dome, including lights; and the panel containing position and time information and vital buttons, replicated from the Controls tab.
<br clear=all>
[[File:LesediTCSadvancedTab_20220215.png|thumb|1000px850px|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>
'''Telescope''' panel:
* 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.
* Open/close the mirror covers. Covers should be open when observing, otherwise closed.
* 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 (also turns tracking on) to enable it to slew.
'''Rotator''' panel:
* Switch the "Lights" on/off. This refers to the fluorescent lights mounted high in the dome.
* Switch on/off the slew lights. This refers to the dimmer lights mounted on the ring beam, that can be used to check on the telescope using the webcam.
* Take TCS control of the dome (needed for all dome functions except controlling the slew lights).
* Park the dome (az=270°).
* Open/close the dome shutters.
* Stop the dome rotation or and shutter movement.
'''Position/time/vital functions''' panel:
* The [[#Local Control Unit (LCU )|LCU]] monitors observing conditions, and has tick boxes to override some forms of shutdown.
* The schematic shows the shutter status (red=closed or moving, green=open) and position, and the telescope status (slewing=red, tracking=yellow) and altaz position. No indication of telescope presence implies that it has not tracked or slewed for the past 30 minutes.
* The time is displayed in SAST, UT, LST and Julian Date.
== Start-up recipes ==
=== Start-up : observing in Sutherland ===Follow this procedure to prepare the telescope and dome facility for observing from the dome in Sutherland:
# '''Check the weather conditions [https://suthweather.saao.ac.za/ here]'''. If windspeed <60km/h and ''T''-''T''<sub>dew</sub> > 1.5 (see [[#Observing limits|observing limits]]), continue with step 2.
# Check the observing floor and '''clear any obstacles''' (e.g. ladders) that may obstruct the telescope.
# '''Switch off the [[#Light switches|lights]]''' everywhere except in the warm room.
# 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 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 MOOKODI 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 ===
On-site technical staff should have checked the facility in the afternoon, clearing any obstacles, turning off the dome lockout and any lights that are not under software control.
# 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<sub>dew</sub> > 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).
# Navigate to the "Advanced" tab of the TCS, and in the central "Dome" section, turn the Slew Lights ON and check the webcam to see if observing floor is clear (if not, call the standby technician). Switch the Slew Lights OFF.
=== Instrument start-up ===
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.
== Sky flat recipe ==
'''1.''' Follow the facility [[#Start-up recipes|start-up procedure]].
'''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.
Then/or, either:
'''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) - '''don't include any decimals''') and . Then enter the Equinox into , e.g. 2000 (don't include the boxes on the upper left panel "J") and click '''Go'''.
or:
'''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).
'''5.''' Lesedi's pointing is excellent, so your target should land very close to the centre of the image. The Due to cable wrap limits that preclude a 360° instrument rotation, the '''image orientation''' will vary between North up, East to the left, ; and North down, East to the right, due to cable wrap limits that preclude a 360° instrument rotation.
To adjust the pointing (e.g. to position a target and comparison star in the field), in the TCS Controls tab, click on the three dots beside "RA offset" (to shift the image horizontally) or "Dec offset" (for a vertical shift), enter the size of the required offset in arcsec, then click on the North, South, East or West button to move the telescope in the desired direction. When you're done, clicking the three dots again will hide the offset boxes.
'''6.''' The focus position is reported in the central status panel on the Controls tab. A reasonable starting point for Mookodi focus (imaging with clear filter) is ~2380μm; ~1700μ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 increment in microns, then click '''+''' or '''-''' to add or subtract e.g. 10μm to the focus position.
=== Creating a target catalogue ===
If you will be observing many targets during your run, or revisiting the same targets repeatedly, it would be helpful to create a target catalogue so that you don't have to type the coordinates into the TCS every time. There are two ways to do this:
# '''Add each target to the catalogue the first time you observe it.''' To do this, click "Catalogue..." enter the target, coordinates and equinox into the boxes and click "Add Target". You can then select the target from the dropdown "Targets" list above the Catalogue button.
# '''Create a catalogue file.''' Create a text file on the PC that is running the browser TCS (e.g. 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.g.
11 12 13,-14 15 16,J1112-1415,2000
22 23 24,-25 26 27,J2223-2526,2000
Save the catalogue with an easily identifiable filename, e.g. myname.txt, then on the TCS, click "Catalogue..." and "Import". Navigate to the appropriate directory and select your catalogue file.
If you are observing from the dome, using lesedi-nuc, and have created your catalogue file on your own PC, you will need to upload it using:
scp myname.txt ccd@lesedi-nuc.suth.saao.ac.za:~/Targets
then on the TCS, click "Catalogue..." then "Import" and select your file from /home/ccd/Targets.
If 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.
== Autoguiding ==
As of February 2021, there is a web browser interface to the standalone backend autoguider control GUI run on 1ms1, so users no longer need to VNC to Lesedi-NUC ([[#Backup autoguiding procedure|unless you have problems]])access the backend. Note that the original autoguider software does need to be running on Lesedi-NUC ioserver1 in order to operate the guider, but you shouldn't need to interact with it directly. The procedure for autoguiding via the browser is described below.
Open a web browser and navigate to:
10.2.2.3132:5001 '''Make sure that there is only ever one autoguider window open at a time on any PC, or you will have problems.'''
The autoguider control interface looks like this:
<br clear=all>
The autoguider camera image is displayed on the top right, with the finderchart image below. 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 Lesedi-NUCioserver1. If it looks ok, continue reading this section, otherwise - and if you run into trouble with any of the steps below - skip to the [[#Backup autoguiding procedure|next section]]call a technician.
To acquire a guide star, do the following:
# Check that "Error = 0". If "Error = 1" click "RESET".
# Click "INITIALISE" to initialise the XY slides. Confirmation of a successful initialisation is indicated with "Initialised = 1".
# From the dropdown menu under "GOTO GS", Select Slide 0 if using SHOCMookodi, or Slide 1 for Sibonise (each Nasmyth port has its own autoguider). '''Make sure the camera is not exposing when switching slides.'''
# Enter the RA and Dec of your target on the two lines below "Fetch DSS image". Use space delimiters, not colons.
# '''Slew the telescope to the target using the TCS and make sure it is tracking before pressing the "Fetch DSS image" button'''. This is important because the autoguider software needs to know the rotator angle relative to the sky in order to load the catalogue image in the correct orientation.
# A catalogue image of your field will load in the bottom right. Click on a fairly bright star in the top half of the image to use as a guide star. The closer to the top of the image the better, to avoid vignetting the SHOC Mookodi field (central) with the Lodestar camera pickoff arm.
# Click "GOTO GS" to the left of the finderchart. You will see the XY slide coordinates updating and the status "Moving = 1".
# In the upper-left "Exposure Control" section, enter an exposure time in milliseconds (e.g. 2000) and click "Start Continuous".
# Click "Stop Continuous" to stop exposing.
# Click "INITIALISE" to return the XY-slides to the home position.
# In the terminal running the web server, press CTRL-C to kill the process. === Backup autoguiding procedure === Users have occasionally encountered repeated loss of connectivity that makes it difficult to use Close the browser control for autoguiding. In this case, you can interact directly with the backend software by following the instructions below. # Connect to the NUC via remote desktop, e.g. for Linux use 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 document.# Once connected to Lesedi-NUC, the autoguider software should be running. If it isn't, or if it fails to respond, follow [[#Autoguider troubleshooting|these instructions]]. '''To start guiding''': # On the main autoguider GUI, if using SHOC select Slide 0; or Slide 1 for Sibonise.# If the status of any of the error codes (Err, XLL, XUL, YLL or YUL) is 1, click RESET, then INITIALISE. "FAKE" should always be a green "Fake is OFF" button while guiding - this is a test function for engineering purposes. # To start continuous exposures with the autoguider Lodestar camera, enter a number (~2 seconds) in the box on the right, and click CONTINUOUS. Binning should be set to 2x2. To get a workable look-up table, on the left-hand side of the main autoguider GUI, move the uppermost vertical slider ~1/6 of the way from the bottom. Leave the other two sliders in their default positions (lower vertical slider halfway up; lower horizontal slider all the way to the left; upper horizontal slider all the way to the right).# Enter the target coordinates (using spaces as delimiters, e.g. 12 34 56 -76 54 32) in the separate GS_FC window and click "Set".# Check that a finder chart loads showing your field. Guide stars are to be selected from outside the green box in the finder chart image. When North is Up in the SHOC/Sibonise image, click on a star in the upper half of the image to use as a guide star.<!--, with X<20000 and Y<15000. As Y approaches 10000 it begins to vignette the SHOC field, so try to choose a guide star at low Y.--># On the XY Slide Control section of the main GUI, click "Goto GS". This will send the XY slides to the position you clicked on the finder chart. <!--If it doesn't, read the coordinates of the guide star off the image and enter them manually; when the position is reached click "Pick guide star" and click on your chosen star in the guide camera image.--># Click the "Pick G_Star" button in the "Guiding" panel, which will turn dark blue to indicate that it's ready to receive your guide star selection. # Choose a star in the Lodestar image and click on it. The "Pick G_Star" button will turn green if it recognises the star. If the button turns grey, your selection has been unsuccessful and you will need to click the "Pick G_Star" button again and then try clicking on a different star.# Click the red GUIDE button - it should turn green to indicate that it has started guiding. '''If guiding fails''' at any point during a track (e.g. due to cloud), the button will turn red. Try increasing the exposure time (change the value and click "CONTINUOUS") and click GUIDE if the star is sill near the box. If the star has drifted, you can either offset the telescope to bring it back to its original position and then click 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 post-drift position. '''To stop the autoguider:''' # Click "GUIDE" to stop guiding.# Click "STOP CONT." to stop exposing.# Click "Initialize" to return the XY-slides to the home position. === Autoguider troubleshooting === If the autoguider GUI isn't already running (or is not responding), open a terminal, log in to 1ms1 (username & password in the Lesedi Resources google doc) and check for any autoguider jobs already running: ssh -Y observer@1ms1.suth.saao.ac.za ps aux | grep readPLCIf there are outstanding jobs, the result will be something like: root 1310 99.8 0.1 39384 13016 ? R Jun21 5284:08 python readPLCandLesediV1.py root 14103 0.0 0.1 39384 13040 pts/11 S+ 14:41 0:00 python readPLCandLesediV1.py root 20411 99.9 0.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 readPLCThese processes remain "hanging" if the software was not closed properly using the EXIT button. You need to kill them using their IDs given above, e.g. in this case: sudo kill -9 1310 14103 20411Then in the same terminal, check that the Lodestar cameras are connected: observer@sa1:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 079: ID 1278:0507 Starlight Xpress Lodestar autoguider Bus 001 Device 081: ID 1278:0507 Starlight Xpress Lodestar autoguiderThere is one Lodestar camera each for SHOC and Sibonise. If you see one Starlight Xpress in the list it might just be the one you need, so try the next steps. If you do not see any Starlight Xpress listed then the cameras are not detected on the USB ports and the icron devices probably need power cycling (call electronics standby). Once any rogue processes are killed and the cameras are connected, start the autoguider GUI: cd /home/observer/src/xyslides2ports sudo ./main_prog -depth 24 You are now ready to continue [[#Autoguiding|running the autoguider from the browser]]. However, if for some reason you need to run the guider from the backend software, you will need to start the finder chart software. Open a new terminal on lesedi-nuc (or preferably a new window in the same terminal with Ctrl-Shift-T) and log in again to 1ms1: ssh -Y observer@1ms1.suth.saao.ac.za cd /home/observer/GS_FC python genfinderLesediFeb2020.py This brings up a finder chart and a coordinates box. You're now ready to [[#Backup autoguiding procedure|guide use the backend autoguider software]]. '''If the autoguider camera image does not update''' after selecting continuous exposures, you will need to press the turquoise "Power Cycle Cameras" button on the backend GUI, then EXIT the software with the red button and restart it as above.
== Shutdown recipes ==
# Click the '''SHUTDOWN''' button on the bottom right of the TCS screen. This will close the mirror & baffle covers, close the dome shutters, and park the telescope and dome. 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 closed and parkedand 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 red and settle in the West].
# On the left-hand panel of the Controls tab, there should be a message in orange stating "Unpark telescope to slew", indicating that the telescope is parked.
# If any of the above is not in the correct state, you can rectify it using the relevant buttons on the Advanced tab.
# '''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 (Mookodi or Sibonise) is not exposing and follow the relevant instrument shutdown procedure.
# On the Controls tab of the TCS 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 red].
# If any of the above is not in the correct state, you can rectify it using the relevant buttons on the Advanced tab.
# '''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 (Mookodi or Sibonise) is not exposing and follow the relevant instrument shutdown procedure.
== Troubleshooting ==
The table below describes some problems you might encounter. Some can be tackled by the observer (see column 4). If the suggested steps to be followed by an observer fail, please call a technician.
{| class="wikitable" border="1"
| The browser TCS won't load or is unresponsive.
| (i) The page might need refreshing. (ii) One or more of the SiTech GUIs may not be running. (iii) The web server may need restarting.
| (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 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).
| (ii) Hannah, IT or electronic standby.
|-
| Mechanical or electronic standby.
|-
| 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.
| 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 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 - be sure to check the labels and get the right ones.
| (i) Hannah, IT or Electronic standby. (ii) Electronic or IT standby if on site, otherwise mechanical standby can fix this.
|-
* Log into SHOC as shoc1m at http://shoc1m.suth.saao.ac.za:5000 and switch camera on
* If in the dome, log into the NUC as ccd <br />
* Open a terminal and ssh -X observer@1ms1lesedis2.suth.saao.ac.za <br />
* rts2-mon <br />
* In CUP menu, check that manual=false. If not, manually switch off dome lockout on observing floor <br />
sudo bash<br />
cd /home/petr/rts2/src/camd<br />
sudo killall CameraServer && sudo ./rts2-camd-andor --server 1ms1lesedis2.suth.saao.ac.za <br />
* Take images with SHOC:<br />
ssh -X observer@1ms1lesedis2.suth.saao.ac.za <br />
rts2-xfocusc -d C0 -e 1<br />
(where -e is the exposure time option. Add "-X 1" to overlay grid lines).<br />
/etc/init.d/rts2 start<br />
* Take images with the Lodestar:<br />
ssh -X observer@1ms1lesedis2.suth.saao.ac.za <br />
rts2-xfocusc -d AG1CCD -e 1<br />
(where AG1CCD is on DER1 and -e is the exposure time option).<br />