Will,
I have a branch that has basic support for hamlib through rigctld
that I have been slowly working on. This branch has native support for
kenwood/elecraft rigs and icom rigs. It also has the code for native
support for the ft5000dx and the ft3000dx, but I have not yet written
the interface code to set up those rig types yet from LOGCFG.DAT.
The documentation is not yet written. One advantage of using rigctld
is that if the code natively supports your rig, you do not need to
install hamlib.
I have pushed this branch to github. It is the trrig branch.
If anyone wants to try this before I have completed work and integrated
it into the master branch, please pull the source code from github, and
compile it. You will need the free pascal compiler, gcc, and various
libraries, most or all of which are normally installed on standard
linux distributions:
libX11
libasound
libieee1284
libsndfile
libusb-1.0
libcurl
If all is set up properly, typing make in the top level directory should
produce all the files that are in the binary distribution. Generally, to
compile on a new computer, I just need to install the free pascal compiler.
To use rigctld with this trrig version, first make sure that rigctld is
in your path so TR can find it. Then use a LOGCFG.DAT file like:
my call = w9cf
contest = cq ww
display mode = color
radio one type = rigctld;4532;/dev/ttyS0;221;4800;38;
The last line is the one I use for my K2 with rigctld. The semicolons
separate
1. the port number for the rigcltd, here the default 4532. You need
a different port number for each instance of rigctld, so if you are
running SO2R use something like 4534 for the second rig.
2. the serial port device that is connected to the rig, here /dev/ttyS0.
3. the "model number" from rigctld. You can find this by typing
rigctld -l |more
and finding your rig. The Elecraft K2 is model 221.
4. the baud rate, 4800 for the K2.
5. the Icom CIV address. For Icoms, this is the correct CIV address for
your rig. For all other rigs, use any value. I used 38 above.
But note, Icoms and Kenwood/Elecraft work natively with the code so
rigctld should not be necessary for them, and rigctld/hamlib has some
limitations (e.g. no way to zero RIT without turning it off).
Note, TR will execute rigctld itself as a separate process. You don't
have to run it yourself.
rigctld with this version works for me on my K2. If you are unable to
compile the code, I can build a binary version, but that will take me
extra time since my release version scripts are only set up to use the
master branch.
73 Kevin w9cf
On Wed, Dec 09, 2015 at 04:39:55AM -0600, George Fremin III wrote:
> I think w9cf has hamlib support working. Check with him I think there has
> been recent testing going on.
>
> --
> George Fremin III
> geoiii@kkn.net
>
> > On Dec 8, 2015, at 8:52 PM, William Liporace <wc2l@wc2l.com> wrote:
> >
> > Still waiting for hamlib or more radio control....
> > FTdx5000 still not supported
> >
> > Will WC2L
> >
> > --
> > William Liporace WC2L
> > http://www.wc2l.com or http://dxc.wc2l.com
> > AR-Cluster Node telent dxc.wc22l.com or 144.93 MHz
> > wc2l@wc2l.com
_______________________________________________
Trlog mailing list
Trlog@contesting.com
http://lists.contesting.com/mailman/listinfo/trlog
|