This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
operations:documentation.ivs.mark5_v2 [2016/08/02 11:21] Ellen Manning [Check the Mark5 system clock] |
operations:documentation.ivs.mark5_v2 [2016/08/02 11:33] (current) Ellen Manning [Check the Mark5 system clock] |
||
---|---|---|---|
Line 28: | Line 28: | ||
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. Edit: You can try checking the <code>mk5=dot?</code>, if it is not synced or showing an error gt than 3, trying syncing the <code>fmset</code> on the pcfs computer. This usually solves the problem of a large offset. (Can someone confirm this and delete the annonations-Arwin) | + | [[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 ===== | ||