Firstly, check the schedule summary printout and find out which is the first scan to finish after the start of the check period (check times for each antenna are given on this page). The idea is to stop the schedule while no data are being recorded. For example, if the check time is 19:00 UT, then in the schedule below, it could be halted after 19:05:45 UT but before 19:07:43 UT:
Start Start Stop Record Scan Line# Source Az El Cable Record Data Data Dur Gbyte date = 2013NOV21 DOY = 325 . . . 325-1854 140 1610-771 170 6 CCW 18:53:58 18:54:08 18:58:33 4:25 35.0 * 325-1859 159 1255-316 119 19 CCW 18:59:02 18:59:12 19:05:45 6:33 43.8 * 325-1907a 178 0131-522 218 7 CCW 19:07:43 19:07:53 19:20:57 13:04 56.7 * . . .
disk_record=offin the log to confirm that the command to stop recording has been sent, and then type:
command. Look for
FHG=off in the response. If you see
FHG=on then the Mark5 is recording and you should stop it with a
. Repeat this step if necessary.
"Halting schedule for system checks
aust_checkprofile from the GUI for the antenna. e.g. for hobart
Navigator -> hb -> aust_check
This will plot antenna coordinates, tracking errors and motor currents against time. Note this step is for the 12m antennas only.
Note: need to start MONICA from the command line
ssh ops-serv2 ./omc.sh
Now the checks can begin. Note that the procedure is different for the 12m antennas and Hobart 26m:
flagr/antenna,acquiredor watch the system monitor display). While you're waiting, Check the generator status:
You will see what the current Conditioning module settings are. Output format is:
<time>/<Module label>/<IF input number>,<Auto or Manual gain control>,<Nyquist filter number>,<Target power level>,<attenuation>,<actual power level>
Check there’s agreement with what appears in the
ifd8f definition in the procedure file. The actual power level should agree pretty well with the target level. The attenuation number can be anywhere between 0 (none) and 63 (maximum). If you see it at 0 or 63, it means the Conditioning module is having trouble getting the power to the right level. You may want to adjust the attenuators (see configuring the RF and IF signal paths) to get them back in range.
You will see what the DBBC has set the BBC freqs to (compare with the .prc file). Output looks like this:
<time>/<bbc name>/<Frequency (MHz)>/<Conditioning module in use>,<Bandwidth (MHz)>,...
the Frequency, Conditioning module label and bandwidth should agree with the listing in
and check the difference reported in the log monitor
flagr/antenna,acquiredbefore continuing to the next:
test1 test2 test3 test4 test5 test1
These commands send the antenna to the following set of (Az, El) coordinates in turn : (1, 87), (1, 6), (1, 45), (-269, 45), (269, 45), (1,87). The idea here is to exercise the antenna and log the results se we can look for any changes over the days that may indicate mechanical problems.
rxp. Should be -256, +248, +18 (x,y,z)
valarmwill turn off any remaining alarm lights on the VCs.
check=*,-vf check=*,-ifd check=*,-v1
caltsyscommand works. Caltsys should return results between 50 and 70K except possibly for RFI affected S-band channels
clkoffand that it's about 10 - 12 us