12-03-2021, 09:44 AM
Hi,
it might only be me but I have WSJT-X running across multiple computers at home, two instances doing WSPR on 50 and 144 on a Raspberry PI4, a PC connected to a Elad FMduo so I can use the multiple RX slices to look at the differing modes, JT65, Q65 & FT8 across 50 MHz. It had become tiresome to connect to each device over VNC to check their health and what was being heard. WSJT-X and other programs using the same base code, have the feature in there to do UDP broadcasts of their status.
Okay PJ you have dribbled on long enough, get to the point.... Included with every build of WSJT-X is a companion program called "message_aggregator.exe" which can be found in the main 'bin' folder.
If you run this a new main window will open and if it detects any broadcast UDP messages on the PC's loopback interface it will start to display the activity of the copy of WSJT-X or JTDX and maybe MSHV (not sure if this one does UDP broadcasts though)
Now for this to work, yes there is always a catch, you MUST have ticked the option on the "Reporting" tab that is in the section called "Network Services" see example below.
[attachment=416]
So now we have stage one working... all copies of WSJT-X on this PC will appear in the message-Aggregator display.
Stage 2. Across all my computers.
We need to change the UDP server value in each copy of WSJT-X to now make it broadcast to the wider home network... so instead of the default 127.0.0.1 as the UDP server value, that needs to be set to: 224.0.0.0 Save this setting by clicking OK and the settings menus will close... now we need to open it again and go to reporting, there will now be more options displayed to us to select, one of these is called "Outgoing interfaces" there should be an option called loopback_1 and another with a name that relates to your network port on the computer, mine is Ethernet If you tick the "Ethernet" option then the UDP will broadcast to the wider network
More to come.....
Here is more just for you
, it had occurred to be as my shack is some 50 metres away from the house, why don't I run the message aggregator on the PC in the house and really annoy the XYL?
So I have... and here is a screen shot of the house PC monitor all my instances of WSJT-X
[attachment=417]
The only annoying thing is that the message-aggregator program does NOT remember its settings, so I have to enter the UDP address each time..
I know this may not be useful to a lot of people but I suspect there are a few like me that have more than one PC running doing HAM related duties
Regards,
Peter, vk5pj
it might only be me but I have WSJT-X running across multiple computers at home, two instances doing WSPR on 50 and 144 on a Raspberry PI4, a PC connected to a Elad FMduo so I can use the multiple RX slices to look at the differing modes, JT65, Q65 & FT8 across 50 MHz. It had become tiresome to connect to each device over VNC to check their health and what was being heard. WSJT-X and other programs using the same base code, have the feature in there to do UDP broadcasts of their status.
Okay PJ you have dribbled on long enough, get to the point.... Included with every build of WSJT-X is a companion program called "message_aggregator.exe" which can be found in the main 'bin' folder.
If you run this a new main window will open and if it detects any broadcast UDP messages on the PC's loopback interface it will start to display the activity of the copy of WSJT-X or JTDX and maybe MSHV (not sure if this one does UDP broadcasts though)
Now for this to work, yes there is always a catch, you MUST have ticked the option on the "Reporting" tab that is in the section called "Network Services" see example below.
[attachment=416]
So now we have stage one working... all copies of WSJT-X on this PC will appear in the message-Aggregator display.
Stage 2. Across all my computers.
We need to change the UDP server value in each copy of WSJT-X to now make it broadcast to the wider home network... so instead of the default 127.0.0.1 as the UDP server value, that needs to be set to: 224.0.0.0 Save this setting by clicking OK and the settings menus will close... now we need to open it again and go to reporting, there will now be more options displayed to us to select, one of these is called "Outgoing interfaces" there should be an option called loopback_1 and another with a name that relates to your network port on the computer, mine is Ethernet If you tick the "Ethernet" option then the UDP will broadcast to the wider network
More to come.....
Here is more just for you
, it had occurred to be as my shack is some 50 metres away from the house, why don't I run the message aggregator on the PC in the house and really annoy the XYL?So I have... and here is a screen shot of the house PC monitor all my instances of WSJT-X
[attachment=417]
The only annoying thing is that the message-aggregator program does NOT remember its settings, so I have to enter the UDP address each time..
I know this may not be useful to a lot of people but I suspect there are a few like me that have more than one PC running doing HAM related duties
Regards,
Peter, vk5pj