Lesedi

Lesedi is a 1-metre, Alt-Az, f/8, Ritchey-Chretien telescope built by APM Telescopes, and installed in the dome that previously housed SAAO's 30-inch Grubb Parsons equatorial. There are two Nasmyth foci, each with an instrument rotator and identical corrector optics. This page describes the facility and its operation.

Current status and issues

Things to be aware of at the current time:

1. 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

To receive calls, the phones in the warm room and on the observing floor can be reached by the following numbers:

Extension number: 9109 (to phone from within the observatory)

To make calls if you have a problem that isn't addressed in this wiki or the fault forum (remember to dial the ** where given):

1.9m/74-inch observer: 9107

1.0m/40-inch observer: 9108

Cape Town remote observing station: 7027

Standby electronics technician: **103

Standby mechanical technician: **104

Standby IT technician: **113

A guided tour of the dome

The purpose of this section is to introduce you to the facilities and equipment you will need during your run. The tour begins at the front door of Lesedi's dome. To aid orientation, the domes of MeerLICHT, Lesedi, and the 40 inch are aligned East-West, perpendicular to the main road that passes SALT at the Northern end of the plateau and leads to the "Robotic Row" of telescopes in the South. A code (which you can obtain from the standby technicians/your support astronomer/other observers) is required to open the door.

Main lighting circuit switch

Just inside the entrance on the left-hand wall is a master switch to control all the lighting circuits in the building. Switch it on if you are working in the building, and always ensure that it is switched off when you leave, especially if people are observing remotely.

Light switches

• Foyer and stairwell light switches can be found on the right-hand wall as you enter the dome, just around the corner to the right, at the foot of the stairs (foyer light switch on the right, stair lights on the left). There is a second switch for the stairwell lights at the top of the stairs.
• Light switches on the left at the top of the stairs. The left-hand switch is for the stairwell lights; the other for the observing floor incandescents.
• The switch for observing floor fluorescent lights is located up the ladder on the observing floor, on the dome control console mounted on wall above the North end of the pier. These are also under software control.
• The slew lights on the ring beam are under software control only.

Ground floor facilities

As you enter the dome on the ground floor, you will find the following facilities:

• Fire extinguisher: mounted on the left-hand wall as you enter.
• First aid kit: on a shelf to the right as you enter the dome.
• Toilet: through the first door on the left as you enter the dome. The light switch is outside the door on the right. The right-hand switch operates an extractor fan(!).
• Kitchen:, second door on the left. It has a microwave, coffee maker, kettle, toaster, snackwich and an array of cutlery and crockery in the cupboard under the sink. There are jars of teas, coffees, hot chocolate and sugar. If these jars become empty, return them to the hostel kitchen in your night lunch bag for refilling. The kitchenware is cleaned daily by the hostel staff, except at weekends.

The control room

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

At the top of the stairs, be careful not to trip over the raised hatch in the floor (this is for lowering the primary mirror for aluminising). You will find Lesedi on a raised pier, surrounded by a metal grid floor, accessed by a ladder. The North end of the pier is nearest the stairs. Familiarise yourself with the following:

• 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 observing 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.

View of the observing floor from the Mobotix webcam, with telescope and dome both in their respective park positions.

Webcam

There are currently two webcams to use to keep an eye (and an ear) on the telescope:

• The Mobotix camera sees the full observing floor, but has no sound.
• The 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.

Observing limits

Meteorological constraints

The dome must be closed when any of the following weather limits is reached:

• Humidity: T_external - T_dew ≤ 1.5
• Wind speed: 60 km/h
• Heavy cloud

In case of strong wind and rain, please park the dome shutters facing into the wind. This can be done remotely by rotating to the required azimuth in the TCS "Advanced" tab, or on-site by putting the dome in lockout and rotating left or right using the dome control console.

Meteorological information

The following should be used for regular monitoring of external conditions while observing:

• DIMM seeing data and all the weather stations on the plateau are summarised on this page
• For assessing sky conditions, SALT and LCO operate all-sky cameras, also available on the website above.
• ATLAS has an 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

Lesedi can safely point between 30° and 89° above the horizon, at any azimuth. There are no obstructions in the dome to be aware of (assuming the observing floor has been checked for ladders etc).

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 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. Observers must not interact with the SiTech software, only with the TCS.

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.

Safety

