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 [2011/01/18 02:40] Jim Lovell |
operations:documentation.ivs [2013/10/03 05:22] (current) Imogen Jones [Setting Up] |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| **Mark5B** | **Mark5B** | ||
| - | 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", 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. | + | 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 |
| + | |||
| + | ''/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=". | 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=". | ||
| Line 24: | 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 41: | 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 |
/home/www/auscope/opswiki/data/attic/operations/documentation.ivs.1295318411.txt.gz · Last modified: 2011/10/26 06:37 (external edit)
Page Tools
