开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Linuxham
  2. Topics

Multiple rigs. #flrig

 

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
Cliff, AE5ZA
 

开云体育

Phil,?

Can you help me understand the connection between flrig and Hamlib? If fldigi only one or the other will be operational at any one time.

73,
Cliff, AE5ZA



On Dec 14, 2023, at 15:02, Philip Rose, GM3ZZA via <gm3zza@...> wrote:

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
 

开云体育

Hi Cliff,

Hamlib has as one of its rigs: FlRig.

Hamlib can drive the xmlrpc interface to flrig. I found that easier to use than trying to control the xmlrpc from within my logger.

BTW I've made progress on my original problem - in a separate response.

Phil

From: [email protected] <[email protected]> on behalf of Cliff, AE5ZA <ae5zaham@...>
Sent: Thursday, December 14, 2023 9:49 PM
To: [email protected] <[email protected]>
Subject: Re: [linuxham] Multiple rigs. #flrig
?
Phil,?

Can you help me understand the connection between flrig and Hamlib? If fldigi only one or the other will be operational at any one time.

73,
Cliff, AE5ZA



On Dec 14, 2023, at 15:02, Philip Rose, GM3ZZA via <gm3zza@...> wrote:

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
 

开云体育

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

From: [email protected] <[email protected]> on behalf of Philip Rose, GM3ZZA via groups.io <gm3zza@...>
Sent: Thursday, December 14, 2023 9:02 PM
To: [email protected] <[email protected]>
Subject: [linuxham] Multiple rigs. #flrig
?
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
Cliff, AE5ZA
 

开云体育

So somehow your logger connects to flrig? For me I use Fllog and it connects directly to fldigi and flrig connects directly to fldigi. I suppose your logger has some special features that are helpful for you. If it works enjoy!

73,
Cliff, AE5ZA



On Dec 14, 2023, at 16:07, Philip Rose, GM3ZZA via <gm3zza@...> wrote:

Hi Cliff,

Hamlib has as one of its rigs: FlRig.

Hamlib can drive the xmlrpc interface to flrig. I found that easier to use than trying to control the xmlrpc from within my logger.

BTW I've made progress on my original problem - in a separate response.

Phil
From:?[email protected]?<[email protected]> on behalf of Cliff, AE5ZA <ae5zaham@...>
Sent:?Thursday, December 14, 2023 9:49 PM
To:?[email protected]?<[email protected]>
Subject:?Re: [linuxham] Multiple rigs. #flrig
?
Phil,?

Can you help me understand the connection between flrig and Hamlib? If fldigi only one or the other will be operational at any one time.

73,
Cliff, AE5ZA



On Dec 14, 2023, at 15:02, Philip Rose, GM3ZZA via??<gm3zza@...> wrote:

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
 

开云体育

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
From: [email protected] <[email protected]> on behalf of Philip Rose, GM3ZZA via groups.io <gm3zza@...>
Sent: Thursday, December 14, 2023 9:02 PM
To: [email protected] <[email protected]>
Subject: [linuxham] Multiple rigs. #flrig
?
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         *
/

 

开云体育

Thanks Paul,

If you read all of my post, you will see I made that mistake at first but then corrected it and still suffered the problem.

My logger tried to connect to the last rig used regardless as to whether it was there or not. I created an instance of the hamlib RIG class for each of the two rigs. The timeout on the first access seemed to create a sticky flag that then caused all accesses to fail.?

I modified my code to only allow me to manually connect each rig once I had switched them on. Since then I've not had a problem with either my logger or wsjtx access the two instances of flrig independently.

Phil GM3ZZA

From: [email protected] <[email protected]> on behalf of W Paul Mills AC?HY <ac0hy@...>
Sent: Friday, December 15, 2023 3:57 PM
To: [email protected] <[email protected]>
Subject: Re: [linuxham] Multiple rigs. #flrig
?
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
From: [email protected] <[email protected]> on behalf of Philip Rose, GM3ZZA via groups.io <gm3zza@...>
Sent: Thursday, December 14, 2023 9:02 PM
To: [email protected] <[email protected]>
Subject: [linuxham] Multiple rigs. #flrig
?
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         *
/

1 - 7 of 7