Changes
Lesedi
,/* Autoguiding */
== Autoguiding ==
Ultimately the autoguider control will be integrated into the TCS, but for now it has a standalone GUIrun on 1ms1 via the Lesedi-NUC. To start 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 document. Once connected to Lesedi-NUC, if the autoguider GUI isn't already running (or is not responding), open a terminal, login to 1ms1 and check for any autoguider sofwarejobs already running:
ssh -Y observer@1ms1.suth.saao.ac.za
ps aux | grep readPLC
The result might be:
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 xyslides software was not exited properly from the EXIT button. You need to kill them using their IDs, e.g.:
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
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.
Once the rogue processes are killed and the cameras are connected, start the autoguider GUI:
cd /home/observer/xyslide_lodestar_GUI_V5
sudo ./main_prog -depth 24
== Troubleshooting ==