Re: TLF and Hamlib 4 - things to look for

[EI6KW]

It's working for me with rigctld and I can use other software simultaneously without any troubles.

This needs in logcfg.dat:

RIGPORT=localhost:4532 (change 4532 if other port is used)

W dniu 16.12.2020 o 14:51, Drew Arnett pisze:

> Dumb question:  Can some of this be avoided by running rigctld and
> then pointing tlf to the daemon?  They didn't change the network
> protocol for rigctld, did they?
>
> Best regards,
>
> Drew
> n7da
>
> On Wed, Dec 16, 2020 at 5:48 AM Thomas Beierlein <tb@hs-mittweida.de> wrote:
> > Hi all,
> >
> > if you want to play with the new Hamlib 4 release candidates for
> > TLF there are some points to remember:
> >
> > 1. Hamlib 4 has changed the scheme for rig numbers to make room for more
> >   new rigs. Please have a look with 'rigctl -l', find your new rig
> >   number and adapt logcfg.dat accordingly.
> >
> > 2. IMPORTANT! Hamlib 4 has a different program API than the versions
> >   before. So any time you switch from Hamlib 3 to 4 (or maybe back) you
> >   have to recompile TLF to adapt to the other API.
> >
> > Afterwards TLF should be able to work with your rig as before.
> >
> > 73, de Tom DL1JBE
> >
> > --
> > "Do what is needful!"
> > Ursula LeGuin: Earthsea
> > --
> >
> >
> >       
>     
-- 
73!
de Slav, EI6KW

FISTS #19019
SOC #1251
TRC #015-Ireland