Logger32 starts up on Radio 2 UDP port
|
Hello Bob. My workaround is slightly different. I deleted the WSJT Radio 2 UDP Port entry in the .ini and I am not using radio 2 for the moment. Now when I open Logger32 it starts on Radio 1 and the UDP bandmap opens as ‘listening’ on the radio 1 UDP socket just waiting for me to open JTDX… Just lovely..
73 Darren G0TSM
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 23 November 2022 12:54 To: hamlogger@groups.io Subject: Re: [hamlogger] Logger32 starts up on Radio 2 UDP port
It's a case of the chicken or the egg, which came first? If you choose to automatically open the UDP port before opening the UDP BandMap (as you do) then things get confused because at the point in time when Logger32 opens the UDP port it has not yet decided which radio it is going to use.
The fix is relatively simple to code. Don't open the UDP port automatically until after deciding which radio will be used.
I don't know exactly what steps you take when operating, but as a potential workaround (until the next auto-update) try closing the UDP port before closing Logger32. You only need to do this once. Now when starting Logger32 the UDP port will not open until you open the UDP BandMap (after Logger32 has decided what radio to use).
Or something like that. SeventyThree(s)
|
|
|
|
Arturo LU6ETB
Hi Darren, Same issue here. 73 de Arturo, LU6ETB El mar, 22 nov 2022 a las 11:33, Darren Collins (G0TSM) (<daz@...>) escribió:
|
|
|
|
Bob
It's a case of the chicken or the egg, which came first? If you choose to automatically open the UDP port before opening the UDP BandMap (as you do) then things get confused because at the point in time when Logger32 opens the UDP port it has not yet decided which radio it is going to use.
The fix is relatively simple to code. Don't open the UDP port automatically until after deciding which radio will be used.
I don't know exactly what steps you take when operating, but as a potential workaround (until the next auto-update) try closing the UDP port before closing Logger32. You only need to do this once. Now when starting Logger32 the UDP port will not open until you open the UDP BandMap (after Logger32 has decided what radio to use).
Or something like that. SeventyThree(s)
|
|
|
|
Bob
Having looks at your screenshot, I think I can duplicate your scenario. The secret appears to be opening the UDP port without opening the UDP BandMap. I can now see Radio 1 selected, but the UDP Port for Radio 2 opened/listening.
It's now Famous Grouse time. I will investigate this tomorrow. SeventyThree(s).
|
|
|
|
Thanks for checking Bob. If I am using Radio 1 and close Logger32 and reopen it, then it will open up on Radio 1 (where I left off) with the CAT working with radio 1 but the UDP port that opens is for Radio 2. The UDP Band map opens with ‘Listening…’.
Screen shot attached is where I was on 20M FT8 on Radio 1 (UDP Port 2237) and I have closed Logger32 and reopened and hovering over the UDP shows the open UDP port as port 2250 which is assigned to Radio 2.
Is there anything I can check for?
Thank You & 73 Darren G0TSM
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Bob
Sent: 22 November 2022 15:25 To: hamlogger@groups.io Subject: Re: [hamlogger] Logger32 starts up on Radio 2 UDP port
I'm not sure what I'm looking for. I configured Radio 1 UDP port to be 2237 and Radio 2 to be 2242.
Start Logger32. Select Radio 1. Start JTDX. Mouse over the UDP pane of the lower status bar say listening on port 2237.
Stop JTDX. Select Radio 2. Start JTDX. Mouse over the UDP pane of the lower status bar say listening on port 2242.
Switch to Radio 1. Mouse over the UDP pane of the lower status bar say listening on port 2237.
What am I missing? SeventyThree(s).
|
|
|
|
Bob
I'm not sure what I'm looking for. I configured Radio 1 UDP port to be 2237 and Radio 2 to be 2242.
Start Logger32. Select Radio 1. Start JTDX. Mouse over the UDP pane of the lower status bar say listening on port 2237.
Stop JTDX. Select Radio 2. Start JTDX. Mouse over the UDP pane of the lower status bar say listening on port 2242.
Switch to Radio 1. Mouse over the UDP pane of the lower status bar say listening on port 2237.
What am I missing? SeventyThree(s).
|
|
|
|
Sorry, slight correction from me: Changing the UDP port *to 0* for radio 2 puts radio 1 on a random UDP port at start-up
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Darren Collins (G0TSM)
Sent: 22 November 2022 14:34 To: hamlogger@groups.io Subject: [hamlogger] Logger32 starts up on Radio 2 UDP port
Hello DX Friends. I’m running 4.0.298 with two radios and JTDX. Radio 1 uses UDP port 2237 Radio 2 uses UDP port 2242
On start-up Logger32 opens on Radio 1 (CAT working fine) but uses the UDP port for radio 2. I have to manually select radio 2 then go back to radio 1 for it to select the correct UDP port.
WSJT UDP Port=2237 WSJT UDP Port 2=2242
Radio To Use=1 Auto Radio Change=0
Changing Auto Radio Change to 1 does not make any difference. Changing the UDP port for radio 2 puts radio 1 on a random UDP port at start-up.
Could anyone offer any advice on how to diagnose this issue?
Thank You and 73, Darren G0TSM
|
|
|
|
Hello DX Friends. I’m running 4.0.298 with two radios and JTDX. Radio 1 uses UDP port 2237 Radio 2 uses UDP port 2242
On start-up Logger32 opens on Radio 1 (CAT working fine) but uses the UDP port for radio 2. I have to manually select radio 2 then go back to radio 1 for it to select the correct UDP port.
WSJT UDP Port=2237 WSJT UDP Port 2=2242
Radio To Use=1 Auto Radio Change=0
Changing Auto Radio Change to 1 does not make any difference. Changing the UDP port for radio 2 puts radio 1 on a random UDP port at start-up.
Could anyone offer any advice on how to diagnose this issue?
Thank You and 73, Darren G0TSM
|
|
|
.png)