User Tools

Site Tools


operations:documentation.logmonitor_eremotectrl

This wiki is not maintained! Do not use this when setting up AuScope experiments!

This is an old revision of the document!


  1. First make sure that e-remote control is running for the antenna you wish to monitor.
  2. In e-remote control, in the “Logging and Operator Input” section, click on the red dot icon (“record the logfile”):

    This will open a dialog window where you need to give a name for the log file to be saved. Select the “Browse for other folders” option, then double-click on “logs” at the end of the list on the left (this is a shortcut to /vlbobs/ivs/logs). Finally, give the log file a name at the top of the dialog. Suggested syntax is
    <experiment_name>_<station_code>_econtrol.log

    e.g.: a file is saved in this location

    /vlbobs/ivs/logs/r4456_yg_econtrol.log
  3. The red dot icon in econtrol should now show a green bar in the top left to indicate that the log is being recorded:
  4. Type a command into the Operator Input section (next to the blue triangle) so that the new log file is created. e.g.
    clkoff
  5. Now start the log monitor from the Applications menu on ops2:
    Applications → AuScope → Log monitor
  6. You will be asked which station is being monitored (type 1, 2 or 3) and then the GUI will start.
  7. Select
    File → Open Log File
    and type in the name of the log file you just created (e.g. /vlbobs/ivs/logs/r4456_yg_econtrol.log) or click on Browse and find the file.
  8. Click OK and the monitor should now be tracking the log file and checking for problems.
  9. At the moment, this program will
    1. monitor the difference in delays between maser and GPS and formatter and GPS, and sound an alarm if they differ by more than 1 us
    2. watch for all other error messages and either beep or sound an alarm depending on severity
    3. watch for Mark5 sync errors that require fmset to be run.
  10. You can acknowledge an alarm which will turn off the siren. You can also mute the alarm for 5 mins at a time.

Note the log monitor script can also be started on ops6 (the PC in the “Lounge”). Just open a terminal window and repeat steps 5 and 6 above. Both ops2 and ops6 share the /vlbobs directory, so log recording needs to be started only from one place.

/home/www/auscope/opswiki/data/attic/operations/documentation.logmonitor_eremotectrl.1344990107.txt.gz · Last modified: 2012/08/15 00:21 by Jim Lovell