User Tools
operations:documentation.clock_and_delay_check
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.clock_and_delay_check [2014/09/12 00:31] Warren Hankey |
operations:documentation.clock_and_delay_check [2019/01/15 03:52] (current) Katie Vandorou [Maser to GPS, Formatter to GPS delays and difference] |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| <code>fmset</code> | <code>fmset</code> | ||
| The Field System and Computer times should agree. Press the <esc> key to exit fmset. | The Field System and Computer times should agree. Press the <esc> key to exit fmset. | ||
| + | |||
| + | If fmset if not successful (persistent clock differences), it might be wirth to (a) reboot the Mk5, (b) check the DBBC and/or reconfigure/reboot the DBBC. | ||
| ===== Maser to GPS, Formatter to GPS delays and difference ===== | ===== Maser to GPS, Formatter to GPS delays and difference ===== | ||
| Line 16: | Line 18: | ||
| 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. | 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. | ||
| - | If the GPIB has been restarted (via the PDU internet power switch, or a power outage) a field system restart is probably required to re-establish communications with the counters connected to the GPIB. The ddif counter may be showing random large offsets, and/or changing rapidly. Restarting the field system should bring this counter back to a steady few microseconds. | + | |
| + | Be sure that mk5=dot? returns FHG_off before you run fmset. Sometimes if a power glitch occurs while the Mark5 is recording, it can get stuck. If FHG_on, end with disk_record=off and then run fmset again | ||
| + | |||
| + | During the observation, it is useful to monitor the delay difference on a plot. to do it, you can start a terminal on ops2 (or ops1hb at MtPleasant) and | ||
| + | |||
| + | **(OLD)** <code>cd /vlbobs/ivs/logs</code> Then start gnuplot: <code>gnuplot</code> You shall start and/or refresh the plot window for each station by hand each time you wish to see the plot: | ||
| + | |||
| + | <code> | ||
| + | set term 'wxt' 0 ; plot "hb_ddif.txt" | ||
| + | set term 'wxt' 1 ; plot "ke_ddif.txt" | ||
| + | set term 'wxt' 2 ; plot "yg_ddif.txt" | ||
| + | </code> | ||
| + | |||
| + | **NEW:** there is now a live update available (no need to export and re-plot the data). Fro this, open a terminal on ops8 and type | ||
| + | <code> | ||
| + | delaylive hb (ke, yg) | ||
| + | </code> | ||
| + | |||
| + | =====GPIB communication with Agilent counters ===== | ||
| + | If the GPIB has been restarted (via the PDU internet power switch, or a power outage) a field system restart is probably required to re-establish communications with the counters connected to the GPIB. Symptomatic is ''fmset'' working OK, sync_error=0, but ''counter'', ''clkoff'','' maserdelay'' commands not working; the ddiff counter showing random large offsets and/or changing rapidly. Restarting the field system should bring the ddiff counter back to a steady several microseconds and enable GPIB comms. | ||
/home/www/auscope/opswiki/data/attic/operations/documentation.clock_and_delay_check.1410481879.txt.gz · Last modified: 2014/09/12 00:31 by Warren Hankey
Page Tools