Note that there is no hardware lockout for the telescope (except for brackets that can be fitted to hold the telescope 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.

This message on the TCS indicates that the dome is locked out and the TCS cannot be used. The dome must be checked for safety before switching off the lockout and continuing.

Local Control Unit (LCU)

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 all-sky camera. 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 observation.
• LCU connection: if the LCU drops out, then the telescope will also shutdown.

During the verification period of the LCU, there are tick boxes available to override the LCU and weather shutdowns. Please don't tick the boxes unless you experience spurious shutdowns, and report the circumstances of those shutdowns. If the suthweather.saao.ac.za page is not updating, the LCU will not be able to read the weather and will close the dome, so you will need to tick the weather override in this circumstance. Note that there is no way to override a loss of connection to the user's browser, so you always need to ensure that you reload the page if a connection warning appears on the TCS.

The LCU -- displayed on both tabs of the TCS -- monitors weather and connections, and shuts down the telescope when certain criteria are met.

In this instance, the weather page hadn't updated for more than 10 minutes, so the LCU issued a shutdown.

The Controls Tab

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.

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" 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 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 has a range of permissible numerical values is indicated in blue, e.g. azimuth, RA, airmass, etc.

Emergency Stop

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.

The Startup button

The Startup button is not a "power-up" button, as all telescope subsystems should be powered up at all times. The Startup button should be used only when you intend to open up to observe, as it opens the dome and the mirror covers.

If you don't want to run the full Startup procedure (e.g. because it's daytime and the dome should not open), but do need to interact with the telescope, individual subsystems can be commanded from the Advanced tab. Buttons on the Controls tab will work without running Startup (with the exception of Shutdown), though the telescope will need to be "unparked" from the Advanced tab before it can slew.

The Startup button runs a script that performs the following tasks in this order:

1. Take remote control of the dome
2. Switch off fluorescent lights
3. Open dome shutters
4. Open mirror covers
5. Unpark telescope so it can slew
6. Set dome to track telescope
7. Select Mookodi rotator
8. 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 in an unknown position, so to use Sibonise you will need to select the instrument after the startup procedure has completed.

The Shutdown button

Once the Startup procedure is complete, the button will read Shutdown, and should be used to close everything at the end of observing. The shutdown script essentially reverses the Startup procedure:

1. Set the dome to remote control (in most scenarios it will already be in remote, but just as a precaution)
2. Close mirror covers
3. Close dome shutters
4. Stop dome from tracking telescope
5. Park dome at az=270°
6. Park telescope at az=90°, alt=50°
7. Park rotators
8. Switch off slew lights
9. Switch off fluorescent lights (likely to be off, but as a precaution)

Control of the dome is not given up, but it can be "taken" using the lockout in the dome. It is not necessary to lockout the dome after use; staff will use this function when working in the dome.

The Advanced Tab

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.

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.

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:

Telescope panel:

• Slew the telescope to specified alt-az coordinates. The telescope will then start tracking.
• Start/stop the telescope tracking. Tracking should be on while observing, otherwise off.
• 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.
• Park (alt=50° az=90°) or unpark the telescope (also turns tracking on) to enable it to slew.

Rotator panel:

• Turn tracking on/off for the rotator on which the instrument currently 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.

Dome panel:

• Rotate the dome to a specified azimuth
• Set the dome to start or stop tracking the telescope. Tracking should be on while observing, otherwise off.
• 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 shutter movement.

Position/time/vital functions panel:

• The 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.
• Emergency Stop.
• Startup or Shutdown, whichever is the opposite of the current status.

Start-up recipes

Start-up in Sutherland

Follow this procedure to prepare the telescope and dome for observing in Sutherland:

1. Check the weather conditions here. If windspeed <60km/h and T-T_dew > 1.5 (see observing limits), continue with step 2.
2. Check the observing floor and clear any obstacles (e.g. ladders) that may obstruct the telescope.
3. Switch off the lights everywhere except in the warm room.
4. Log into ioserver1 in the warm room (address, username & password in the User Resources google doc), open a browser and navigate to the webcam and click "Live Feed". Adjust the PC's volume to ensure that you can hear the ambient noise in the dome.
5. Open a second browser window and navigate to the TCS (URL, username & password in the User Resources google doc).
6. 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.
7. Select the Instrument you require by clicking either MOOKODI or SIBONISE to the mid-left of the display. The selected instrument name will turn green.

Start-up 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.

