Yes and no. For the 'yes' part:
You can point tlf to use the daemon (as Slave wrote) but it is activated via the normal hamlib library call (with rig model number 2). That means in these case it goes directly to the hamlib library and talk to rig model 2 which results in hamlib library making a TCP connection to rigctld (model number 2) (which talks to the hamlib library, which talks to the radio rigctld is configured for). (Sounds like overkill and make my head spinning). And for the first part of the game - talking to the hamlib library - it has to be adapted to the correct API. For the 'no' part: To use rigctld directly TLF has to be changed to use a direct TCP connection to rigctld. But that is not how TLF works at the moment. Summary: At the time being you have to recompile during the switch between Hamlib 3 and 4. 73, de Tom DL1JBE Am Wed, 16 Dec 2020 14:51:02 +0000 schrieb Drew Arnett <arnett.d...@gmail.com>: > 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 <t...@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 > > -- > > > > -- "Do what is needful!" Ursula LeGuin: Earthsea --
