rigsmtr(1)

1RIGSMTR(1)                  General Commands Manual                 RIGSMTR(1)
2
3
4

NAME

6       rigswr - measure S-Meter vs azimuth using Hamlib
7

SYNOPSIS

9       rigswr [OPTION]... start_freq stop_freq [freq_step]
10

DESCRIPTION

12       rigswr uses Hamlib to control a rig to measure S-Meter vs azimuth:
13       It  scans frequencies from start_freq to stop_freq with step freq_step.
14       For each frequency, it transmits at 25% of total POWER during 0.5  sec‐
15       ond in CW mode and read VSWR.
16       Azimuth  in degree and corresponding S-Meter level in dB relative to S9
17       are then printed on stdout.
18       To work correctly, rigsmtr needs a rig that could measure S-Meter and a
19       Hamlib backend that is able to get it.
20
21       Keep  in mind that Hamlib is still BETA level software.  A lof of stuff
22       hasn't been tested thoroughly, and the API may  change  without  publi‐
23       cised  notice.  Please  report  bugs and feedback at the e-mail address
24       given in the REPORTING BUGS section.
25

OPTIONS

27       This program follow the  usual  GNU  command  line  syntax,  with  long
28       options  starting  with  two  dashes  (`-').   A  summary of options is
29       included below.
30
31       -m, --model=id
32              Select radio model number. See model list provided by rigctl.
33
34       -r, --rig-file=device
35              Use device as the file name of the radio to operate on.
36
37       -s, --serial-speed=baud
38              Set serial speed  to  baud  rate.  Uses  maximal  rig  speed  as
39              default.
40
41       -c, --civaddr=id
42              Use  id  as  the CI-V address to communicate with the rig.  Only
43              for Icom rigs. NB: the id is in decimal, unless prefixed by  0x,
44              in which case it is hexadecimal.
45
46       -p, --ptt-file=device
47              Use  device as the file name of the Push-To-Talk device to oper‐
48              ate on.  This is only needed if the radio  doesn't  have  legacy
49              PTT control.
50
51       -p, --ptt-type=type
52              Use  type device as the kind of the Push-To-Talk device to oper‐
53              ate on.  Supported types are  RIG,  DTR,  RTS,  PARALLEL,  NONE.
54              This  is  only  needed if the radio doesn't have legacy PTT con‐
55              trol.
56
57       -C, --set-conf=parm=val[,parm=val]*
58              Set config parameter. See -L option of rigctl for a list.
59
60       -v, --verbose
61              Set verbose mode, cumulative (BUG, ERR, WARN, VERBOSE, TRACE).
62
63       -h, --help
64              Show summary of options and exit.
65
66       -V, --version
67              Show version of program and exit.
68
69

RETURN VALUE

71       rigswr exits with: 0 if all operations went fine; 1  if  there  was  an
72       invalid  command line option or arg; 2 if an error was returned by Ham‐
73       lib; 3 if the rig doesn't have the required capabilities.
74
75

EXAMPLE

77       rigswr -m 209 -r /dev/tty1 14000000 14350000 50000 > cswr
78
79       Scans frequencies between 14MHz and 14.200MHz  with  50KHz  step  on  a
80       TS850 and record VSWR measurements in file cswr.
81       After completion, cswr file contains the following lines :
82         14000000 1.50
83         14050000 1.31
84         14100000 1.22
85         14150000 1.07
86         14200000 1.07
87
88
89       Result could then be ploted with gnuplot:
90              gnuplot
91              set data style linespoints
92              set grid
93              plot "cswr"
94

AUTHOR

96       Man page written by Thierry Leconte & Stephane Fillod .
97

BUGS

99       Depending on keyer/QSK setup, transmits in CW mode may not be modulated
100       thus giving possibly wrong result. Please report this situation  if  it
101       happens.
102

REPORTING BUGS

104       Report bugs to <hamlib-developer@users.sourceforge.net>.
105

COPYRIGHT

107       Copyright © 2004-2006 Thierry Leconte & Stephane Fillod
108       This is free software; see the source for copying conditions.  There is
109       NO warranty; not even for MERCHANTABILITY or FITNESS FOR  A  PARTICULAR
110       PURPOSE.
111