This is an old revision of the document!

TMO Observation Error Log Tracking

Date	Time	Error	Reason?	Solution
June 23rd, 2023	7:40pm	Zach found the telescope trapped in its limits!	During checks before SSP, Zach found the telesope pointed west and trapped in the limits. Motors were “in blinky mode!” When ACP connects to the telescope, tracking is started. It is likely that when Zach was doing morning checks, they forgot to park it.	Zach recovered it from the limit (This is something only Jon and Zach should do! As doing it incorrectly can cause damage).
June 26th, 2023	Reported at ~6:30pm by Jon	Dome motor appeared to have stalled during a move last night, was showing as slewing (it wasn't) and when I clicked “stop motion”, ACP threw an error and crashed.	Dome moter appeared to stall at one point in the night.	From Jon, “When I restarted and parked it moved fine,”
June 26th, 2023	~9:30pm	Telescope pointed at dome	Occasionally the telescope and dome can get off centered from each other, such that the telescope is pointing at the inside of the dome, and the slit is no longer tracking the telescope. This can happen if multiple interfaces (MaximDL, ACP, etc) are used to slew the scope and dome.	Zach was able to recover by 'resetting' everything to the 'start' position. Park the scope, park the dome, etc.
July 1st, 2023	~10:00pm	Shutter Error	Occasionally the dome will lose connection to the sensors, if this happens a shutter error will prompt an Error. This will effectively stop the dome for safety	The on-duty SSP TA informed Adam of an error, who called Zach. Zach found the dome closed with “Shutter Error.” Despite the dome being closed, ACP thought it was opened. Zach queued the dome to close (ACP prompted a message asking if I really wanted to do this since there was an error being prompted.) Clicked “yes.” Once that was done and ACP realized the slit was closed. Zach parked the scope. I then opened it and then made sure it went back to it's home position.