1GRIG(1)                          User Commands                         GRIG(1)
2
3
4

NAME

6       grig  -  graphical  user  interface for the Ham Radio Control Libraries
7       (hamlib)
8
9

SYNOPSIS

11       grig [OPTION]...
12
13

DESCRIPTION

15       Grig is a simple Ham Radio control (CAT) program based on the Ham Radio
16       Control  Libraries.  It is intended to be highly generic presenting the
17       user to the same graphical user interface regardless of which radio  is
18       being controlled.
19
20       Grig  does not store any radio configuration, instead it takes a number
21       of command line options.
22
23       -m, --model=ID
24              select radio model number; see --list
25
26       -r, --rig-file=DEVICE
27              set device of the radio, eg. /dev/ttyS0
28
29       -s, --speed=BAUD
30              set transfer rate (serial port only)
31
32       -c, --civ-addr=ID
33              set CI-V address (decimal, ICOM only)
34
35       -C, --set-conf=par=val[,par2=val2]
36              set additiional configuration parameters
37
38       -d, --debug=LEVEL
39              set hamlib debug level (0..5)
40
41       -D, --delay=VALUE
42              set delay between commands in msec (see below)
43
44       -n, --nothread
45              use timeout calls instead of thread (see below)
46
47       -l, --list
48              list supported radios and exit
49
50       -p, --enable-ptt
51              enable ptt control
52
53       -P, --enable-pwr
54              enable power status control
55
56       -h, --help
57              show a brief help message and exit
58
59       -v, --version
60              show version information and exit
61
62       Example: Start grig using YAESU FT-990 connected to  the  first  serial
63       port, using 4800 baud and debug level set to warning:
64
65            grig -m 116 -r /dev/ttyS0 -s 4800 -d 3
66
67       or if you prefer the long options:
68
69            grig --model=116 --rig-file=/dev/ttyS0 --speed=4800 --debug=3
70
71       It is usually enough to specify the model ID and the DEVICE.
72
73       If you start grig without any options it will use the Dummy backend and
74       set the debug level to 0 (RIG_DEBUG_NONE). If you do  not  specify  the
75       transfer  rate  for  the  serial port, the default serial speed will be
76       used by the backend and even if you specify a value, it can be overrid‐
77       den  by  the backend. If you omit the radio device (port) grig will use
78       /dev/ttyS0 or localhost if the selected radio is RPC-rig.
79
80

DEBUG LEVELS

82       0    No debug, keep quiet.
83       1    Serious bug.
84       2    Error case (e.g. protocol, memory allocation).
85       3    Warnings.
86       4    Verbose information.
87       5    Trace.
88
89       Grig has its own debug message handler, which will manage messages from
90       hamlib too.  The messages are printed to STDERR by default but they can
91       be redirected to a file.  In bash shell you would write something like:
92
93            grig [options] 2> grig.log
94
95       You can then use the Message Window in the View menu to view these mes‐
96       sages.  The  debug messages printed by grig a formatted in a structured
97       way with each line containing both time, source and level of  the  mes‐
98       sage.  Each  field  is separated with ;; so you can also import the log
99       file into a spread sheet for further analysis.
100
101

FEATURES

103       Grig 0.8.1 supports the most commonly used CAT command  implemented  by
104       hamlib.  These  include  frequency, mode, filter and various level set‐
105       tings. Please note that not all features have  been  thoroughly  tested
106       since  I  don't  have  access to any modern high-end radios. Therefore,
107       comments regarding success or failure in  using  grig  will  be  highly
108       appreciated.
109
110

KNOWN BUGS AND LIMITATIONS

112       Buffer Overflow in Radio
113              By default, grig tries to execute rig commands as fast as possi‐
114              ble in order to achieve an almost real-time remote control expe‐
115              rience. This strategy has turned out to cause problems with some
116              radios, probably because these radios acknowledge the  reception
117              of  a  command  before  executing them, whereby the next command
118              will be sent before the previous one has  terminated.  To  avoid
119              any possible buffer overflow in these situations, one can try to
120              experiment with the -D or --delay command line  argument,  which
121              will  put  the specified delay in between each executed command.
122              The default value is 10 milliseconds and the  smallest  possible
123              value  is  1  millisecond (if one specifies 0 millisecond on the
124              command line, the default value will be
125               used).  If you find a value which is better for your radio than
126              the default value, please let us know about it.
127
128       Daemon Never Starts on FreeBSD
129              There  have  been  reports  on that the new, thread-based daemon
130              process is never  started  on  FreeBSD,  while  the  old,  time‐
131              out-based daemon worked fine. It is therefore possible to choose
132              the two ways to run the daemon process. The default is  the  new
133              thread based daemon, but if you use FreeBSD and nothing seems to
134              work after start-up you can select the timout-based daemon  with
135              the -n or --nothread command line option.
136
137       Connection Settings
138              Once you have started grig you can not change the radio settings
139              (model, device, speed). You will have to restart the program  if
140              you want to change any of these settings.
141
142       Multiple Radios
143              Grig can control only one radio at the time. There are, however,
144              no problems in starting several instances of  grig  as  long  as
145              they  do not try to control the same radio. An exception to this
146              is the RPC-rig backend in which case the rpc rig daemon will act
147              as a server while grig or any other hamlib frontends will act as
148              a clients.
149
150       Power OFF State
151              On some radios, grig does not cope very well with the power  off
152              state.  It  is yet not known whether this is a bug in the hamlib
153              backend or in grig and we will definitely appreciate your input.
154              The  situation  gets  even more complicated due to the fact that
155              different radios behave in a different ways when they  are  pow‐
156              ered  OFF;  some of them will continue to respond to remote com‐
157              mands, while others will not. Even  the  same  radio,  like  the
158              FT-817,  can  behave differently depending on whether it is pow‐
159              ered from internal batteries or  external  power  supply.   Grig
160              tries  to  handle this mess by suspending all rig commands while
161              in power OFF state. Only the power ON command will  be  sent  to
162              the  rig.   By default, the power status control is disabled and
163              must explicitly be enabled using the -P or --enable-pwr  command
164              line switch.
165
166       PTT Control
167              Similar to the power state, the PTT has caused strange behaviour
168              on some radios.  Consequently, it has been disabled  by  default
169              but  can  be  enabled  using the -p or --enable-ptt command line
170              aguments.
171
172

AUTHOR

174       Written by Alexandru Csete, OZ9AEC.
175
176

REPORTING BUGS

178       Report bugs to <groundstation-developer@lists.sourcforge.net>.
179       Bugs related to hamlib should be reported directly to the hamlib devel‐
180       opers at <hamlib-developer@lists.sourceforge.net>.
181
182
184       Copyright © 2001-2006 Alexandru Csete.
185       This is free software; see the source for copying conditions.  There is
186       NO warranty; not even for MERCHANTABILITY or FITNESS FOR  A  PARTICULAR
187       PURPOSE.
188
189

SEE ALSO

191       rigctl(1)
192
193
194
195
196Alexandru Csete                  Version 0.8.1                         GRIG(1)
Impressum