Date: Mon, 16 May 2005 09:16:04 -0700 From: Russell E Owen Subject: Re: 2.5m obslog 20050513 (MJD 53504) At 11:48 AM +0000 2005-05-14, Jurek Krzesinski wrote: >Problems: >--------- >We managed to confuse mechanicals on sp1, while changing exposure time: >instead increasing it to 1500s, we shortened it to 150s (typo). Solving >that problem took 40 minutes of science time. > > >... >---------------------------------------------- >Issuing goStare science with 1500 exposure >2005-05-14 10:08:22Z: There is an aborted exposure on sp1. >sp1 cameraNag {} t-g-sdss-2.apo.nmsu.edu 2200 >sp2 cameraNag {} t-g-sdss-2.apo.nmsu.edu 2200 >Flushing charge for 15 sec >mcpPut: SYSTEM.STATUS >2005-05-14 10:09:06Z: Original command was !e1500! >2005-05-14 10:09:06Z: expected reply was !e1500 >OK >! >Mechanicals did not respond correctly; response was e1500 >failed: { already exposing } > >goStare was not successful, trying again >Mechanicals did not respond correctly; response was e1500 >failed: { already exposing } >------------------------------------------------- > >Also we couldnd't drop instruments. Hmmm - maybe sos was confused? We did exit >from the sop window and tried goStare on the coopilot computer. No, the error >message was the same as above. We issued andother mechSend s and this time >noticed that the shuter open and closed sensors were both off on the sp1: > >sp1> mechSend s >spMechVersion v2_5_0 >Bootup 719771169 >SpectroID 1 >SlitID 40 >Air On >Shutter_open_sensor Off >Shutter_closed_sensor Off >Left_open_sensor On >Left_closed_sensor Off >Right_open_sensor Off >Right_closed_sensor On > >So we rebooted mechanicals on sp1 hopping that that will clear the problem. >Unfortunately it didn't. We called Joh B. He asked us to check if the presure >is fine? it was, if there is any hissing sound (air leak)? there wasn't, >so we rebooted mechanicals again and ... this time shutter sensors were >set properly: > >sp1> mechSend s >spMechVersion v2_5_0 >Bootup 719771169 >SpectroID 1 >SlitID 40 >Air On >Shutter_open_sensor Off >Shutter_closed_sensor On >Left_open_sensor Off >Left_closed_sensor On >Right_open_sensor Off >Right_closed_sensor On > >We started sucessfuly the exposure, but the seeing was terrible >and the efficiency marginal. The exposure was read out properly, but >s/n was time due to the problem, well the last 20 minutes were in twilight with >very bad seeing conditions. Sorry for that last message; I found the details. Now...anybody know how to get to a log of what was received from (and/or sent to) specMech? It would be very interesting to see the details of the exposure abort. Clearly it got into a nasty state. It would also be worth testing some manual exposure aborts. -- Russell