User Tools

Site Tools


operations:documentation.ivs.mark5_v2

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.ivs.mark5_v2 [2013/07/24 06:51]
Jim Lovell [Synchronising the Mark5 Clock]
operations:documentation.ivs.mark5_v2 [2016/08/02 11:33] (current)
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 this command ​on mk5hb and mk5yg: +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>​ +
-and this command on mk5ke:+
 <​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:
Line 23: 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'',​ sync the ''​fmset''​ on the pcfs computer. This usually solves the problem of a large offset. More information can be found here [[http://​auscope.phys.utas.edu.au/​opswiki/​doku.php?​id=operations:​documentation.ivs#​dbbc_configuration]]. (Can someone confirm this and delete the annonations-Arwin)
 ===== Synchronising the Mark5 Clock ===== ===== Synchronising the Mark5 Clock =====
  
Line 51: Line 47:
 ==== 3. Configure the Mark5 ==== ==== 3. Configure the Mark5 ====
 Then do one of the following depending on the experiment type. Then do one of the following depending on the experiment type.
-  * For R1, R4, RD, RDV, T2, ANZ, CRDS, CRF, OHIG:<​code>​setupsx</​code>​ +  * For  AUST,R1, R4, RDV, T2, ANZ, CRDS, CRF, OHIG:<​code>​setupsx</​code>​ 
-  * For AUST, CONT:<​code>​setup8f</​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 ==== ==== 4. Synch/time check ====
  
Line 62: Line 57:
  
 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
/home/www/auscope/opswiki/data/attic/operations/documentation.ivs.mark5_v2.1374648685.txt.gz · Last modified: 2013/07/24 06:51 by Jim Lovell