User Tools
operations:documentation.ivs
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:documentation.ivs [2010/12/08 02:12] Jim Lovell |
operations:documentation.ivs [2013/10/03 05:22] (current) Imogen Jones [Setting Up] |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| * [[operations:documentation.ivs.SchedStart|Running the schedule]] | * [[operations:documentation.ivs.SchedStart|Running the schedule]] | ||
| + | **Mark5B** | ||
| - | **DBBC** | + | As oper@mk5ya, first check if the dimino program is running (ps -ef | grep dim). If not, start it with "dimino -m0&". While your at the prompt, check that the ntp time is correct by running "ntpq -np" (for a non-interactive session). Alternatively, run ''ntpq'' and then issue the "peers" command. The offset and delay to tac32ho should be small (less than ~5 milliseconds). If it is not, then you will need to resynch the machine to the NTP server. As root, issue the commands |
| - | 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 | + | ''/etc/init.d/ntp stop''\\ |
| + | ''ntpdate cnsshb''\\ | ||
| + | ''/etc/init.d/ntp stop'' | ||
| - | dbbcifa=1,agc,1\\ | ||
| - | dbbcifb=4,agc,4\\ | ||
| - | dbbcifc=2,agc,2\\ | ||
| - | dbbcifd=2,agc,2 | ||
| - | It appears that CoMo 3 is reporting low total power levels. It may be that there is a poor connection on one of the SMAs...The target values for the total power readings is 56000. this can be checked by the command dbbcif[abcd]. If the levels are too high or low, then adjust the attenuation on the IF box. | + | After entering these commands, check the ntp status again. Once the NTP time is ok, you will need to run "fmset" on pcfshb, set the time (with ".") and then sync the formatter ("s", followed by "y"). Exit from fmset as soon as you have finished. |
| - | **Mark5B** | + | It's worthwhile making a test recording using the mark5b. To do this you can either use tstdimino on mk5ya or the fs. The instructions below are for the fs but to use them in tstdimino, omit the leading "mk5=". |
| - | + | ||
| - | As oper@mk5hb, first check if the dimino program is running (ps -ef | grep dim). If not, start it with "dimino -m0&". While your at the prompt, check that the ntp time is correct by running "ntpq", and then issuing the "peers" command. The offset and delay to tac32ho should be small (less than ~5 milliseconds). If it is not, then the best thing to do is to run "fmset" on pcfsya, set the time (with ".") and then sync the formatter ("s", followed by "y"). Exit from fmset as soon as you have finished. | + | |
| - | + | ||
| - | It's worthwhile making a test recording using the mark5b. To do this you can either use tstdimino on mk5hb or the fs. The instructions below are for the fs but to use them in tstdimino, omit the leading "mk5=". | + | |
| mk5=mode=ext:0x55555555:2 (For VSI recording, 1-bit sampling, 8 MHz BW) | mk5=mode=ext:0x55555555:2 (For VSI recording, 1-bit sampling, 8 MHz BW) | ||
| Line 36: | Line 31: | ||
| mk5=protect=off\\ | mk5=protect=off\\ | ||
| mk5=reset=erase | mk5=reset=erase | ||
| + | |||
| + | Make sure there are no other experiments on the module or you will erase those too with this command!! | ||
| + | |||
| **Running the Schedule** | **Running the Schedule** | ||
| Line 44: | Line 42: | ||
| //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 pcfshb 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 | ||
| Line 53: | Line 51: | ||
| * 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 "; (where the last number is either 1 or 2, the number of disk modules loaded |
| Line 60: | Line 58: | ||
| End of experiment - The "source=stow" command does not currently work so please stow the dish using the HMI interface and the "Stow" button. | End of experiment - The "source=stow" command does not currently work so please stow the dish using the HMI interface and the "Stow" button. | ||
| - | To run the status monitor, enter this command at the pcfsya prompt | + | To run the status monitor, enter this command at the pcfshb prompt |
| /usr/bin/xterm -name monit2 -e /usr2/fs/bin/monit2 | /usr/bin/xterm -name monit2 -e /usr2/fs/bin/monit2 | ||
| Line 66: | Line 64: | ||
| **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''.r at the prompt, check that the ntp time is correct by running "ntpq", and then issuing the "peers" command. The offset and delay to tac32ho should be small (less than ~5 milliseconds). If it is not, then the best thing to do is to run "fmset" on pcfsya, set the time (with ".") and then sync the formatter ("s", followed by "y"). Exit from fmset as soon as you have finished. | + | * //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''.r at the prompt, check that the ntp time is correct by running "ntpq", and then issuing the "peers" command. The offset and delay to tac32ho should be small (less than ~5 milliseconds). If it is not, then the best thing to do is to run "fmset" on pcfshb, set the time (with ".") and then sync the formatter ("s", followed by "y"). Exit from fmset as soon as you have finished. |
| - | It's worthwhile making a test recording using the mark5b. To do this you can either use tstdimino on mk5hb or the fs. The instructions below are for the fs but to use them in tstdimino, omit the leading "mk5=". | + | It's worthwhile making a test recording using the mark5b. To do this you can either use tstdimino on mk5ya or the fs. The instructions below are for the fs but to use them in tstdimino, omit the leading "mk5=". |
| mk5=mode=ext:0x55555555:2 (For VSI recording, 1-bit sampling, 8 MHz BW) | mk5=mode=ext:0x55555555:2 (For VSI recording, 1-bit sampling, 8 MHz BW) | ||
| Line 89: | Line 87: | ||
| //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 pcfshb 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 | ||
| Line 105: | Line 103: | ||
| End of experiment - The "source=stow" command does not currently work so please stow the dish using the HMI interface and the "Stow" button. | End of experiment - The "source=stow" command does not currently work so please stow the dish using the HMI interface and the "Stow" button. | ||
| - | To run the status monitor, enter this command at the pcfsya prompt | + | To run the status monitor, enter this command at the pcfshb prompt |
| /usr/bin/xterm -name monit2 -e /usr2/fs/bin/monit2 | /usr/bin/xterm -name monit2 -e /usr2/fs/bin/monit2 | ||
/home/www/auscope/opswiki/data/attic/operations/documentation.ivs.1291774352.txt.gz · Last modified: 2011/10/26 06:37 (external edit)
Page Tools
