MDM Trouble Report for 2013 Nov 09

Telescope: 2.4m
Observer(s): Frank & Holoienen (OSU)
Instrument: OSMOS

Problem(s) Encountered:
As Eric already put in a report, and ours would replace his, I 
have attached Eric's earlier report of the same day here.

First part by Eric :

Received a call of a wire hanging loosely from the telescope.  Arrived to find that the 
rotator hand paddle cable had been torn out from the hand paddle.  Hand paddle was 
connected to the standard point as usual so it is unclear how this happened.  I have 
looked all around for schematics for the rotator hand paddle wiring.  I cannot even 
find any documentation at all on the upgraded rotator.  Even though there are only 
two button, and two subsequent relays associated to them, I am hesitant to try blindly 
reconnecting wiring without some sort of documentation.  Other interesting anomaly 
is that the paint on the center-east portion of the platform is all removed from the 
platform.  It does not appear to have been scraped necessarily, and there are no 
obvious signs of any collision with anything, but still worth mentioning since I am 
suspect of coincidences.  
I will move the telescope around before heading back down the mountain to ensure 
there is nothing odd in standard operations.  If I do not get any sort of information 
on wiring the hand paddle by the time I have tested telescope motions, I will leave 
the hand paddle and cable removed from the telescope.  The current observer does 
not need the rotator, so observations through Sunday night will not be impacted.

Second part from Stephan :

During one point in the night, when we were following PG1700+518
such that the airmass grew >2.0, suddenly the guiding stopped, 
and with scaringly fast speed the telescope ran off, and would
have brought itself into a troublesome position had we not quickly
quickly hit the red  stop  button at the black TCS switch panel.
We then could bring the telescope back to zenith after waiting for
a very brief period, and meanwhile sending the zenith coordinates 
to it -- hitting start and giving it the  go  command luckily
made it turn out of its bad position (it had not yet reached the hard limits,
but was clearly marching towards them).
The cause for this sudden loss of control is unclear -- as mentioned earlier, we
were just barely at airmass >2.0, both pointing and guiding were working extremely
well, and there had not been any indications of any trouble.

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

Submitted on 2013 Nov 10 [7:58:06]
NOTE: This trouble report replaces the previous report for 2013 Nov 09