[Trlog] Rig Control Problem

Alan Dove alan at alandove.com
Thu Feb 17 09:24:08 EST 2022

Hey, folks:

Thanks again for the quick troubleshooting help. I've now run the
additional tests suggested, and it looks like hamlib is working but
TRlog isn't able to communicate with my rig through it. The workaround
James suggested for direct Icom control didn't work for me either. This
is probably just some weird thing unique to my setup, so I'll certainly
recommend that others try TRLinux, but in my case TLF just ended up
being easier to get working. Fortunately, the two programs have nearly
identical interfaces and both look like very capable contest loggers.

73, and I hope to see you on the bands.

         --Alan (AB1XW)

On Wed, 2022-02-16 at 22:55 -0700, w9cf at arrl.net wrote:
> Obviously, you should use whatever program you find works best.
> I don't have an Icom rig, so the built in Icom code is written from
> a combination of Tree's original code and the Icom documentation.
> I can test rigctld code with my rig.
> If you fire up trlog with the rigctld, you should be able to run
> ps -aef |grep rigctld
> and see the command that trlog is running. For example with a TS590SG
> as radio 1 with its built in USB serial port at /dev/ttyTS590sg_a,
> I have the LOGCFG.DAT line:
> rigctld;4532;/dev/ttyTS590sg_a;2037;115200;38;timeout=500;
> and with trlog running
> ps -aef |grep rictld
> shows
> schmidt  22906 22903  1 17:53 pts/8    00:02:56
> /usr/local/bin/rigctld --port=4532 --rig-file=/dev/ttyTS590sg_a --
> model=2037 --serial-speed=115200 --civaddr=38 --set-conf=timeout=500
> With the rig tuned to 3545.00 KHz, I can type
> ncat localhost 4532
> and then type an f key followed by an enter. ncat replies with
> 3545000
> showing that rigctld is working independently of trlog.
> If you have hamlib working with rigctld, you can make sure that
> rigctld
> is correctly receiving commands with ncat. If trlog doesn't work
> then,
> it is a bug in the trlog code.  If the ncat doesn't work, it is a
> problem
> in setting up rigctld or hamlib. If the rigctld process is defunct or
> not there, then try running it standalone in a terminal and
> connecting
> in a second terminal with ncat to see which command line argument is
> incorrect or to let me know if there is a bug.
> For what is is worth, my /usr/local/bin/rigctld is symbolically
> linked to
> /usr/bin/rigctld-wsjtx, the slightly modified hamlib 4 version
> distributed
> with the wsjtx source.
> 73 Kevin w9cf

More information about the Trlog mailing list