This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
operations:starting_eremotectrl [2013/02/04 06:28] Jamie McCallum |
operations:starting_eremotectrl [2013/06/11 04:42] Jim Lovell |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Starting e-Remote Control ====== | ====== Starting e-Remote Control ====== | ||
Note that these steps are only necessary if e-remote Control is not already running. | 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): | 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): | ||
Line 16: | Line 18: | ||
Once it is running, e-remote control is the main observing interface. | 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. | 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. | ||
- |