This is an old revision of the document!
Note that these steps are only necessary if e-remote Control is not already running.
It seems its best to start Hobart 12 [hb] first to avoid communication conflicts between econtrol and other field systems.
e-Remote Control (formerly known as econtrol) can be started from the Applications menu on ops2 (or on the local ops machines at Yarragadee and Katherine):
Applications -> AuScope [Hobart|Katherine|Yarragadee] -> e-remote control
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.
Common problems that cause E-remote to not respond include:
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
ps -ef | grep ercd
If this returns a list of one or more processes, kill them with a
Then go back to the top of this page and try starting e-remote control again.
If ctrl shift e does not work, run this code from a terminal in the pcfs VNC:
Once it is running, e-remote control is the main observing interface. You can send PCFS commands and comments from the bottom of the log window. Note you won’t see the log window update until you type in a command or the next scheduled command is sent.
Also click on the “M5 Capacity” box to view M5 Capacity