Changes
/* Troubleshooting */
1. If the '''web GUI is unresponsive''', showing a status that you don't believe, or reporting errors, the first thing to try is to reload the browser. If that doesn't solve the problem, restart the web server and backend using the following commands in a terminal:
ssh observer@1ms1lesedis2.suth.saao.ac.za
sudo systemctl restart lesedi
sudo systemctl restart lesedi-web
5. '''Focus is unresponsive'''. This is typically a comms loss to the SiTech focuser GUI and doesn't respond to the instructions in point 2. Follow the full instructions on [[#Starting SiTech software| starting SiTech software]] to restart.
6. '''No rotator comms'''. First try shutting down and restarting all SiTech. If that doesn't work, log into 1ms1 lesedis2 and do the following: ssh observer@1ms1lesedis2.suth.saao.ac.za
ls -l /dev/ttyU*
Look for the USB port associated with ttyUSBRot2 - in this case it is ttyUSB1. Check the serial number of the device on port ttyUSB1:
observer@sa1lesedis2:~$ udevadm info -a -n /dev/ttyUSB1 | grep '{serial}'
ATTRS{serial}=="A603G14W"
ATTRS{serial}=="0000:00:14.0"
7. '''The telescope won't slew'''. First check that the telescope is unparked and that the target is within the visibility window. If those things are fine, the telescope may have triggered the hardware azimuth limit switch. This sometimes happens if the telescope is at azimuth ~165. Go to the SiTechExe GUI (the long, thin one) and at the top of the Scope tab, check if any of the arrows are red or orange. If they are, click the opposite arrow a few times to move the telescope out of the limit. If the motors are in "blinky", you may need to click the button at the bottom to switch the motors to automatic.
8. '''Telescope won't slew: motors are in "blinky" mode and won't switch to auto.''' There is likely an error on the alt and/or az controller board which will need to be reset. Find the SiTechExe GUI (the long, thin one) and try pressing the button at the very bottom to switch the motors to Auto. If it does nothing, select the "Features" tab on the same GUI. Press the "Controller Stuff" button, which will open the "Controller Information Window". There are two columns in this GUI, one for alt, one for az. There is a text box about two-thirds of the way down each column, which will either say "No Errors", or list some errors. If there is an error in the box, click the "Reset Errors" button directly underneath that text box. '''Be very careful not to click any other button.''' If that has fixed the problem, the motors will now be in Auto mode - the button in the top left corner will say "To Manual (Blinky)", and the long, thin SiTechExe button will say "Motors Automatic" at the bottom. Close the Controller Information Window and resume operations. This almost always solves the problem, but if it persists, go to 8a).
8a) If point 8 didn't get the telescope motors back to Auto mode, close all SiTech software, power cycle the raspberry Pi in the altaz controller box under the North pier, then restart SiTech. If the motors aren't in Auto and can't be switched to Auto on startup, check for errors as per point 8 above. Still got trouble? Go to 8b.
8b) If 8 & 8a) don't solve the problem, close all SiTech software and reset the SiTech altaz controller under the North pier, then restart the SiTech software. If the motors aren't in Auto and can't be switched to Auto on startup, check for errors as per point 8 above.
