HamApps Support (VK3AMA)
On 14/08/2020 1:20 am, g4wjs wrote:
prior to the latest release JTAlert was not able to interoperate with multiple WSJT-X clients, instead one had to start a JTAlert instance for each WSJT-X client. I am not sure that the latest inclusion of multicast UDP support in JTAlert has changed that position. We will have to wait for confirmation from Laurie, but I suspect you may have to start groups of applications each using a different multicast group address. So for example two WSJT-X instances would look like this:Bill,
Neither is exactly correct. The current JTAlert implementation will transparently support each WSJT-X instance using a unique multicast address (per your first diagram) as well as instances running either common multicast or unicast (with unique port) address.
Your second diagram is closest to the mark, but it shows a single JTAlert instance which will work, but restrict JTAlert to a single WSJT-X instance. There should be an equal number of JTAlert / WSJT-X combinations.
WSJT-X instance #1 -------------+ +-----------> JTAlert instance #1
WSJT-X instance #2 -------------+---> 184.108.40.206 ---+-----------> JTAlert instance #2
WSJT-X instance #3 -------------+ +-----------> JTAlert instance #3
I can't speak for the GridTracker multi-instance requirements
The simplest method is that all WSJT-X instances use a single address/port, JTAlert can handle that configuration now.
FYI, Under-the-hood, JTAlert.exe (the main window) is still stuck in the unicast IP + unique WSJT-X port realm (due to AutoIT limits) but instead of forcing those restrictions on the WSJT-X UDP Server setup, that is applied to the JTAlertV2.Manager.exe process (.NET code) which translates the WSJT-X multicast traffic to the still required unicast traffic. JTAlert talks exclusively to the Manger process with the Manager process handling all the UDP traffic to and from the WSJT-X instances.
de Laurie VK3AMA