Date: Fri, 24 Aug 2001 08:51:56 -0700
From: Russell E Owen
Subject: Re: 2.5m obslog 20010823 (MJD 52145)
>The TCC reported:
>0 0 I RotType="Obj"
>0 0 I RotPos = -0.000475, 0.000000, 4505357364.85000
>0 7 I SpiderInstAng = 19.787410, -0.004508, 4505357421.82235
>0 7 : Cmd='show object'
>0 0 F Modu="prt_ReadMatch"; Text="bad reply"; Expected="AZ  MOVE
>23.2759011 -0.0054147 29426.82235"; Received="199.69639
>8 -1.845568 29415.647674 0 0.000000"
>0 0 F Modu="prt_ReadMatch"; Text="bad reply"; Expected="ALT MOVE
>44.3344544 0.0013911 29426.82235"; Received="AZ  MOVE 2
>3.2759011 -0.0054147 29426.82235"
>0 0 F Modu="prt_ReadMatch"; Text="bad reply"; Expected="ROT MOVE
>199.6451872 -0.0045090 29426.82235"; Received=" "
>0 0 F Modu="axe_o_Move"; Text="command failed for AZ , ALT, ROT"
>0 0 F Modu="prt_ReadMatch"; Text="bad reply"; Expected="AZ  MOVE";
>Received="ALT MOVE 44.3344544 0.0013911 29426.82235"
>0 0 F Modu="prt_ReadMatch"; Text="bad reply"; Expected="ALT MOVE";
>Received=" "
>0 0 F Modu="prt_ReadMatch"; Text="bad reply"; Expected="ROT MOVE";
>Received="ROT MOVE 199.6451872 -0.0045090 29426.82235
>"
Thanks for the excellent extract. It looks like the TCC and MCP got
out of synch, which usually means a timeout. I looked at the last few
nights and saw several timeouts 8/23 and two 8/24. This is MCP bug
2172. Unfortunately, it seems to have gotten worse lately.
-- Russell