This is an old revision of the document!

Observational Run Logs for TMO

Feb

Date	Observer	Notes	Other
2-01-2024	Zach	Clouds
2-02-2024	Zach	Clouds
2-03-2024	Zach	Clouds
2-04-2024	Zach	Clouds
2-05-2024	Zach	Clouds
2-06-2024	Zach	Clouds	Wind Advisory, by the time the wind slowed down, it was rather cloudy
2-07-2024	Zach	Clouds and Chance of rain, wind advisory	Opened up at 5:30pm - Dispatcher probably ran for a few minutes at most before I decided that the chance of rain (40% when I made the decision) wasn't worth the risk. Physically went up to TMO to do basic checks. I will note, it appears that the wind is blowing the sensor around. Will have to monitor it to make sure it doesn't get pushed up against the building.
2-08-2024	Zach	clouds
2-09-2024	Zach	Clouds
2-10-2024	Zach	Clouds / rain / snow
2-11-2024	Zach	Clouds
2-12-2024	Zach	Clear - Opened	Queue'd dispatcher to run for tonight around 5pm. Opened fine, when I left it at 8/9pm it was doing fine. At 4am I found it dome closed with “HARDWARE / Driver error due to “bad dome motor”. I was able to use ASCOM device hub to reconnect it and move it. Reopened around 4am - note, the cloud sensor has been detecting “cloudy” all night despite it being clear! Which means Zach prob needs to clean the snesor off with cleaning solution. According to TMO61 Scheduler Report for 20240212 it ran for 471 mins.
2-13-2024	Zach	Clear - Opened (appeared to have a couple more problems than usual.	Started dispacter in the afternoon. Found scheduler error “Scheduler operator intervention due to ACP becoming compromised around 7pm. IF ACP is still running but frozen or unresponsive. Check your ACP-connected devices and weather input now. If ACP is gone, something killed it. Scheduler depends on ACP. Try to determine why it was killed.” Likely, it was killed due to ACP's error “Run-time error '-2147352567(80020009)': Bad rotation sensor or stalled motor” Restarted telescope and let run. Stopped monitoring around 8:30pm. Around 3am the Telescope had reached horizon limit again due to similar ACP error above. Zach Restarted it around 3:30am. At 7am when Zach got up to site, the camera was stuck on “reading out” a 10 second flat exposure. This seemed to have been caused by the fact that the camera was unplugged on the telescope! Zach put a very small amount of tape on the USB to hopefully keep it more snug… According to TMO61 Schedular report, it ran for 227 mins last night.
2-14-2024	Zach	DAY TIME LOG / NOTES	Covered up pipe leading from bathroom to outside and reinforced it. Put tape on USB extension cable to help keep it snug (but should be loose enough to not allow problems to occur). Cleaned off sensor with cleaning solution. Rebooted / updated TMO desktop.
2-14-2024	Zach	NIGHT TIME LOG / NOTES	Opened up and seemed to have no issues throughout the night. Cloud sensor kept reporting clear skies. It changed to 'cloudy' in the morning as clouds came in. TMO61 Scheduler Report for 20240214 reports that it was active for 476 mins (when I checked TMO around 3am, it was just sitting / sleeping waiting.
2-15-2024	Zach	Virtual Campus Obs night, plus looks to be potentially cloudy.	Started ACP scheduler after the campus obs night. Checked around 3am and it appeared that things were going well, however it wasn't until 5am that I realized it was stuck on “reading” an exposure. This happened before when the camera has become physically disconnected from the telescope. Sure enough, coming up to the telescope on Feb 16th it was unpluged. Unsure of how long it actually ran (Scheduler reports it ran for about 9 hours - but it only got three images…, which mean that the camera was stuck in the read position for a significant amount of time)
2-16-2024	Zach	DAY TIME MAINTENICE LOG	Updated TMO Desktop. Reconnected camera USB. Pulled cable out of metal housing and provided as much slack as possible.

Jan

Date	Observer	Notes	Other
1-17-2024	Zach	Started Dispatcher at ~6pm. Ran for ~1.5 hours. NMSU having significant networking issues. Shutdown early
1-18-2024	Zach	Started Dispatcher at ~6pm. Ran for ~6 hours. Zach found “ACP Runtime Error” around 5:30am. Observations had stopped around 12-1am
1-19-2024	Zach	Clouds
1-20-2024	Zach	Clouds
1-21-2024	Zach	Clouds
1-22-2024	Zach	Clouds
1-23-2024	Zach	Clouds
1-24-2024	Zach	Questionable	Started the C:\Documents\ACP Astronomy\Data\Code\StdDarks.vbs script at ~10am
1-25-2024	Zach	Opened up for Virtual Campus Obs. Clouds could be seen through the dome. ACP's unsafe weather script took over and shut down the dome. Did the 'backup' plan for campus obs, due to chance of rain did not leave it running.
1-26-2024	Zach	Opened up and it ran fine! Dial web cam feel off when tracked over the west.
1-27-2024	Zach	Clear, but cloud sensor saying it was very cloudy. Started around 5:30pm. Dispatcher went for an hour then stopped due to 'very cloudy' dome was open. Closed down, restarted, went till 8:30am when it did it again. Stopped the operations after that
1-28-2024	Zach	Opened up around 6:30pm, ran for about an hour. Then got too cloudy (shut down / closed dome with any issue	Suspected issue with cloud sensor - reporting very cloudy when clear
1-29-2024	Zach	Clouds
1-30-2024	Zach	Clouds
1-31-2024	Zach	Potential clouds tonight - going to use tonight to test fixes to cloud sensor	Went up to check cloud sensor, noticed a green film over it. As per the sensor's manual, I attempted to clean it. I was able to remove some of the green film. Will see how the sensor responds.