Date: Fri, 20 Jun 2008 15:57:59 -0600
From: Dan Long
Subject: Re: 2.5m obslog 20080619 (MJD 54637)
Hi Jon and Fritz,
    I thought the 2.5m secondary output was logged in "from.secondary"
on pod, but I can't find the June 6th problem (grepping for BUSSER in
2008-06*.log).  If from.secondary is indeed from the 2.5m, it would
mean that the output from the host session was not what the galil was
sending (assuming that the tap is at the output of the galil - is
it?).
    The log from that night reports seeing the following output from a
host session.
a 0000004A 0000004A  00000100 20C00FFC  FFFFC800 20C00FFC  00000002 0003FF2A
m 20C00FFC= 32312C00 c 2700 _____ p 0004FBDA
>A=1627496.; B=?1653168.; C=14?70885.; D=-588?7.; E=-7780.; ?MG "OK"
  20C00FFC BUSSER
d 00000000 00000020  00000000 0000FFFF  0000270D 00000000  0000FFFF 00004001
a 0000004A 0000004A  00000100 20C00FFC  FFFFC800 20C00FFC  00000002 0003FF0E
m 20C00FFC= 32312C00 c 2700 _____ p 0004FBDA
>XQ #STATUS
>A=1627496.; B=?1653168.; C=14?70885.; D=-588?7.; E=-7780.; ?MG "OK"
  20C00FFC BUSSER
d 00000000 00000020  00000000 0000FFFF  0000270D 00000000  0000FFFF 00004001
a 0000004A 0000004A  00000100 20C00FFC  FFFFC800 20C00FFC  00000002 0003FEF2
m 20C00FFC= 32312C00 c 2700 _____ p 0004FBDA
>A=1627496.; B=?1653168.; C=14?70885.; D=-588?7.; E=-7780.; ?MG "OK"
  20C00FFC BUSSER
    The fact that the problem last night seems to start with issuing
an m4l (which is a sop wrapper around mirror status, show scale, show
focus, and cagets for the MiGs), and was cleared by starting a host
session, might be a hint in tracking down where this gets into the
stream.
    Is there somewhere else we could put a tap which might help track
down where this extra output is coming from?
				Cheers,
				  Dan
>Can we put a logging tap on it?
>
>--jim
>
>On Fri, 20 Jun 2008, Dan Long wrote:
>
>>>                        APACHE POINT OBSERVATORY SDSS 2.5M
>>>
>>>                                  OBSERVING LOG
>>>                              Thursday June 19, 2008
>>>
>>>                                   (MJD 54637)
>>>
>>>---=== OBSERVING TEAM ===---
>>>
>>>Dan Oravetz
>>>Audrey Simmons (support)
>>>
>>>---=== OBSERVING PLAN ===---
>>>
>>>Spectro Monthly Checkout and pre-Shake tasks
>>>
>>>---=== OBSERVING SUMMARY ===---
>>>
>>>Homed/relaxed mirrors.
>>>
>>
>>
>>
>>>When the `m4l' command was issued, it froze and did not come back with the
>>>mirror numbers. We quit out of the IOP session and tried again and still had
>>>the same freezing issue. We exited from the TCC interpreter to the $ prompt
>>>and typed `HOST TCC_SEC' to try to talk to the secondary mirror
>>>controller and
>>>the reply was a bunch of numbers (see Problems section of the log MJD 54624,
>>>June 6th, for an example of the gibberish output). `m4l' was then
>>>issued for a
>>>third time and mirror numbers were issued. Another `HOST TCC_SEC' gave the
>>>normal  "connection established" message with the : prompt.
>>>
>>
>>Hi Dan,
>>
>>   This is I think the first time the transition to gibberish was
>>seen.  I assume there was no evidence of strangeness in the homing
>>process just prior to the mirror numbers command?  Was establishing
>>a host session to the secondary all that was necessary to restore
>>proper behavior, or did you reboot the galil?
>>
>>   Since we swapped the M2 controller (including its galil) on the
>>9th, a repeat of the scrambled output seen on the 6th, indicates
>>that the problem is not in the controller but somewhere in the
>>communications downstream.  It almost looks like the AUX data
>>stream is getting mixed in with the command/status stream.
>>
>>
>>				Cheers,
>>
>>				  Dan
>
>For whatever reason, the `m4l' command produced mirror numbers after
>establishing the host session to the secondary.  We did not need to reboot
>the galil, though that would have been our next course of action.
>
>DanO
>>
>>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 4102 in the sdss-25mlog archive, URL
>>DSS         http://www.astro.princeton.edu:81/sdss-25mlog/msg.4102.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