1. If you are not working on site at SAAO in Cape Town, enable your SAAO VPN.
2. Check the weather conditions here. If windspeed <60km/h and T-T_dew > 1.5 (see observing limits), continue with step 2.
3. Open a Chrome or Chromium browser, navigate to the Unifi webcam, click "Live Feed" and check your volume level so you can hear sounds from the dome. Also open this [https:10.2.50.12 webcam] which gives a wider view of the observing floor.
4. Open another browser window and navigate to the TCS (URL, username & password in the Lesedi User Resources google doc).
5. 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.
6. Click the STARTUP button on the bottom right of the screen. 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 do anything else until it disappears, indicating that the startup procedure is complete.
7. 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 MOOKODI or SIBONISE. MOOKODI is automatically selected on startup.
8. 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.

Instrument start-up

Follow the instructions on the Mookodi wiki.

Sky flat recipe

If the sky is clear during morning/evening twilight, you will be able to take sky flats.

1. (a) If you're starting with the facility closed:

• Follow the start-up procedure.
• Follow the appropriate instrument setup procedure.

This will result in a stationary telescope pointing out of the open shutters with open mirror covers.

Or,

1. (b) If the telescope is already up and running, dome and mirror covers open: On the TCS Advanced tab:

• On the central Dome panel, make sure Tracking is switched ON,
• On the left-hand Telescope panel, click Park Telescope.

If the dome stops moving before it reaches the telescope park azimuth in the East, on the left-hand-side of Advanced tab, click telescope Tracking ON, wait for the dome to catch up, then turn telescope tracking off again. This might be necessary because the dome won't track a stationary telescope.

Then:

2. On the instrument PC, select the required filter. If you need flats in a variety of filters, be sure to cycle through them in the correct order (e.g. UBVRI during evening twilight; IRVBU in the morning). This also applies if you need a range of prebin settings (i.e. start with low binning in the evening; high to low binning in the morning).

Observing recipes

Acquiring a target

1. Follow the facility start-up procedure.

2. Check that the selected target is within the pointing limits. If you're not sure, or want to find out the exact altaz of your target, 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 enter the RA, Dec (you can use spaces for delimiters, i.e. hh mm ss (though colons will work too) - don't include any decimals) and Equinox into the boxes on the upper left panel 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 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 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.

Autoguiding

As of February 2021, there is a web browser interface to the backend autoguider control GUI, so users no longer need to access the backend (unless you have problems). Note that the original autoguider software does need to be running on 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.32:5001

The autoguider control interface looks like this:

The web browser interface for Lesedi's autoguider (click to enlarge).

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 ioserver1. If it looks ok, continue reading this section, otherwise - and if you run into trouble with any of the steps below - skip to the next section.

To acquire a guide star, do the following:

In the "X-Y Slides Control" section at the bottom left:

1. Check that "Error = 0". If "Error = 1" click "RESET".
2. Click "INITIALISE" to initialise the XY slides. Confirmation of a successful initialisation is indicated with "Initialised = 1".
3. From the dropdown menu under "GOTO GS", Select Slide 0 if using Mookodi, or Slide 1 for Sibonise (each Nasmyth port has its own autoguider). Make sure the camera is not exposing when switching slides.
4. Enter the RA and Dec of your target on the two lines below "Fetch DSS image". Use space delimiters, not colons.
5. 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.
6. 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 Mookodi field (central) with the Lodestar camera pickoff arm.
7. Click "GOTO GS" to the left of the finderchart. You will see the XY slide coordinates updating and the status "Moving = 1".
8. In the upper-left "Exposure Control" section, enter an exposure time in milliseconds (e.g. 2000) and click "Start Continuous".
9. The Lodestar image will continuously update. Your guide star should be visible - click on it, then click "Search guide star" in the "Guiding Control" section, and watch for the message box below it to be populated with numbers and a time stamp, beginning with e.g. "zmax = 12345". The zmax value is counts on the star, so make sure it isn't saturated (<65536), else reduce the exposure time.
10. Click "Guide". If successful, the guide button will turn green, and the star will continuously be pulled back towards the red cross that appears 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 "Start Continuous") and click "Guide" if the star is sill near the red cross. 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 at the end of the night:

1. Click "GUIDE" to stop guiding.
2. Click "Stop Continuous" to stop exposing.
3. Click "INITIALISE" to return the XY-slides to the home position.
4. 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 the browser control for autoguiding. In this case, you can interact directly with the backend software by following the instructions below.

1. Connect to ioserver1 via remote desktop, e.g. for Linux use the Remmina client, set the server to ioserver1.suth.saao.ac.za and enter the username and password from the Lesedi User Resources Google document.
2. Once connected to ioserver1, the autoguider software should be running. If it isn't, or if it fails to respond, follow these instructions.

