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)
-->
== 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 ([[#Backup autoguiding procedure|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
'''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 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 [[#Backup autoguiding procedure|next section]]call a technician.
To acquire a guide star, do the following:
# 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. === 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 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 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 [[#Autoguiding|running the autoguider from Close 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 [[#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"
| 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.