Changes
/* Autoguiding */
== Autoguiding ==
As of February 2021, there is a web browser interface to the standalone autoguider control GUI run on 1ms1, so users no longer need to VNC to Lesedi-NUC([[#Backup autoguider procedure|unless you have problems]]). Note that the original autoguider software does need to be running on Lesedi-NUC 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:
<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 web server may not be running (see instructions above)+++++++ or the autoguider control software might not be open running on Lesedi-NUC. If it looks ok, continue reading this section, otherwise skip to the [[#Backup autoguider procedure|next section]].
To acquire a guide star, do the following:
# 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 new post-drift position.
To stop the autoguider at the end of the night:
=== Backup autoguiding procedure ===
# 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]].
=== Autoguider troubleshooting ===
If the autoguider GUI isn't already running (or is not responding), open a terminal, login 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
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 xyslides 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:
Bus 001 Device 079: ID 1278:0507 Starlight Xpress Lodestar autoguider
Bus 001 Device 081: ID 1278:0507 Starlight Xpress Lodestar autoguider
If you do not see the 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:
sudo ./main_prog -depth 24
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]].
== SHOC on Lesedi vs. other SAAO telescopes ==
