MDM Trouble Report for 2012 Oct 21

Telescope: 2.4m
Observer(s): Adams (OSU)
Instrument: OSU

Problem(s) Encountered:
Near the beginning of the night Prospero stopped listing the CamFocus.  I tried restarting Prospero and reset camfocus 5800, but it didn't work.  I also tried power cycling the IE and restarting the software.  Received the following error:

pr> call ossetup
 Querying wheels
 Current SLIT position: 2 [1.4 arcsec cente]
 Current DISPERSER position: 1 [VPH grism]
 Current FILTER1 position: 6 [Open]
 Current FILTER2 position: 6 [Open]
 Resetting collimator and camera focus to nominal 15C values...
 Resetting COLFOC...
 Setting colfoc...
 Resetting CAMFOC...
 Error: Command returned error
ERROR: CAMFOC CAMFOC=TIMEOUT cannot read from 140.252.83.155:8004
 CAMFOC request aborted with errors.
 Subroutine stack Line number:
 PROSPERO                0
 ossetup                20
 Execution error in line  20
 Command: camfoc reset 5800

I repeated the IE power cycling, startup, and ossetup and it looked good for a second but then the camfocus went back to  * .  Tried camfoc reset, but it failed.
pr> camfoc reset 5800
 Resetting CAMFOC...
 Error: Command returned error
ERROR: CAMFOC CAMFOC=TIMEOUT cannot read from 140.252.83.155:8004
 CAMFOC request aborted with errors.
 Execution error in Prospero command.
 Command: camfoc reset 5800

I tried the IE power cycling a 3rd time and it seemed like things were alright, but when I started target acquisition the first sympton started again:

IC> WARNING: ERROR: No response ACQTAG=OSMOS.20121022035116
Somehow Prospero now things camfocus is 60 (instead of 5800).

Prospero commands to OSMOS started to be very, very slow.  It now takes a full minute for Prospero to respond to commands to OSMOS.  Commands to the disperser and slit wheels seem fine, but changing the ROI and starting exposures is excruciatingly slow.
The IC warning reappears every time I issue a command to OSMOS.
I turned off the software and restarted the IC computer, but the error soon reappeared and the Prospero response time remained very slow.

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

Submitted on 2012 Oct 22 [6:22:32]