This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
operations:documentation.ivs.mark5 [2011/06/16 10:40] Jim Lovell |
operations:documentation.ivs.mark5 [2013/02/25 01:16] (current) Jamie McCallum |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Mark5B setup ====== | ||
+ | ===== Loading and unloading modules ===== | ||
+ | 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=IPVQM0tGNgo|Removing a Mark5 module]] | ||
+ | |||
+ | ===== Setting up and configuring the Mark5 software ===== | ||
+ | |||
+ | 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> | ||
+ | |||
+ | There are two versions of the recording software currently in use. The original software is ''dimino'' which can support modules of up to 8 TB capacity (current used by Hb and Yg) and ''DIMino'' which supports 16 TB modules (in use at Ke). | ||
+ | |||
+ | Hb, Yg: | ||
+ | First check if the dimino program is running: | ||
+ | <code>ps -ef | grep dim</code> | ||
+ | If not, start it with | ||
+ | <code>dimino -m0&</code> | ||
+ | |||
+ | Ke: | ||
+ | First check if the DIMino program is running: | ||
+ | <code>ps -ef | grep DIM</code> | ||
+ | If not, start it with | ||
+ | <code>DIMino -m0&</code> | ||
+ | |||
+ | |||
+ | ===== Synchronising the Mark5 Clock ===== | ||
+ | |||
+ | 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: | ||
+ | <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: | ||
+ | <code>proc=<experiment_name>hb</code> | ||
+ | e.g. | ||
+ | <code>proc=r1473hb</code> | ||
+ | then type | ||
+ | <code>ready_disk | ||
+ | setupsx</code> | ||
+ | This will configure the Mark5 for the experiment. The alternative is to [[operations:documentation.ivs.mark5mode|set the mode manually]]. | ||
+ | |||
+ | Now check that the times are all OK: | ||
+ | |||
+ | <code>mk5=dot?</code> | ||
+ | |||
+ | 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 pcfs[hb|ke|yg], 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. | ||
+ | ===== Test Recording ===== | ||
+ | |||
+ | It's worthwhile making a test recording using the Mark5. This is done through the ''oprin'' window. | ||
+ | |||
+ | <code>disk_record=on | ||
+ | mk5=dot? (Output should appear as before, but it should say FHG_on) | ||
+ | disk_record=off</code> | ||
+ | Now check the data are OK: | ||
+ | <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: | ||
+ | <code>postob</code> | ||
+ | To clear the disk module, ONLY IF YOU'RE CERTAIN there is no data already on the disk! | ||
+ | <code> mk5=protect=off; mk5=reset=erase </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]]. |