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 [2013/05/30 04:32] Jim Lovell [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 68: | Line 70: | ||
| gnuplot | gnuplot | ||
| plot 'yg_ddif.txt' u linesp | plot 'yg_ddif.txt' u linesp | ||
| - | </code> This will plot the delay difference against day number. you can use the right mouse button in the plot window to zoom in. Every time you press "Export data" the output files are refreshed and you can replot the values in gnuplot either by typing 'replot' or by pressing the "Replot" button in the plot window. Other possible useful files to plot are ''yg_maser2gps.txt'', the difference between the maser and GPS 1PPS, and ''yg_fmout.txt'', the difference between GPS and Mark5 output 1PPS. | + | </code> This will plot the delay difference against day number. You can use the right mouse button in the plot window to zoom in. Every time you press "Export data" the output files are refreshed and you can replot the values in gnuplot either by typing 'replot' or by pressing the "Replot" button in the plot window. Other possible useful files to plot are ''yg_maser2gps.txt'', the difference between the maser and GPS 1PPS, and ''yg_fmout.txt'', the difference between GPS and Mark5 output 1PPS. |
| + | - Seperate windows [0|1|2] can be opened for each station by replacing the final command above with:<code> | ||
| + | set terminal 'wxt' 2; plot 'yg_ddif.txt' | ||
| + | </code> | ||
| === So when do I need to reconfigure the DBBC, run fmset etc? === | === So when do I need to reconfigure the DBBC, run fmset etc? === | ||
| Line 74: | Line 79: | ||
| If the delay difference is stable you don't need to do anything. | If the delay difference is stable you don't need to do anything. | ||
| - | 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!// | + | 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 drifting (usually linearly), the DBBC probably needs reconfiguring. | + | |
| + | 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): | ||
| + | <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: | ||
| + | <code>dbbc=pps_sync</code> | ||
| + | Then in a terminal window on pcfs[hb|ke|yg], run fmset to get the clocks lined up. | ||
| + | Now resume observations with a ''cont'' or ''schedule='' command. | ||
| - | This usually is caused by the DBBC. First, go around the back of rack 14 and move the cable from the DOTMON output of the Mark5B to the "1 PPS Mon" output of the DBBC (left hand side, sixth SMA from the top). If the same offset is seen on the counter, then the problem in in the DBBC. A temporary fix can be achieved with ''pps_sync'' in DBBC Control but this did not reliably fix the problem on 13/10/10. Instead, try reconfiguring the DBBC with ''reconf'' - this will take ~two minutes in total and you will need to re-issue the ''dbbcifa=...'' commands, and resynch the mark5B with ''fmset''. | ||
| ==== PCFS log window reports problem with ReadPower.sh ==== | ==== PCFS log window reports problem with ReadPower.sh ==== | ||
/home/www/auscope/opswiki/data/attic/operations/monitoring_hb.1369888330.txt.gz · Last modified: 2013/05/30 04:32 by Jim Lovell
Page Tools
