rpc.rigd(8)

1RIGD(8)                         RPC Rig Daemon                         RIGD(8)
2
3
4

NAME

6       rigd - Hamlib rig service daemon
7

SYNOPSIS

9       rpc.rigd [OPTION]...
10

DESCRIPTION

12       The  rigd  program  is  a  Hamlib  rig  daemon  that handles RPC client
13       requests. This allows multiple user programs to share  one  radio.   At
14       this time multiple radio 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

OPTIONS

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 radio model number. See rig model list (use 'rigctl -l').
34              NB: rigctl (or third party software) will  use  rig  model  1901
35              when using rigd.
36
37       -r, --rig-file=device
38              Use  device as the file name of the port the radio is connected.
39              Often a serial port, but could be a USB to serial adapter.  Typ‐
40              ically /dev/ttyS0, /dev/ttyS1, /dev/ttyUSB0, etc.
41
42       -p, --ptt-file=device
43              Use  device  as the file name of the Push-To-Talk device using a
44              device file as described above.
45
46       -d, --dcd-file=device
47              Use device as the file name of the Data  Carrier  Detect  device
48              using a device file as described above.
49
50       -p, --ptt-type=type
51              Use  type of Push-To-Talk device.  Supported types are RIG, DTR,
52              RTS, PARALLEL, NONE.
53
54       -d, --dcd-type=type
55              Use type of Data Carrier Detect  device.   Supported  types  are
56              RIG, DSR, CTS, CD, PARALLEL, NONE.
57
58       -s, --serial-speed=baud
59              Set  serial  speed  to baud rate. Uses maximum serial speed from
60              rig backend capabilities as the default.
61
62       -c, --civaddr=id
63              Use id as the CI-V address to communicate  with  the  rig.  Only
64              useful for Icom rigs.
65              NB:  the  id  is  in decimal notation, unless prefixed by 0x, in
66              which case it is hexadecimal.
67
68       -C, --set-conf=parm=val[,parm=val]*
69              Set config parameter.  e.g. stop_bits=2
70              Use -L option of rigctl for a list.
71
72       -t, --prog=number
73              Use number as the RPC program number. The default is 536871065.
74
75       -v, --verbose
76              Set verbose mode, cumulative (see DIAGNOSTICS below).
77
78       -h, --help
79              Show a summary of these options and exit.
80
81       -V, --version
82              Show the version of rigd and exit.
83
84       Please note that the backend for the radio to  be  controlled,  or  the
85       radio itself may not support some commands. In that case, the operation
86       will fail with a Hamlib error code.
87

EXAMPLES

89       Start rigd as root for a Yaesu FT-920 using a USB to serial adapter and
90       backgrounding:
91
92       # rpc.rigd -m 114 -r /dev/ttyUSB1 &
93
94       Start rigd as root for a Yaesu FT-920 using COM1 while generating TRACE
95       output:
96
97       # rpc.rigd -m 114 -r /dev/ttyS0 -vvvvv
98
99       Start rigd as root for a Yaesu FT-920 using a  USB  to  serial  adapter
100       while setting baud rate and stop bits and backgrounding:
101
102       # rpc.rigd -m 114 -r /dev/ttyUSB1 -s 4800 -C stop_bits=2 &
103

DIAGNOSTICS

105       The  -v,  --version option allows different levels of diagnostics to be
106       output to stderr and correspond to -v for BUG, -vv for  ERR,  -vvv  for
107       WARN, -vvvv for VERBOSE, or -vvvvv for TRACE.
108
109       A given verbose level is useful for providing needed debugging informa‐
110       tion to the email address below.  For example, TRACE output  shows  all
111       of  the values sent to and received from the radio which is very useful
112       for radio backend library development  and  may  be  requested  by  the
113       developers.
114

SECURITY

116       No authentication whatsoever; could be done through domain restriction,
117       though.  Please ask if stronger security is needed.
118

BUGS

120       Does not support more than one rig that  share  the  same  serial  port
121       (e.g. Icom radios on a CI-V bus).
122
123       Does  not  support  more than one communication device for multiple rig
124       control.  (e.g. for Single Operator 2 Radio)  Help needed!
125

REPORTING BUGS

127       Report bugs to <hamlib-developer@lists.sourceforge.net>.
128       We are already aware of the bugs in the previous section :-)
129

AUTHORS

131       Written by Stephane Fillod and the Hamlib Group
132       <http://www.hamlib.org>.
133

COPYRIGHT

135       Copyright © 2000-2007 Stephane Fillod and the Hamlib Group.
136
137       This is free software; see the source for copying conditions.  There is
138       NO  warranty;  not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
139       PURPOSE.
140