Date: Mon, 4 Feb 2008 13:05:59 -0700 From: Dan Long Subject: Re: Delayed Slew On 54498 Hi Kaike, Since the delay appeared to be between that one sop session and the TCC and not between the TCC and mcp, I think the rebooting of the mcp and the lack of delay since is probably just coincidence. Cheers, Dan >Just for your information. We did not see the delay during last two nights. >Not sure if it contributed but we did rebooted MCP two nights ago. >-kaike > >On Feb 4, 2008, at 11:11 AM, Dan Long wrote: > >> Friday night's log mentioned a delay in slewing to the first >>field of the night. By comparing the TCC and murmur logs, it looks >>like the delay was between SOP and the TCC, as a gcam command and a >>gotoField command issued 2 and 8 minutes earlier respectively both >>show up at the TCC at the same time, 01:04:47Z. It appears that >>several commands from the sop session 14490 were queued up and not >>seen by the TCC until 01:04:47Z (other connections were able to >>issue TCC commands such as the test slew during this time). >> >> Once the TCC got the command the mcp immediately started moving >>the telescope, and the guider started taking exposures (which were >>out of sync with the slew due to the delay). Subsequent commands >>showed no delay. What follows is the sequence of events from the >>murmur log and tcc log during that time. >> >> >>23:49:44Z Mur: SOPGUI (IOP 14490) issues startDa -tcc >> >>00:57:21Z Mur: SOPGUI (IOP 14490) issues gcam 5.0 command >> There is no evidence of the TCC receiving this command >> until much later. >>01:01:28Z TCC: Test slew to 60,60,60 >>01:01:28Z Mur: mcp starts moving telescope >>01:02:08Z Mur: Last Fiducial Crossing of 60,60,60 test slew >>01:02:16Z TCC: Test slew to 60,60,60 ends >>01:03:00Z Mur: SOPGUI issues gotoField -gflat >>01:03:22Z Mur: SOP sends track command >> SOP sends commands to turn on FF lamp and close FF screens >>01:04:15Z Mur: Setting binning for guider flat >>01:04:45Z Mur: Turning off FF lamps >>01:04:47Z TCC: gcam doread 5 (normal 2x2 binning) >> apparently in response to the SOPGUI command issued at >> 00:57 nearly 8 minutes earlier >>01:04:47Z TCC: track 25.2835, -9.3913 FK5 command received >> TCC gets command nearly two minutes after SOPGUI command >> showed up in the murmur log >>01:04:47Z Mur: tLatch, drifts, MS.ON ... mcp starts slewing telescope >> mcp responds immediately to the track command once the TCC >> sees it. >>01:04:52Z TCC: gcam doread 5 /binfac = (1,1) >>01:05:50Z Mur: Last mcp activity from gotoField >>01:52:52Z TCC: Slew end from gotoField >>01:06:12Z Mur: SPOGUI reissues gotoField -gflat >>01:06:16Z TCC: track 25.2835, -9.3913 command reissued >>01:06:24Z TCC: Slew end >>01:06:31Z TCC: gcam doread 5 /binfac = (1,1) >> >> >> >> Cheers, >> >> Dan >> >> >>DSS DSS DSS DSS DSS Digital Sky Survey DSS DSS DSS DSS DSS DSS >>DSS *** The information posted to SDSS mailing lists is proprietary *** >>DSS This is message 3908 in the sdss-25mlog archive, URL >>DSS http://www.astro.princeton.edu:81/sdss-25mlog/msg.3908.html >>DSS The index is at http://www.astro.princeton.edu:81/sdss-25mlog/INDEX.html >>DSS To join/leave the list, go to >>DSS >>http://www.astro.princeton.edu:81/cgi-bin/mailinglists.pl/show_subscription?list=sdss-25mlog >>DSS To post a message, mail it to sdss-25mlog@astro.princeton.edu >>DSS >>DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS