locked Version 2.16.11 Multicast and Multiple Instances


Santiago Mejia
 

Good morning all. I have a question regarding the new JT Alert version with multicast and running multiple instances of Wsjtx+JTAlert and Grid Tracker. Prior to the newest version, I had 3 separate instances of Wsjtx and JtAlert running fine, along with Grid Tracker and Log4OM as well. All were working fine and communicating smoothly.

However, after upgrading to version 2.16.11 of JtAlert, I don´t seem to be able to get the 3 instances of WSJTX talk with JTAlert, Grid Tracker and Log4OM. I´ve configured the Wsjtx instances to use a muilticast ip and udp port and configured GT and Log4Om to listen to that port but no info is coming thru from 2 of the 3 instances.

Can anyone help?, thanks.
______________
73 de Santiago
HI8SMX
web: www.hi8smx.online 
YouTube: HI8SMX 
Twitter: @hi8smx
Instagram: hi8smx


g4wjs
 

On 13/08/2020 16:07, Santiago Mejia via groups.io wrote:
Good morning all. I have a question regarding the new JT Alert version with multicast and running multiple instances of Wsjtx+JTAlert and Grid Tracker. Prior to the newest version, I had 3 separate instances of Wsjtx and JtAlert running fine, along with Grid Tracker and Log4OM as well. All were working fine and communicating smoothly.

However, after upgrading to version 2.16.11 of JtAlert, I don´t seem to be able to get the 3 instances of WSJTX talk with JTAlert, Grid Tracker and Log4OM. I´ve configured the Wsjtx instances to use a muilticast ip and udp port and configured GT and Log4Om to listen to that port but no info is coming thru from 2 of the 3 instances.

Can anyone help?, thanks.
______________
73 de Santiago
HI8SMX
Hi Santiago,

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:

WSJT-X - instance 1 ----------> 239.255.0.0 -------------> JTAlert instance 1
                                    |
                                     +-----------------> Gridtracker instance 1

WSJT-X - instance 2 ----------> 239.255.0.1 -------------> JTAlert instance 2
                                       |
                                       +-----------------> Gridtracker instance 2

rather than the more straightforward:

WSJT-X instance 1 -------------+                    +-----------> JTAlert
                               |                    |
                               +---> 239.255.0.0 ---+
                               |                    |
WSJT-X instance 2 -------------+                    +-----------> Gridtracker

I do not know if Gridtracker is capable of running two or more instances on the same machine, so the first configuration may not be possible.

73
Bill
G4WJS.



--
73
Bill
G4WJS.


Santiago Mejia
 


I got it working -almost-. I have Wsjtx broadcasting to the same multicast ip and port in the 3 instances and JTAlert is listening fine. On the GT tracker side, callable roster is getting information fine but Lookup Window only works with first instance not the other two. While everything is going fine to Log4OM too, so no problem there.

I guess this is a GT issue, so I will take it to their group and see what I can find.

Santiago
______________
73 de Santiago
HI8SMX
web: www.hi8smx.online 
YouTube: HI8SMX 
Twitter: @hi8smx
Instagram: hi8smx


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:

WSJT-X - instance 1 ----------> 239.255.0.0 -------------> JTAlert instance 1
                                       |
                                       +-----------------> Gridtracker instance 1

WSJT-X - instance 2 ----------> 239.255.0.1 -------------> JTAlert instance 2
                                       |
                                       +-----------------> Gridtracker instance 2

rather than the more straightforward:

WSJT-X instance 1 -------------+ +-----------> JTAlert
                               |                    |
                               +---> 239.255.0.0 ---+
                               |                    |
WSJT-X instance 2 -------------+ +-----------> Gridtracker

I do not know if Gridtracker is capable of running two or more instances on the same machine, so the first configuration may not be possible.

73
Bill
G4WJS.
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.

eg.
WSJT-X instance #1 -------------+ +-----------> JTAlert instance #1
                                |                    |
WSJT-X instance #2 -------------+---> 239.255.0.0 ---+-----------> 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


g4wjs
 

On 13/08/2020 22:13, HamApps Support (VK3AMA) wrote:
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:

WSJT-X - instance 1 ----------> 239.255.0.0 -------------> JTAlert instance 1
                                       |
                                       +-----------------> Gridtracker instance 1

WSJT-X - instance 2 ----------> 239.255.0.1 -------------> JTAlert instance 2
                                       |
                                       +-----------------> Gridtracker instance 2

rather than the more straightforward:

WSJT-X instance 1 -------------+ +-----------> JTAlert
                               |                    |
                               +---> 239.255.0.0 ---+
                               |                    |
WSJT-X instance 2 -------------+ +-----------> Gridtracker

I do not know if Gridtracker is capable of running two or more instances on the same machine, so the first configuration may not be possible.

73
Bill
G4WJS.

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.

eg.
WSJT-X instance #1 -------------+ +-----------> JTAlert instance #1
                                |                    |
WSJT-X instance #2 -------------+---> 239.255.0.0 ---+-----------> 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

Hi Laurie,

thanks for that info. Shame you have to jump through so many hoops to get it all working but what you have at least looks like the way the WSJT-X UDP Message Protocol was intended to work, from the outside. Well done for getting it up and running.

73
Bill
G4WJS.


--
73
Bill
G4WJS.


Santiago Mejia
 


This issue was solved. Everything is working fine with Wsjtx, JTAlert and Gridtracker. The issue of Lookup Window only working with 1st instance is a GT issue and Tag will be looking at it in future releases. 

Today's fixed of UDP Rebroadcast has allowed me to also incorporate FRLogger (A logger for Flex Radios) into the mix. No I can have Wsjtx (3 instances), JTAlert (3 instancies), GridTracker, Log4Om and FRLogger running at the same time.

Thanks Laurie.

Santiago
______________
73 de Santiago
HI8SMX
web: www.hi8smx.online 
YouTube: HI8SMX 
Twitter: @hi8smx
Instagram: hi8smx