1ROTD(8) RPC Rotator Daemon ROTD(8)
2
3
4
6 rotd - Hamlib rotator service daemon
7
9 rpc.rotd [OPTION]...
10
12 The rotd program is a Hamlib rotator daemon that handles RPC client
13 requests. This allows multiple user programs to share one rotator. At
14 this time multiple rotator support is not available (help needed!).
15
16 Keep in mind that Hamlib is BETA level software. While a lot of back‐
17 end libraries lack complete rig support, the basic functions are usu‐
18 ally well supported. The API may change without publicized notice,
19 while an advancement of the minor version (e.g. 1.1.x to 1.2.x) indi‐
20 cates such a change.
21
22 Please report bugs and provide feedback at the e-mail address given in
23 the REPORTING BUGS section. Patches and code enhancements are also
24 welcome.
25
27 This program follows the usual GNU command line syntax, with long
28 options starting with two dashes (`-').
29
30 Here is a summary of the supported options:
31
32 -m, --model=id
33 Select rotator model number. See model list (use 'rotctl -l').
34 NB: rotctl (or third party software) will use rotor model 101
35 when using rotd.
36
37 -r, --rot-file=device
38 Use device as the file name of the port the rotator is con‐
39 nected. Often a serial port, but could be a USB to serial
40 adapter. Typically /dev/ttyS0, /dev/ttyS1, /dev/ttyUSB0, etc.
41
42 -s, --serial-speed=baud
43 Set serial speed to baud rate. Uses maximum serial speed from
44 rotor backend as the default.
45
46 -C, --set-conf=parm=val[,parm=val]*
47 Set config parameter. e.g. stop_bits=2
48 Use -L option of rotctl for a list.
49
50 -t, --prog=number
51 Use number as the RPC program number. The default is 536873369.
52
53 -v, --verbose
54 Set verbose mode, cumulative (see DIAGNOSTICS below).
55
56 -h, --help
57 Show summary of these options and exit.
58
59 -V, --version
60 Show version of rpc.rotd and exit.
61
62 Please note that the backend for the rotator to be controlled, or the
63 rotator itself may not support some commands. In that case, the opera‐
64 tion will fail with a Hamlib error code.
65
67 Start rotd as root for a RotorEZ using a USB to serial adapter and
68 backgrounding:
69
70 # rpc.rotd -m 401 -r /dev/ttyUSB1 &
71
72 Start rotd as root for a RotorEZ using COM1 while generating TRACE out‐
73 put:
74
75 # rpc.rotd -m 401 -r /dev/ttyS0 -vvvvv
76
77 Start rotd as root for a RotorEZ using a USB to serial adapter while
78 setting baud rate and stop bits and backgrounding:
79
80 # rpc.rotd -m 401 -r /dev/ttyUSB1 -s 4800 -C stop_bits=2 &
81
83 The -v, --version option allows different levels of diagnostics to be
84 output to stderr and correspond to -v for BUG, -vv for ERR, -vvv for
85 WARN, -vvvv for VERBOSE, or -vvvvv for TRACE.
86
87 A given verbose level is useful for providing needed debugging informa‐
88 tion to the email address below. For example, TRACE output shows all
89 of the values sent to and received from the rotator which is very use‐
90 ful for rotator backend library development and may be requested by the
91 developers.
92
94 No authentication whatsoever; could be done through domain restriction,
95 though. Please ask if stronger security is needed.
96
98 Does not support more than one communication device for multiple rotor
99 control. (e.g. for Single Operator 2 Radio) Help needed!
100
102 Report bugs to <hamlib-developer@lists.sourceforge.net>.
103 We are already aware of the bug in the previous section :-)
104
106 Written by Stephane Fillod and the Hamlib Group
107 <http://www.hamlib.org>.
108
110 Copyright © 2000-2007 Stephane Fillod and the Hamlib Group. Contrib‐
111 uted by Francois Retief <fgretief@sun.ac.za>.
112 This is free software; see the source for copying conditions. There is
113 NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
114 PURPOSE.
115
117 rotctl(1), hamlib(3)
118
119
120
121Hamlib February 24, 2007 ROTD(8)