Date: Tue, 16 Oct 2001 10:24:30 -0700
From: Russell E Owen
Subject: Re: 2.5m obslog 20011015 (MJD 52198) (MCP->TCC log for timeout)
>...The third exposure was interrupted by an ''axis halted'' problem (all 3 axes) which
>occurred at Oct 16 00:34:39 MDT.  We believe this problem occurred because of
>the delay in communication between the tcc and the mcp (i.e., the tcc did not
>receive the echo of the command it sent to the mcp fast enough)....
Here is the log of data coming from the MCP to the TCC. Note the 5 second delay between the echo of the AZ STATUS command and the status data being returned. (The time tags are unix seconds; rather than convert to UT, I found the correct entry by looking for the bad command echo in the TCC log and searching for that data in the MCP->TCC log).
1003214046.60 ROT MOVE 146.7073485 -0.0041179 23687.20868
1003214046.61  OK
1003214048.87 AZ  STATUS
1003214054.17 -40.648057 -2.213956 23680.864170 0 0.000000 OK
1003214054.22 AZ  MOVE -40.7088085 -0.0053989 23692.20868
1003214054.22  OK
1003214054.28 ALT MOVE 49.6307188 -0.0022875 23692.20868
1003214054.29  OK
1003214054.36 ROT MOVE 146.6867656 -0.0041152 23692.20868
1003214054.37  OK
1003214054.38 ALT STATUS
1003214054.51 49.643981 -0.935754 23686.369068 0 0.000000 OK
1003214054.52 AZ  MOVE
1003214054.74  OK
1003214054.75 ALT MOVE
1003214054.75  OK
1003214054.83 AZ  INIT
1003214056.40  OK
1003214056.41 ALT INIT
-- Russell