It may be necessary to log on the POINTING micro for checks in case of anomalous behaviour.
The normal state can be check by typing procs -e to check the running processes. It should say:
ant51_s: procs -e Id PId Grp.Usr Prior MemSiz Sig S CPU Time Age Module & I/O 2 0 0.0 128 4.75k 0 w 0.00 159:19 sysgo <>>>term 3 0 0.0 128 2.00k 0 s 37:20.78 159:19 ifman 4 0 0.0 128 20.25k 0 s 2:32.27 159:19 routed <>>>nil 5 0 0.0 128 2.00k 0 a 2:17.03 159:19 sockman 6 2 0.0 128 6.75k 0 w 0.00 159:19 shell <>>>term 7 6 0.0 128 6.75k 0 w 0.13 159:19 shell <dd >>>term 8 0 0.0 128 62.75k 0 e 29.00 159:19 nfsc <>>>term 9 7 0.0 128 12.00k 0 e 0.01 159:19 ftpd <>>>nil 10 7 0.0 128 12.00k 0 e 0.44 159:19 telnetd <>>>nil 11 7 0.0 128 15.50k 0 s 0.03 159:19 tsmon <>>>term 12 13 2.2 128 6.75k 0 e 0.16 75:15 shell <>>>pks00 13 0 0.0 128 22.00k 0 e 0.25 75:15 telnetdc <pks00 14 0 0.0 128 11.25k 0 e 1.53 159:19 rmshd <dd >pipe >>nil 15 0 0.0 128 9.50k 0 e 10:37:06.41 159:19 ev_it1s <dd >>>nil 16 0 0.0 128 11.25k 0 e 26.77 159:19 ev_itsync <dd >>>term 17 0 0.0 128 11.25k 0 e 0.02 159:19 ev_itincr <dd >>>term 18 0 0.0 128 11.25k 0 e 1:27:55.70 159:19 tcpip <dd >>>nil 19 0 0.0 128 11.25k 0 s 1:25:13.52 159:19 subxmit <>>>nil 20 21 0.0 128 6.75k 0 w 0.18 0:00 shell <>>>pks01 21 0 0.0 128 22.00k 0 a 0.18 0:00 telnetdc <pks01 22 20 0.0 128 18.25k 0 * 0.36 0:00 procs <>>>pks01
Programs ev_it1s, ev_itsync, ev_itincr (the time keepers), tcpip (which handles communications with BURE1), subxmit (which communicates with the RECEIVER micro program subrecv to control the subreflector), and rmshd (which support the rmsh commands from BURE1) should all be active.
Program user can display all the status bits of the antenna. Program UT displays the running UT and LST times. Program set_time can be used to re-synchronize the micro and reset the UT time. LST will become good again only after a command has been send by BURE1. Program incr can be used to re-initialize the encoders/subreflector. Program dmp dumps the antenna common.
Synchronisation problems may require to have a look at the ``history'' of the synchro errors. They are logged in files named sync.ant11, sync.ant21, etc.... These files should be small. To check their size, use:
ant51_s: chd /dd/ANTENNA ant51_s: dir -e sync.* Owner Last modified Attributes Sector Bytecount Name ------- ------------- ---------- ------ --------- ---- 0.0 96/07/16 0314 ------wr 1B51 150 sync.ant11 0.0 96/07/16 0230 ------wr 1B50 125 sync.ant31 0.0 96/07/16 0230 ------wr 1BC0 50 sync.ant41 0.0 96/07/16 0230 ------wr 1B52 50 sync.ant51The size (Bytecount) should be less than about 2000 bytes. Otherwise, too many timing errors have appeared: check the TU01 time bus. The sync.ant files contain the date and time of the error:
ant51_s: list sync.11 Tue Jul 16 09:31:42 1996 Tue Jul 16 09:31:43 1996 Tue Jul 16 10:15:27 1996 Tue Jul 16 10:15:35 1996 Tue Jul 16 10:15:41 1996 Tue Jul 16 10:15:47 1996If the file size keep increasing, the antenna are no longer properly synchronized. Use command set_time to re-synchronize them and reset the UT time. If the files get too large (Bytecount ), delete them using command
ant51_s: del sync.ant*