User Tools
operations:documentation:lba_starting_and_monitoring
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:documentation:lba_starting_and_monitoring [2013/03/14 04:14] Jim Lovell [Starting] |
operations:documentation:lba_starting_and_monitoring [2014/11/22 09:01] (current) Jesse Swan [Monitoring] |
||
|---|---|---|---|
| Line 45: | Line 45: | ||
| * **Time: delays OK, stable and within 1us (clkoff, maserdelay)**\\ In the eRemoteControl, issue the commands ''clkoff'' and ''maserdelay''. These values should be within 0.5 microsecond of each other and stable (i.e. similar results if you issue the commands again). If not, see [[operations:monitoring_hb#clkoff_reading_is_drifting_or_far_from_the_maser-gps_offset|this entry]] in the common Problems section for a remedy. | * **Time: delays OK, stable and within 1us (clkoff, maserdelay)**\\ In the eRemoteControl, issue the commands ''clkoff'' and ''maserdelay''. These values should be within 0.5 microsecond of each other and stable (i.e. similar results if you issue the commands again). If not, see [[operations:monitoring_hb#clkoff_reading_is_drifting_or_far_from_the_maser-gps_offset|this entry]] in the common Problems section for a remedy. | ||
| * **Time: Maser status OK**\\ Check the "Standard VCH-1005A Manager" display on the Windows PC (to view it, start a VNC session to time[hb|ke|yg]). Green numbers are good, red are bad. Here's an example of how it should look:\\ {{:operations:maserok.jpg?200|}}\\ Report any red numbers to Brett ASAP. if you see mention of 'Battery', the maser has lost mains power and is running on it's UPS. If so, tell Brett immediately. | * **Time: Maser status OK**\\ Check the "Standard VCH-1005A Manager" display on the Windows PC (to view it, start a VNC session to time[hb|ke|yg]). Green numbers are good, red are bad. Here's an example of how it should look:\\ {{:operations:maserok.jpg?200|}}\\ Report any red numbers to Brett ASAP. if you see mention of 'Battery', the maser has lost mains power and is running on it's UPS. If so, tell Brett immediately. | ||
| + | * **Mark5: mk5=vsn? correct**\\Verify you're recording to the correct module with a ''mk5=vsn?'' command | ||
| * **Mark5: mk5=mode? correct**\\ Check mode with this command in the field system: ''mk5=mode?''. The result should agree with the procedure file setting in setup01 | * **Mark5: mk5=mode? correct**\\ Check mode with this command in the field system: ''mk5=mode?''. The result should agree with the procedure file setting in setup01 | ||
| * **Mark5: mk5=dot? response nominal**\\ This is a check of the Mark5 decoder time. Check the time offset in the formatter with this command in the field system:''mk5=dot?''. Make sure it reports a small offset (~<10ms) as the final value, that ''syncerr_eq_0'' and that ''FHG_on'' or ''FHG_off'' depending on whether it is currently recording or not. If not, ''fmset'' may need to be run. | * **Mark5: mk5=dot? response nominal**\\ This is a check of the Mark5 decoder time. Check the time offset in the formatter with this command in the field system:''mk5=dot?''. Make sure it reports a small offset (~<10ms) as the final value, that ''syncerr_eq_0'' and that ''FHG_on'' or ''FHG_off'' depending on whether it is currently recording or not. If not, ''fmset'' may need to be run. | ||
| To do this, open a terminal on pcfs[hb|ke|yg], and type | To do this, open a terminal on pcfs[hb|ke|yg], and type | ||
| <code>fmset</code> | <code>fmset</code> | ||
| + | Only run fmset when the mk5 is not recording; therefore, halt the schedule with **halt** and stop recording with **disk_record=off**; check with **mk5=dot?** | ||
| + | |||
| When the interface appears, type | When the interface appears, type | ||
| <code>s</code> | <code>s</code> | ||
| Line 55: | Line 58: | ||
| Following this, the clocks should all be synchronised and agree with UT. Press the [Esc] key to exit ''fmset''. Then check the times again: | Following this, the clocks should all be synchronised and agree with UT. Press the [Esc] key to exit ''fmset''. Then check the times again: | ||
| <code>mk5=dot?</code> | <code>mk5=dot?</code> | ||
| + | you can continue the schedule with **cont** | ||
| + | |||
| * **Mark5: disk_pos OK**\\ The command ''disk_pos'' in the field system should report three values - the current number of btyes recorded, bytes at start of previous scan and bytes at start of current scan. If not currently recording, the first and third values should agree. | * **Mark5: disk_pos OK**\\ The command ''disk_pos'' in the field system should report three values - the current number of btyes recorded, bytes at start of previous scan and bytes at start of current scan. If not currently recording, the first and third values should agree. | ||
| * **Meteorology: Weather (wth) being logged**\\ Look through recent messages in the field system log for output from the ''wth'' command, which will look like this:\\/#wx#/16.1,1007.9,58.6\\ | * **Meteorology: Weather (wth) being logged**\\ Look through recent messages in the field system log for output from the ''wth'' command, which will look like this:\\/#wx#/16.1,1007.9,58.6\\ | ||
/home/www/auscope/opswiki/data/attic/operations/documentation/lba_starting_and_monitoring.1363234494.txt.gz · Last modified: 2013/03/14 04:14 by Jim Lovell
Page Tools
