User Tools
operations:monitoring_hb
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:monitoring_hb [2014/11/10 23:18] Ross Turner [clkoff reading is drifting or far from the maser-GPS offset] |
operations:monitoring_hb [2014/12/17 09:53] (current) Warren Hankey [FS time is out by several seconds] |
||
|---|---|---|---|
| Line 46: | Line 46: | ||
| ==== FS time is out by several seconds ==== | ==== FS time is out by several seconds ==== | ||
| The origin of this problem is presently unknown but the FS time can get seriously out of step. To fix this, **while not recording** start the ''fmset'' program from an ''oper@pcfshb'' terminal and issue the "+" and "-" commands, then quit from fmset (ESC). Restart fmset and the FS time should now be correct. You may need to resync the mark5B pps after this procedure. | The origin of this problem is presently unknown but the FS time can get seriously out of step. To fix this, **while not recording** start the ''fmset'' program from an ''oper@pcfshb'' terminal and issue the "+" and "-" commands, then quit from fmset (ESC). Restart fmset and the FS time should now be correct. You may need to resync the mark5B pps after this procedure. | ||
| + | |||
| + | Be sure to check that FHG=off. Sometimes if there is a power glitch while the Mark5 is still recording, it can get 'stuck' in record mode. This will need to be stopped with disk_record=off, then run fmset again. | ||
| ==== clkoff reading is drifting or far from the maser-GPS offset ==== | ==== clkoff reading is drifting or far from the maser-GPS offset ==== | ||
| Line 78: | Line 80: | ||
| If the delay difference is more than 20 us, or gets so large that the ''clkoff'' or ''maserdelay'' values lose precision, run ''fmset'' to get the delays back to something manageable. //Make sure you are not recording while running fmset! Issuing a ''halt'' command from e-RemoteCtrl followed by ''disk_record=off'' is usually a safe method.// | If the delay difference is more than 20 us, or gets so large that the ''clkoff'' or ''maserdelay'' values lose precision, run ''fmset'' to get the delays back to something manageable. //Make sure you are not recording while running fmset! Issuing a ''halt'' command from e-RemoteCtrl followed by ''disk_record=off'' is usually a safe method.// | ||
| + | |||
| + | The first thing to do is try the command | ||
| + | <code>counter</code> | ||
| + | in e-RemoteCtrl. Check to see if this worked by typing ''clkoff'' and ''maserdelay''. If this doesn't fix it, proceed with the steps below. | ||
| If the delay difference is drifting (usually linearly), the DBBC probably needs reconfiguring. This can be done from e-RemoteCtrl as follows (again, best to halt the schedule and make sure you're not recording): | If the delay difference is drifting (usually linearly), the DBBC probably needs reconfiguring. This can be done from e-RemoteCtrl as follows (again, best to halt the schedule and make sure you're not recording): | ||
| - | <code>dbbc=reconfig</code> | + | <code>dbbc=reconf</code> |
| Monitor how things are going in the DBBC VNC session. A reconfig takes about 2 minutes. When it's completed, synchronise the dbbc: | Monitor how things are going in the DBBC VNC session. A reconfig takes about 2 minutes. When it's completed, synchronise the dbbc: | ||
| <code>dbbc=pps_sync</code> | <code>dbbc=pps_sync</code> | ||
/home/www/auscope/opswiki/data/attic/operations/monitoring_hb.1415661480.txt.gz · Last modified: 2014/11/10 23:18 by Ross Turner
Page Tools
