User Tools

Site Tools


operations:starting_eremotectrl

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.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
operations:starting_eremotectrl [2013/10/23 00:42]
Imogen Jones
operations:starting_eremotectrl [2017/06/08 14:13]
Arwin Kahlon
Line 10: Line 10:
 Click on the tab with the name of the antenna (e.g. "​Hobart12"​) and you'll be prompted for a username and password. From the AuScope Operations room, use the oper account. From Yarragadee use the ''​ygobserver''​ account and from Katherine ''​keobserver''​. It's the usual password. Start the Hobart econtrol first or you may run into socket issues. Click on the tab with the name of the antenna (e.g. "​Hobart12"​) and you'll be prompted for a username and password. From the AuScope Operations room, use the oper account. From Yarragadee use the ''​ygobserver''​ account and from Katherine ''​keobserver''​. It's the usual password. Start the Hobart econtrol first or you may run into socket issues.
  
-Click on the boxes next to “StatusMonitor"​ and "​Logging and Operator Input”. This should trigger the program to connect to pcfs[hb|ke|yg] 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. If you still don't see any status window updates the server process may need re-starting. Exit from e-remote control, open a terminal in the VNC session on pcfs[hb|ke|yg] and type +Click on the boxes next to “StatusMonitor"​ and "​Logging and Operator Input”. This should trigger the program to connect to pcfs[hb|ke|yg] 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. ​ 
 + 
 +**Troubleshooting** 
 + 
 +Common problems that cause E-remote to not respond include: 
 + 
 +     * E-remote is no longer connecting to the field system computer. ​ Anything but a green rectangle in the bottom right hand corner of e-remote is bad. 
 +     * The field system computer is no longer connected to the internet. ​ Check this by pinging pcfs[hb|ke|yg] (or just opening a VNC session). 
 +     * The field system has crashed. VNC into pcfs[hb|ke|yg] and make sure the field system software is running. ​ If not, start it in an empty terminal. You will have to restart the setup procedure. 
 +     * It's just decided to have a fit, in which case simply closing the e-remote session and re-opening it may fix it.  If the field system has been running the whole time and the problem is with the e-remote software only, you will NOT have to restart the entire setup procedure as the schedule should have been running the whole time. 
 + 
 + 
 +If you still don't see any status window updates the server process may need re-starting. Exit from e-remote control, open a terminal in the VNC session on pcfs[hb|ke|yg] and type 
 <​code>​ ps -ef | grep ercd </​code>​ <​code>​ ps -ef | grep ercd </​code>​
 If this returns a list of one or more processes, kill them with a If this returns a list of one or more processes, kill them with a
Line 18: Line 30:
 If ctrl shift e does not work, run this code from a terminal in the pcfs VNC: If ctrl shift e does not work, run this code from a terminal in the pcfs VNC:
  
-<​code>/​usr2/​eremotectrl/​bin/​ercd /​usr2/​eremotectrl/​config/​eremotectrl/conf</​code>​+<​code>/​usr2/​eremotectrl/​bin/​ercd /​usr2/​eremotectrl/​config/​eremotectrl.conf</​code>​
  
 Once it is running, e-remote control is the main observing interface. Once it is running, e-remote control is the main observing interface.
Line 24: Line 36:
  
 Also click on the "M5 Capacity"​ box to view M5 Capacity ​ Also click on the "M5 Capacity"​ box to view M5 Capacity ​
 +
 +**Alternative way to have alarms**
 +
 +If you cannot get eremnote control to work you can still have log monitor alarms. You can use Dave's stream log script. On a terminal in ops8 type (e.g for hb):
 +
 +./​stream_log hb
 +
 +This will begin streaming the log from pcfs to /​tmp/​hb.log. Then from the log monitor, start monitoring that file (/​tmp/​hb.log). Seems to be best to do a clkoff first.
/home/www/auscope/opswiki/data/pages/operations/starting_eremotectrl.txt · Last modified: 2021/01/20 05:06 by Warren Hankey