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/12/17 09:55]
Warren Hankey [Maser to GPS, Formatter to GPS delays and difference]
operations:documentation.clock_and_delay_check [2019/01/15 03:52]
Katie Vandorou [Maser to GPS, Formatter to GPS delays and difference]
Line 19: Line 19:
  
  
-**Be sure that mk5=sot? 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+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 =====
 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. 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/pages/operations/documentation.clock_and_delay_check.txt · Last modified: 2019/01/15 03:52 by Katie Vandorou