### OBSDATE ### 20110223 ### LOGDATE ### 110224 ### OBSERVERS ### BAW ### WEATHER ### Clear and dry. ### LOCATION ### REMOTE ### PROGRAM ### The goal was to get some red giant data ### SIDEROSTATS ### n3 s1 ### TARGETS ### Nothing. Abject failure. Eps Hyi on pavo, no fringes Bet hor on acq camera, could see by eye on pavo, wouldn't servo. Zet Pup on pavo, no fringes -10000 to 10000 Del Vel on pavo, no fringes -5000 to 5000 ### PROBLEMS ### S1 inexplicably died a couple of times near the start of the night. Generally, it manifested itself as RTP communications errors. The only way to recover was to restart S1. The problem seemed to disappear later. S1 ran away twice. First it rotated about 180 degrees in azimuth instead of only moving the requested ~3 degrees. It was possible to stop and recover it. However, it caused errors as its slew to the next target was much longer than N3, and so it "failed" to slew in the time taskmaster expected. S1 also ran away again in elevation when stowing. While the azimuth seemed to behave itself, the elevation simply keeps turning. It does not respond to a stop command, but that locks up the server and the only way to stop it is power cycle. It seems to respond properly to the elrel command, but not the stow command. Power has been left off. I was unable to find any fringes on three different stars. I searched from -10000 to 10000 on one star and -5000 to 5000 on another. Both were chosen to be bright and unresolved after my first failure (which should also have been unresolved, but low in the sky and not so bright). When I was shutting down, I started getting errors from opcon about laser instability. Perhaps, the metrology was not measuring correctly. I am skeptical of this explanation as the lasers were fine at the start.