Mike, WA3MJZ, The latest version of GridTracker has the ability to forward UDP traffic from wsjtx. However, as Bill as pointed out, the packet flow is one way. I use N3FJP Logging which does support multicast UDP traffic.
A WSJTX related compatibility
question. I’ve been running WSJTX integrated with N1MM for
several years. A friend said I should look at using
GridTracker. I download/installed GridTracker and tried to use
all 3 programs but GridTracker does not receive UDP messages
on port 2237 if N1MM and WSJT are running. I configured a
version of WSJT only with GridTracker and that worked. I
looked on the GridTracker forum and there are some notes on
problems running all three programs. I cannot get their
“solutions” to work. Is it possible for 2 programs to use the
same UDP port? Are these three programs compatible? If anyone
has done this please let me know your configuration.
Mike WA3MJZ
Hi Mike,
I believe that N1MM Logger+ does not support multicast UDP, which
is needed if more than one server is to interoperate with WSJT-X
instances.
JTAlert has a facility to re-send the WSJT-X UDP traffic on a
different port, which you could use to feed N1MM Logger+ but that
is only one-way so N1MM Logger+ would not be able to initiate QSOs
in WSJT-X if you chose that route.
A WSJTX related compatibility question. I’ve been running WSJTX integrated with N1MM for several years. A friend said I should look at using GridTracker. I download/installed GridTracker and tried to use all 3 programs but GridTracker does not receive UDP messages on port 2237 if N1MM and WSJT are running. I configured a version of WSJT only with GridTracker and that worked. I looked on the GridTracker forum and there are some notes on problems running all three programs. I cannot get their “solutions” to work. Is it possible for 2 programs to use the same UDP port? Are these three programs compatible? If anyone has done this please let me know your configuration.
