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 Next revision Both sides next revision | ||
|
operations:documentation.ivs [2010/12/08 02:49] Jim Lovell |
operations:documentation.ivs [2012/05/25 01:05] Jamie McCallum [Setting Up] |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| **Mark5B** | **Mark5B** | ||
| - | 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. | + | 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 |
| - | 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=". | + | ''/etc/init.d/ntp stop''\\ |
| + | ''ntpdate cnsshb''\\ | ||
| + | ''/etc/init.d/ntp stop''''\\ | ||
| + | |||
| + | 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. | ||
| + | |||
| + | 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 32: | Line 38: | ||
| //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 48: | Line 54: | ||
| 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 54: | Line 60: | ||
| **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 77: | Line 83: | ||
| //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 93: | Line 99: | ||
| 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/pages/operations/documentation.ivs.txt · Last modified: 2013/10/03 05:22 by Imogen Jones
Page Tools
