User Tools

Site 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.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
operations:documentation.clock_and_delay_check [2014/09/12 00:40]
Warren Hankey [GPIB communication with counters trobleshooting]
operations:documentation.clock_and_delay_check [2019/01/15 03:52]
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 15: Line 17:
  
 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.
 +
 +
 +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 ===== =====GPIB communication with Agilent counters =====
/home/www/auscope/opswiki/data/pages/operations/documentation.clock_and_delay_check.txt · Last modified: 2019/01/15 03:52 by Katie Vandorou