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_v2 [2012/08/15 04:32] Jim Lovell |
operations:documentation.ivs.mark5_v2 [2016/08/02 11:23] Ellen Manning [Check the Mark5 system clock] |
||
---|---|---|---|
Line 9: | Line 9: | ||
First check if the dimino program is running: | First check if the dimino program is running: | ||
- | <code>ps -ef | grep dim</code> | + | <code>ps -ef | grep -i dim</code> |
- | If it is, we want to re-start it so that output is logged to the correct place. Stop it with the command | + | If it is (you should see ''DIMino -m0'' in the output from the above), we want to re-start it so that output is logged to the correct place. Stop it with this command: |
- | <code>Enddim</code> | + | <code>EndDIM</code> |
Then start it and give the experiment code and station ID as the argument. E.g. for r1456 at Yarragadee: | Then start it and give the experiment code and station ID as the argument. E.g. for r1456 at Yarragadee: | ||
<code>cd ~ | <code>cd ~ | ||
Line 21: | Line 21: | ||
201222802:40:54 dimino Ready. End with Enddim, please | 201222802:40:54 dimino Ready. End with Enddim, please | ||
</code> | </code> | ||
- | |||
===== Check the Mark5 system clock ===== | ===== Check the Mark5 system clock ===== | ||
- | The Mark5 gets it's system time from a local GPS receiver which runs an NTP server. You can check if it is synchronised with the command | + | The Mark5 gets it's system time from a local GPS receiver which runs an NTP server. You can check if it is synchronised with the command as oper@mk5(station name) on the vnc viewer: |
<code>ntpq -np</code> | <code>ntpq -np</code> | ||
Look for an offset (reported in milli-sec) from the the first server listed of about 10 ms or less ((detail on ntpq output can be found here: | Look for an offset (reported in milli-sec) from the the first server listed of about 10 ms or less ((detail on ntpq output can be found here: | ||
- | [[http://tech.kulish.com/2007/10/30/ntp-ntpq-output-explained/|NTP output explained]])). If there is a large offset, the Mark5 system clock may need resetting. Contact the on-call person for assistance. | + | [[http://tech.kulish.com/2007/10/30/ntp-ntpq-output-explained/|NTP output explained]])). If there is a large offset, the Mark5 system clock may need resetting. Contact the on-call person for assistance. Edit: You can try checking the ''mk5=dot?'', if it is ''syncerr_gt_3'' or ''not_synced'', trying syncing the ''fmset'' on the pcfs computer. This usually solves the problem of a large offset. (Can someone confirm this and delete the annonations-Arwin) |
===== Synchronising the Mark5 Clock ===== | ===== Synchronising the Mark5 Clock ===== | ||
Line 35: | Line 34: | ||
The following steps are done through e-remote Control or the Field System. | The following steps are done through e-remote Control or the Field System. | ||
+ | ==== 1. Set the recording mode ==== | ||
First set up the Mark5 recording mode. Use the experiment procedure file: | First set up the Mark5 recording mode. Use the experiment procedure file: | ||
<code>proc=<experiment_name><station_ID></code> | <code>proc=<experiment_name><station_ID></code> | ||
Line 41: | Line 41: | ||
then type | then type | ||
<code>ready_disk</code> | <code>ready_disk</code> | ||
- | Then one of the following depending on the experiment type. | + | |
- | * For R1, R4, RD, RDV, T2, ANZ, CRDS, CRF, OHIG:<code>setupsx</code> | + | ==== 2. VSN Check ==== |
- | * For AUST, CONT:<code>setup8f</code> | + | It's important that the modules have valid VSN codes. Please follow this procedure to |
+ | [[operations.VSN_Check|check that the VSN reported in the log agrees with the physical VSN label]]. | ||
+ | |||
+ | ==== 3. Configure the Mark5 ==== | ||
+ | Then do one of the following depending on the experiment type. | ||
+ | * For AUST,R1, R4, RDV, T2, ANZ, CRDS, CRF, OHIG:<code>setupsx</code> | ||
+ | * For CONT, RD:<code>setup8f</code> | ||
This will configure the Mark5 for the experiment. | This will configure the Mark5 for the experiment. | ||
+ | ==== 4. Synch/time check ==== | ||
Now check that the times are all OK: | Now check that the times are all OK: | ||
Line 51: | Line 58: | ||
look for ''syncerr_eq_0'', and that the final number is less than ~5 ms. | 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 | + | If you see something like ''syncerr_gt_3'' or ''not_synced'' (Edited by Arwin, can someone check this and delete this message?)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> | <code>fmset</code> | ||
When the interface appears, type | When the interface appears, type | ||
Line 60: | Line 67: | ||
<code>mk5=dot?</code> | <code>mk5=dot?</code> | ||
- | |||
- | ===== Field System and station time agreement ===== | ||
- | |||
- | The fmset program can be used to confirm that the Field system time agrees with the station time. Open a terminal on pcfs[hb|ke|yg], and type | ||
- | <code>fmset</code> | ||
- | The Field System and Computer times should agree. | ||
- | |||
- | ===== Maser to GPS, Formatter to GPS delays and difference ===== | ||
- | |||
- | Now check the maser-GPS and delay through the DBBC and Mark5 (Formatter minus GPS) with the <code>maserdelay</code> and <code>clkoff</code> commands respectively which read the Agilent counters. Log these values in the checklist. | ||
- | They should bethe same to within 0.5 microsec. The Log Monitor should report the difference whuch should be less than +/- 0.5 us. | ||
- | |||
- | Issue the ''maserdelay'' and ''clkoff'' commands a few times to check that they aren't drifting. A drift in the formatter-GPS time is usually an indication of a DBBC problem, usually requiring a reconfig to fix. | ||
- | |||
- | 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 Operator Input window, type <code>counter</code> and try the ''maserdelay'' and ''clkoff'' commands again. | ||
- | |||
- | |||
- | ===== Test Recording ===== | ||
- | |||
- | Now make a test recording using the Mark5. This is done through the Operator Input 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> | ||
- | The output should appear in the pcfs[hb|ke|yg] VNC session. Good data should contain quite flat bandpasses and zero phase. See [[operations:monitoring_autocor|autocorrelation spectra plots]] for an example and what problems to look out for. If there's a problem, the DBBC may need reconfiguring. | ||
- | |||
- | 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]]. |