MDM Trouble Report for 2013 Apr 25

Telescope: 2.4m
Observer(s): Jenna Nugent (University of Oklahoma)
Instrument: OSMOS, R4K

Problem(s) Encountered:
In the beginning of the night, I encountered some iraf errors:
Warning: Cannot open image
Error: pixel storage file is truncated (filename.fits)
Error: software terminate (interrupt)

I dealt with these by just trying to reload the image or logging out of 
iraf and logging back in. 

Later, during an exposure, Prospero froze. I tried crtl-c and got the error:
^C Command interrupted by a Ctrl-C
 ERROR: Could not get IC status

I typed 'startup' in the Prospero window and received status statements
and this error:
 Caliban data-transfer disks synchronized & ready...
 Error: Command returned error
ERROR: Path can't be changed during transfer.
  
 *** ERROR: Invalid IC Path: /lhome/data
 This is bad.  It usually means either
   1) The path is really not valid (mistyped?)
   2) The path is valid, but Caliban was started wrong
 If (1), use the PATH command and try again
 If (2), then
   1) Restart Caliban
   2) Try STARTUP again in Prospero
  
 STARTUP failed...
  
 Execution error in Prospero command.
 Command: startup

Then I typed 'status', which seemed to fix the problem. 
After this I heard a low grinding noise coming from the dome. It
was not very windy at this time. It would stop before I could 
discern where it was coming from. After this, 
I noticed the Maxim DL program was not showing any guide stars. I checked 
for clouds and there were none. I tried moving to several other
fields, but this did not help. 
I tried:
1. Moving probe to origin, got an error message in xmis: WARNING:
Not at Y CCW Limit
2. Dithering around to look for stars. I saw none.
3. Closing the Guide Star Selector and opening it again.
4. Pressing disconnect then connect in Maxim DL's Camera Control Setup tab.
5. Moving to slit, center and several different guide stars. Though
xmis indicated the probe was moving, Maxim DL showed the camera was
idle.
6. Attempting to move the guide probe to slit, then turning off 
track, drives and pressing stop on TCS. I moved the platform up 
so I could see the guide probe camera and it was not in its proper
location. 

All of these things affirmed to me that some sort of issue was occurring
between xmis and the guider. I tried quitting out of xmis and re-entering
it but received an error:
Network Socket Error (on hiltner)
Could not bind xmis emulator socket on port 6129 
Reason: The bound address is already in use. 
Is another instance running?

Many attempts at re-opening xmis2 (under the Telescope Control tool
bar) returned that error.

I tried opening xmis under the Data Acquisition tool bar on the 
Desktop, but got the old GUI, which I closed. As a last resort, I 
tried opening that one again and it would not open. 
At this, I gave up and commenced the shutdown procedure, during which I heard
a loud buzzing coming from near the garage door. It sounded 
similar to the generator, but was not it.

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

Submitted on 2013 Apr 26 [3:52:11]