Both instances of flrig are trying to
use the same port for xmlrpc (probably 12345). Only one server can
be on the same port at one time. The second one will fail to
start. If both could run together, it would be chaos as both would
try to reply to same command.
On 12/14/23 16:15, Philip Rose, GM3ZZA
via groups.io wrote:
Progress (I hope).
I realised my logger is attempting to connect to the rig that
was used for the last QSO even if it's not connected. I suffered
the hamlib timeout every time I start my logger
?
If I don't do this and only try to connect to it once I've
started flrig for any or all of the rigs then I seem to connect
OK. I've tried this from a standing start and connected to both
rigs OK.
I now need to try this with all the apps.
Phil GM3ZZA
I have recently bought a new rig
IC705 in addition to the IC7300 I already have.
I have created two aliases for flrig to access the two
rigs using --config-dir. I have configured each instance
of flrig to listen to different ports :12345 for the
IC7300 and :12346 for the IC705.
I have only twice managed to connect my logging app
(zzalog) since, and both times to the IC705 instance. I
think it was when I started the IC705 then started zzalog.
I am using hamlib to connect to flrig. I tried WSJT-X and
that also failed to connect. Hamlib seems to timeout on
the connection after a couple of minutes.
I did originally make the mistake of not changing the port
number on the new instance of flrig, so maybe there is
some memory of this lingering about. My OS is debian
bookworm on a converted Dell laptop.
When I next get time, I'll try some more measured tries.
Phil GM3ZZA
--
/
* Amateur Radio Station AC0HY *
* W. Paul Mills SN807 *
* Assistant EC Alpha-1 ARES Shawnee/Wabaunsee, KS *
* President Kaw Valley Amateur Radio Club *
/
W Paul Mills AC?HY