To start guiding:

1. On the main autoguider GUI, if using Mookodi select Slide 0; or Slide 1 for Sibonise.
2. 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.
3. 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).
4. 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".
5. 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 Mookodi/Sibonise image, click on a star in the upper half of the image to use as a guide star.
6. 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.
7. 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.
8. 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.
9. 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:

1. Click "GUIDE" to stop guiding.
2. Click "STOP CONT." to stop exposing.
3. 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 lesedis2 (username & password in the Lesedi Resources google doc) and check for any autoguider jobs already running:

         ssh -Y observer@lesedis2.suth.saao.ac.za
         ps aux | grep readPLC

If 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 readPLC

These 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 20411

Then 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 autoguider

There is one Lodestar camera each for Mookodi 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 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 ioserver1 (or preferably a new window in the same terminal with Ctrl-Shift-T) and log in again to lesedis2:

         ssh -Y observer@lesedis2.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 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

Shutting down using the SHUTDOWN button

1. 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.
2. Turn on the slew lights on the "Advanced" tab and check on the Mobotix webcam that telescope and dome are closed and parked.
3. 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].
4. 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.
5. If any of the above is not in the correct state, you can rectify it using the relevant buttons on the Advanced tab.
6. Logout of the TCS and close the webcam browser windows.
7. Stop the autoguider exposures and initialise the XY slides.
8. Make sure the instrument (Mookodi or Sibonise) is not exposing and follow the relevant instrument shutdown procedure.

Shutting down without the SHUTDOWN button

If you woke up the telescope with the STARTUP button, it will have turned into a SHUTDOWN button (these will be changed to independent buttons in a later version of the software). If there has been a failure in the nighttime that has resulted in the web server being restarted but the telescope remaining open, the software will forget that the startup procedure was run before the crash, so there will be no shutdown button. Here you have two choices: if there is no urgent reason to close (e.g. bad weather), you can press STARTUP and wait for the commands to execute (even though everything is already running), then close up using the subsequent SHUTDOWN button. The alternative is to shutdown each subsystem individually from the Advanced tab of the TCS:

1. Ensure that you can see the feed from one of the webcams. On the TCS Advanced tab:
2. In the central Dome panel, turn the Slew lights "ON".
3. In the left-hand Telescope panel, click Mirror Covers "CLOSED" and wait for the "OPEN" button to turn grey.
4. In the central Dome panel, click "CLOSE".
5. In the left-hand Telescope panel, click "PARK TELESCOPE".
6. In the lower left Rotator panel, click Tracking "OFF".
7. In the central Dome panel, click "PARK DOME".
8. Check the webcam image for a closed dome and a parked telescope.
9. In the central Dome panel, turn the Slew lights "OFF".
10. 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].
11. If any of the above is not in the correct state, you can rectify it using the relevant buttons on the Advanced tab.
12. Logout of the TCS and close the webcam browser windows.
13. Stop the autoguider exposures and initialise the XY slides.
14. Make sure the instrument (Mookodi or Sibonise) is not exposing and follow the relevant instrument shutdown procedure.

Troubleshooting

Symptom	Cause	Solution	Who to call
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@lesedis2.suth.saao.ac.za and running the commands sudo systemctl restart lesedi and sudo systemctl restart lesedi-web, then reload the browser. If any of the SiTech software is restarted, you must also do (iii).	(ii) Hannah, IT or electronic standby.
TCS displays a warning stating that "The lockout has been engaged in the dome. No commands will be allowed until it is disabled. Try again or contact a technician for assistance...."	The dome is manually locked out.	Call a technician to check if the telescope and dome are in a safe state. If it is safe to do so, the lockout switch by the North pier needs to be turned to the OFF position.	Mechanical or electronic standby.
The dome didn't open on startup.	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.	Observer.
The autoguider Lodestar camera is not reading out.	The Lodestar camera needs rebooting.	In the 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.	Observer.
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 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.
One of the subsystems (rotator, secondary or tertiary mirror) doesn't respond.	Either (i) the motor is not in auto, or (ii) there is a comms issue with one or more subsystems, or (iii) the controller is in a fault state.	(i) On the Advanced tab of the TCS, check that there is a green "AUTO" indicator beside the relevant subsystem. If the button says "MANUAL", click it to put the motor in AUTO mode. If that doesn't help, or if it is already in AUTO, the problem is likely (ii) or (iii) and you'll need assistance.	(i) Observer. (ii) & (iii) Hannah, Electronic or IT standby.