User Tools
operations:r4447_set_up_and_monitoring_instructions
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
operations:r4447_set_up_and_monitoring_instructions [2010/10/13 00:23] Jamie McCallum |
operations:r4447_set_up_and_monitoring_instructions [2011/10/26 06:37] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | <note>Hobart 12m now uses pcfshb and mk5ya rather than pcfsya and mk5ya respectively.</note> | ||
| + | |||
| **Drudg** | **Drudg** | ||
| Line 45: | Line 47: | ||
| After editing the proc file, it is necessary to set up the DBBC and Mark5B. The C:\DBBC_CONF\dbbc_config_file.txt has been edited to set the frequencies correctly for R1/R4 type experiments. For other experiments, the DBBC frequencies can be calculated either from the sky frequencies or from the original values of the VCs in the proc file. The sky frequencies are given in the skd file. To convert the VC frequency settings to DBBC frequencies you need to add 480 MHZ for the first 4, add 980.1 for dbbc05-dbbc08, add 120 for dbbc09-dbbc14 and set dbbc15 and dbbc16 to something innocuous (say, 320 MHz) as they're not being recorded. Running C:\DBBC_CONF\DBBC Control.190710.exe and answering yes to configure the system should load the frequencies correctly. One the configuration is complete, you need to set up the IF system. The commands to do this are | After editing the proc file, it is necessary to set up the DBBC and Mark5B. The C:\DBBC_CONF\dbbc_config_file.txt has been edited to set the frequencies correctly for R1/R4 type experiments. For other experiments, the DBBC frequencies can be calculated either from the sky frequencies or from the original values of the VCs in the proc file. The sky frequencies are given in the skd file. To convert the VC frequency settings to DBBC frequencies you need to add 480 MHZ for the first 4, add 980.1 for dbbc05-dbbc08, add 120 for dbbc09-dbbc14 and set dbbc15 and dbbc16 to something innocuous (say, 320 MHz) as they're not being recorded. Running C:\DBBC_CONF\DBBC Control.190710.exe and answering yes to configure the system should load the frequencies correctly. One the configuration is complete, you need to set up the IF system. The commands to do this are | ||
| - | dbbcifa=1,agc,1 | + | dbbcifa=1,agc,1\\ |
| - | dbbcifb=4,agc,4 | + | dbbcifb=4,agc,4\\ |
| - | dbbcifc=2,agc,2 | + | dbbcifc=2,agc,2\\ |
| dbbcifd=2,agc,2 | dbbcifd=2,agc,2 | ||
| Line 77: | Line 79: | ||
| //Clocks//\\ | //Clocks//\\ | ||
| - | * Run "/usr/bin/xterm -name monit2 -e /usr2/fs/bin/monit2" on pcfsya to check pcfs time.\\ | + | * Run "/usr/bin/xterm -name monit2 -e /usr2/fs/bin/monit2" on pcfsya to check pcfs time.\\ |
| - | * Check SNTP Server OK in the HMI\\ | + | * Check SNTP Server OK in the HMI\\ |
| - | * Run clkoff to check formatter-GPS time offset | + | * Run clkoff to check formatter-GPS time offset |
| //Rx/IF system// - Run systemp12 to check system temperature. The reported values should be ~25 CAL units for S-band (only one channel has the appropriate filter and will give consistent values) and 12-13 CALs for X-band. When scaled to Kelvin, expect values of ~85-90 K. | //Rx/IF system// - Run systemp12 to check system temperature. The reported values should be ~25 CAL units for S-band (only one channel has the appropriate filter and will give consistent values) and 12-13 CALs for X-band. When scaled to Kelvin, expect values of ~85-90 K. | ||
| //Mark5B//\\ | //Mark5B//\\ | ||
| - | * disk_pos should report three values - the current number of btyes recorded, bytes at start of previous scan and bytes at start of current scan. If not currently recording, the first and third values should agree.\\ | + | * disk_pos should report three values - the current number of btyes recorded, bytes at start of previous scan and bytes at start of current scan. If not currently recording, the first and third values should agree.\\ |
| - | * decoder time - Check time offset in the formatter with "mk5=dot?" and check that it reports a small offset as the final value, than syncerr_eq_0 and that FHG_on or FHG_off depending on whether it is currently recording or not.\\ | + | * decoder time - Check time offset in the formatter with "mk5=dot?" and check that it reports a small offset as the final value, than syncerr_eq_0 and that FHG_on or FHG_off depending on whether it is currently recording or not.\\ |
| - | * Check mode with "mk5=mode?". The result should be "/mk5/!mode? 0 : ext : 0x55555555 : 2 : 2 ;" | + | * Check mode with "mk5=mode?". The result should be "/mk5/!mode? 0 : ext : 0x55555555 : 2 : 2 ;" |
| Line 99: | Line 101: | ||
| **Common problems** | **Common problems** | ||
| - | * //clkoff reading is drifting or far from the maser-GPS offset// - This usually is caused by the DBBC. First, go around the back of rack 14 and move the cable from the DOTMON output of the Mark5B to the "1 PPS Mon" output of the DBBC (left hand side, sixth SMA from the top). If the same offset is seen on the counter, then the problem in in the DBBC. A temporary fix can be achieved with ''pps_sync'' in DBBC Control but this did not reliably fix the problem on 13/10/10. Instead, try reconfiguring the DBBC with ''reconf'' - this will take ~two minutes in total and you will need to re-issue the ''dbbcifa=...'' commands, and resynch the mark5B with ''fmset''. | + | * //clkoff reading is drifting or far from the maser-GPS offset// - This usually is caused by the DBBC. First, go around the back of rack 14 and move the cable from the DOTMON output of the Mark5B to the "1 PPS Mon" output of the DBBC (left hand side, sixth SMA from the top). If the same offset is seen on the counter, then the problem in in the DBBC. A temporary fix can be achieved with ''pps_sync'' in DBBC Control but this did not reliably fix the problem on 13/10/10. Instead, try reconfiguring the DBBC with ''reconf'' - this will take ~two minutes in total and you will need to re-issue the ''dbbcifa=...'' commands, and resynch the mark5B with ''fmset''. |
/home/www/auscope/opswiki/data/attic/operations/r4447_set_up_and_monitoring_instructions.1286929418.txt.gz · Last modified: 2011/10/26 06:37 (external edit)
Page Tools
