User Tools

Site Tools


operations:monitoring_ke

Differences

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

Link to this comparison view

operations:monitoring_ke [2011/10/26 06:37] (current)
Line 1: Line 1:
 +===== Observations on the Katherine 12m =====
 +
 +Setting up for a Katherine observation.
 +
 +This can be done from ops4, the 4-monitor PC in the control room.
 +
 +1. Bring up VNC sessions on the katherine field system, timing PC and DBBC. This can be done via the Application menu in 
 +
 +the top right of the desktop:
 + Applications -> AuScope Katherine -> VNC -> [choose the server]
 +
 +2. Configure the DBBC. The procedure is the same as for Hobart but the DBBC control software is a newer version with two 
 +windows, one client window for commands and one server for responding to commands and logging results. To start it up, you need to start the ''​DBBC Control net.exe''​ program first (shortcut is on the desktop, upper RHS). To get the control interface, you then run ''​DBBC Client.exe''​. The command syntax is unchanged for this version of the DBBC software.
 +
 +3. Set up the Mark5 is the same way as for Hobart. The only differences are:
 +  *  The mark5 PC is called mk5ke
 +  * If dimino needs starting, do it via a terminal window in the pcfske VNC session. That way if the network goes down, dimino will continue to run
 +
 +4. Start the observations in the same way as Hobart, except the schedule name will end in ke instead of hb. e.g. 
 +schedule=r4455ke,#​1
 +
 +5. Start up a checklist GUI on ops4:
 + Applications -> AuScope Katherine -> Checklist GUI
 +
 +6. Start econtrol
 + Applications -> AuScope Katherine -> econtrol
 +
 +Click on the boxes next to “StatusMonitor"​ and "​Logging and Operator Input”. This should trigger the program to connect to pcfske and you’ll see a status window and log window. If you don't see any information updating in the status window, type [ctrl]-[shift]-e to start the server process on the field system. You can send PCFS commands and comments from the bottom of the log window. Note you won’t see the log window update until the next scheduled command is sent.
 +
 +
 +7. It's best to only have the katherine VNC sessions running when running through the checklist and to rely on econtrol ​
 +and the log monitor the rest of the time. You should use the VNC sessions to check that the autocorrelation spectra are ok though. ​
 +
 +8. Alarms are currently provided by the [[operations:​documentation.logmonitor| log monitor]].
 +
  
/home/www/auscope/opswiki/data/pages/operations/monitoring_ke.txt · Last modified: 2011/10/26 06:37 (external edit)