howto:change_variables_from_a_terminal_session
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | howto:change_variables_from_a_terminal_session [Unknown date] (current) – external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | This is a how to change rts2 variables for the telescope or other instruments, | ||
+ | The motivation from this is to benefit from the versatility of other UNIX utilities to run scripts. | ||
+ | |||
+ | ====== Using rts2-xmlrpcclient ====== | ||
+ | You must first have a config file (default is / | ||
+ | that contains the user and password for the running xmlrpcclient interface under [xmlrpc] | ||
+ | |||
+ | |||
+ | [xmlrpc] | ||
+ | | ||
+ | authorization = " | ||
+ | |||
+ | Then you must simply run " | ||
+ | |||
+ | For example to set a specific target to be observed next: | ||
+ | rts2-xmlrpcclient -s EXEC.next 3 | ||
+ | | ||
+ | Now if you want to set a specific variable each hour, day or week the man page for the command cron should be looked at. | ||
+ | |||
+ | For running a command only once at a certain time, the " | ||
+ | echo " | ||
+ | See the man page of at for other ways to specify time. Remember this is by default in local telescope time. | ||
+ | |||
+ | Another important feature is to send commands, which is not the same as setting variables. For example if you want the executor to stop the current observation and observe a specific target immediately: | ||
+ | rts2-xmlrpcclient -c EXEC.now 3 | ||
+ | |||
+ | This is also good for parking or moving the telescope or asking the dome to " |
howto/change_variables_from_a_terminal_session.txt · Last modified: 2012/06/11 00:00 (external edit)