User Tools
operations:documentation.ivs.mark5
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.mark5 [2011/04/03 15:47] Jim Lovell |
operations:documentation.ivs.mark5 [2011/07/13 05:47] Jim Lovell [Setting up and configuring the Mark5 software] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Mark5B setup ====== | ====== Mark5B setup ====== | ||
| - | |||
| ===== Loading and unloading modules ===== | ===== Loading and unloading modules ===== | ||
| - | If necessary, load a new module. Here are a couple of videos showing how it's done: | + | If necessary, load a new module. Here are a couple of videos showing how to install and remove modules: |
| * [[http://www.youtube.com/watch?v=bTk3_iauRUo|Mark5 module installation]] | * [[http://www.youtube.com/watch?v=bTk3_iauRUo|Mark5 module installation]] | ||
| * [[http://www.youtube.com/watch?v=IPVQM0tGNgo|Removing a Mark5 module]] | * [[http://www.youtube.com/watch?v=IPVQM0tGNgo|Removing a Mark5 module]] | ||
| + | |||
| ===== Setting up and configuring the Mark5 software ===== | ===== Setting up and configuring the Mark5 software ===== | ||
| - | Log in to mk5ya as oper:<code>ssh oper@mk5ya</code> | + | Log in to Mark5 you want to set up (either mk5hb, mk5ke or mk5yg) as oper. //Do this from within the pcfs[hb|ke|yg] VNC session so that the Mark5 software will continue to run even if the network link from Hobart to the telescope goes down.// e.g. <code>ssh oper@mk5hb</code> |
| First check if the dimino program is running: | First check if the dimino program is running: | ||
| Line 14: | Line 14: | ||
| If not, start it with | If not, start it with | ||
| <code>dimino -m0&</code> | <code>dimino -m0&</code> | ||
| - | While your at the prompt, check that the ntp time is correct by running | + | ===== Synchronising the Mark5 Clock ===== |
| - | <code>ntpq</code> | + | |
| - | 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. | + | |
| - | + | The following steps are done through the Field System. If not already started, start the Field system software on pcfs[hb|ke|yg] by starting a new terminal in the VNC session on pcfs[hb|ke|yg], and type: | |
| - | It's worthwhile making a test recording using the Mark5. 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=". | + | <code>fs</code> |
| + | An ''oprin'' window will appear and Field System commands are typed here. | ||
| First set up the Mark5 recording mode. There are two ways to do this, but the best way is to use the experiment procedure file: | First set up the Mark5 recording mode. There are two ways to do this, but the best way is to use the experiment procedure file: | ||
| Line 26: | Line 25: | ||
| <code>proc=r1473hb</code> | <code>proc=r1473hb</code> | ||
| then type | then type | ||
| - | <code>setupsx</code> | + | <code>ready_disk |
| - | This will configure the Mark5 for the experiment. The alternative is to set the mode manually. For VSI recording, 1-bit sampling and 8 MHz bandwidths ((e.g. R1 and R4 experiments): | + | setupsx</code> |
| - | <code>mk5=mode=ext:0x55555555:2</code> | + | This will configure the Mark5 for the experiment. The alternative is to [[operations:documentation.ivs.mark5mode|set the mode manually]]. |
| - | For VSI recording, 1-bit sampling and 4 MHz bandwidths (e.g. APSG, CRF, OHIG and T2 experiments) | + | |
| - | <code>mk5=mode=ext:0x55555555:4</code> | + | Now check that the times are all OK: |
| - | Now check that the times reported are correct, that FHG_off and syncerr_eq_0, and that the final number is less than ~5 ms: | ||
| <code>mk5=dot?</code> | <code>mk5=dot?</code> | ||
| - | If you see something like ''syncerr_gt_3'' then ''fmset'' may need to be run again. Also check that the maser-GPS and delay through the DBBC are the same (to within 1 microsec) with the <code>clkoff</code> and <code>maserdelay</code> commands which read the Agilent counters. | + | |
| + | look for ''syncerr_eq_0'', and that the final number is less than ~5 ms. | ||
| + | If you see something like ''syncerr_gt_3'' then ''fmset'' may need to be run to synchronise the clocks. To do this, open a terminal on pcfshb, and type | ||
| + | <code>fmset</code> | ||
| + | When the interface appears, type | ||
| + | <code>s</code> | ||
| + | then confirm with a | ||
| + | <code>y</code> | ||
| + | Following this, the clocks should all be synchronised and agree with UT. Press the [Esc] key to exit ''fmset''. | ||
| + | |||
| + | Now check that the maser-GPS and delay through the DBBC are the same (to within 1 microsec) with the <code>clkoff</code> and <code>maserdelay</code> commands which read the Agilent counters. | ||
| If one or both counters are not responding to these commands, you will see an error message like this <code>ERROR sp -4 GPIB Device time-out on response c2</code> To fix this, try re-setting the counters. In the ''oprin'' window, type <code>counter</code> and try the ''maserdelay'' and ''clkoff'' commands again. | If one or both counters are not responding to these commands, you will see an error message like this <code>ERROR sp -4 GPIB Device time-out on response c2</code> To fix this, try re-setting the counters. In the ''oprin'' window, type <code>counter</code> and try the ''maserdelay'' and ''clkoff'' commands again. | ||
| + | ===== Test Recording ===== | ||
| + | |||
| + | It's worthwhile making a test recording using the Mark5. This is done through the ''oprin'' window. | ||
| - | Now make a test recording: | ||
| <code>disk_record=on | <code>disk_record=on | ||
| - | mk5=dot? (As before, but it should say FHG_on) | + | mk5=dot? (Output should appear as before, but it should say FHG_on) |
| disk_record=off</code> | disk_record=off</code> | ||
| Now check the data are OK: | Now check the data are OK: | ||
| - | <code>mk5=scan_check?</code> | + | <code>scan_check</code> |
| Check the last numbers are the correct date at the start of the scan, duration, the data rate (should be 256 for the 8MHz mode, 128 for the 4 MHz mode) and 0 at the end for no problems. Then plot an autocorrelation from the data: | Check the last numbers are the correct date at the start of the scan, duration, the data rate (should be 256 for the 8MHz mode, 128 for the 4 MHz mode) and 0 at the end for no problems. Then plot an autocorrelation from the data: | ||
| <code>postob</code> | <code>postob</code> | ||
| + | [[operations:monitoring_autocor|Check that the spectra are OK]]. | ||
| If there are dropped or strange-looking bands, the [[hardware:dbbc.reprogram|DBBC may need reprogramming]]. | If there are dropped or strange-looking bands, the [[hardware:dbbc.reprogram|DBBC may need reprogramming]]. | ||
| - | |||
/home/www/auscope/opswiki/data/pages/operations/documentation.ivs.mark5.txt · Last modified: 2013/02/25 01:16 by Jamie McCallum
Page Tools
