Locked Strange Port Issue - WSJT-X / Gridtracker #TechnicalHelpQuestion #FT8


Serge VA3SB
 

Hello to the group. FYI I have also posted this message on the Gridtracker group as I am not sure where the issue may be.

I am presently using Gridtracker Version 1.22.1123, WSJT version 2.5.4 and JTAlert version 2.60.2. The software all works fine.
However, when I shut down the software and restart it, In order to get Gridtracker and WSJT to communicate, I am required to change the Port assignment.

My setting in the WSJT Reporting tab are:
UDP Server - 224.0.0.1
UDP Server port number - 2246
Outgoing interfaces - loopback_0
Multicast TTL - 1

My settings in Gridtracker General tab are:
Multicast - Enabled
IP - 224.0.0.1
Port - 2246

Forward UDP Messages NOT Enabled

When I restart the software, I have to go into both WSJT and Gridtracker and change the existing port - I usually alternate between 2246 and 2247.When I change the port the two pieces of software begin to communicate again.

Not quite sure why I have to do this and any guidance / assistance to correct this issue would be greatly appreciated.

73

Serge
VA3SB


Dave Garber <ve3wej@...>
 

keep an eye on which order you start. one of the three may be taking
control of the port, causing the other to faulter??

are you also using a logging program in this mix

Dave Garber
VE3WEJ / VE3IE

On Tue, Dec 13, 2022 at 4:07 PM Serge Bertuzzo <smbertuzzo@...> wrote:

Hello to the group. FYI I have also posted this message on the Gridtracker
group as I am not sure where the issue may be.

I am presently using Gridtracker Version 1.22.1123, WSJT version 2.5.4 and
JTAlert version 2.60.2. The software all works fine.
However, when I shut down the software and restart it, In order to get
Gridtracker and WSJT to communicate, I am required to change the Port
assignment.

My setting in the WSJT Reporting tab are:
UDP Server - 224.0.0.1
UDP Server port number - 2246
Outgoing interfaces - loopback_0
Multicast TTL - 1

My settings in Gridtracker General tab are:
Multicast - Enabled
IP - 224.0.0.1
Port - 2246

Forward UDP Messages NOT Enabled

When I restart the software, I have to go into both WSJT and Gridtracker
and change the existing port - I usually alternate between 2246 and
2247.When I change the port the two pieces of software begin to communicate
again.

Not quite sure why I have to do this and any guidance / assistance to
correct this issue would be greatly appreciated.

73

Serge
VA3SB






Michael Black
 

Make sure you pick all the network inferfaces in the WSJT-X Outgoing interfaces pulldown.I've seen problem particularly when there's a wireless interface too.
Mike W9MDB

On Tuesday, December 13, 2022 at 03:07:00 PM CST, Serge Bertuzzo <smbertuzzo@...> wrote:

Hello to the group. FYI I have also posted this message on the Gridtracker group as I am not sure where the issue may be.

I am presently using Gridtracker Version 1.22.1123, WSJT version 2.5.4 and JTAlert version 2.60.2. The software all works fine.
However, when I shut down the software and restart it, In order to get Gridtracker and WSJT to communicate, I am required to change the Port assignment.

My setting in the  WSJT Reporting tab are:
UDP Server - 224.0.0.1
UDP Server port number  - 2246
Outgoing interfaces - loopback_0
Multicast TTL  - 1

My settings in Gridtracker General tab are:
Multicast - Enabled
IP - 224.0.0.1
Port - 2246

Forward UDP Messages NOT Enabled

When I restart the software, I have to go into both WSJT and Gridtracker and change the existing port - I usually alternate between 2246 and 2247.When I change the port the two pieces of software begin to communicate again.

Not quite sure why I have to do this and any guidance / assistance to correct this issue would be greatly appreciated.

73

Serge
VA3SB


Serge VA3SB
 

Hi Dave. Thank you for your prompt response.
I usually start Gridtracker first followed by WSJT-X and JT Alert. I will change the order with WSJT-X followed by Gridtracker and JTAlert and see if that makes a difference.
Thank you for the suggestion.

Serge
VA3SB


Serge VA3SB
 

Hi Dave. Well you were correct.
It seems if I start WSJT-X followed by JTAlert and then by Gridtracker I do not encounter the port issue.
Such a simple solution. Many thanks.

73

Serge
VA3SB