MDM Trouble Report for 2017 Jun 16

Telescope: 2.4m
Observer(s): Ryan Chornock (Ohio University)
Instrument: OSMOS/B

Problem(s) Encountered:
The dome started acting up in the evening. After I finished one object and moved on to the next, I noticed that the dome did not make it there and I could hear the drive repeatedly pulsing. I saw that the dome was stuck near azimuth 90, while both of my targets were setting in the west, which I thought was weird (how did it end up in the east?). I know the second target was near azimuth 300.
I tried homing the dome, which didn't work, followed by manually rotating the dome to home.  I even tried cycling the power to the dome controller in the computer room. Nothing worked, and when the dome was allowed to move automatically (either auto dome or sent to home), it just wanted to continually circle.  While it was circling, the azimuth readout on the the TCS always said something like 277 (i.e., not changing as the dome moved).
I turned off automatic control and manually rotated the dome to the azimuth of my setting target to start my observation while I emailed Eric.  

Eric called and suggested power cycling the dome encoder box in the trash can at the top of the ladder in the dome.  

I did that and reset the dome azimuth to the current position from the xtcs GUI.  The dome moved correctly to my next object and I experienced no more problems with the dome for the rest of the night.

------------------------------

Submitted on 2017 Jun 17 [5:08:51]