User Tools

Site Tools


operations:checklist_parameters

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
operations:checklist_parameters [2012/02/20 03:09]
Jim Lovell
operations:checklist_parameters [2013/08/29 01:05] (current)
Warren Hankey
Line 9: Line 9:
   * **delays OK, stable and within 1us (clkoff, maserdelay)**\\ In the econtrol, 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). The monitoring software will calculate the difference for you and should ring an alarm if the difference is not acceptable. 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.   * **delays OK, stable and within 1us (clkoff, maserdelay)**\\ In the econtrol, 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). The monitoring software will calculate the difference for you and should ring an alarm if the difference is not acceptable. 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.
   * **Maser status OK**\\ Check the "​Standard VCH-1005A Manager"​ display on the Windows PC (to view it, start a VNC session via the Applications menu 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.   * **Maser status OK**\\ Check the "​Standard VCH-1005A Manager"​ display on the Windows PC (to view it, start a VNC session via the Applications menu 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.
-  * **mk5=mode? correct**\\ Check mode with this command in econtrol: ''​mk5=mode?''​. The result should be\\ ''/​mk5/​!mode?​ 0 : ext : 0x55555555 : 2 : 2 ;''​ for R1 and R4 experiments,​\\ ''/​mk5/​!mode?​ 0 : ext : 0x55555555 : 4 : 2 ;''​ for OHIG, APSG and CRF observations.+  * **mk5=mode? correct**\\ Check mode with this command in econtrol: ''​mk5=mode?''​. The result should be\\ ''/​mk5/​!mode?​ 0 : ext : 0x55555555 : 2 : 2 ;''​ for R1R4 and CRF experiments,​\\ ''/​mk5/​!mode?​ 0 : ext : 0x55555555 : 4 : 2 ;''​ for OHIG, APSG and observations.
   * **mk5=dot? response nominal**\\ This is a check of the Mark5 decoder time. Check the time offset in the formatter with this command in econtrol:''​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.   * **mk5=dot? response nominal**\\ This is a check of the Mark5 decoder time. Check the time offset in the formatter with this command in econtrol:''​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.
   * **disk_pos OK**\\ The command ''​disk_pos''​ in econtrol 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. It is normal for Yarragadee ''​disk_pos''​ to lag its expected value due to regular stows for USN uplinks.   * **disk_pos OK**\\ The command ''​disk_pos''​ in econtrol 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. It is normal for Yarragadee ''​disk_pos''​ to lag its expected value due to regular stows for USN uplinks.
/home/www/auscope/opswiki/data/pages/operations/checklist_parameters.txt · Last modified: 2013/08/29 01:05 by Warren Hankey