Multiple UDP Listeners at once?

Feature Requests
1

It would be a meaningful improvement if I could have multiple UDP listeners turned on at the same time in WRL CAT Control & Integrations (and eventually the Desktop app when the feature moves over).

I am not using multiple applications simultaneously in ways that could presumably cause too much info to fly at the WRL CC&I app at once, I’m just tired of forgetting to switch between my WSJTX listener getting data from GridTracker, my N1MM listener getting data from POTACAT, and my N3FJP listener getting data from fldigi by way of N3FJP when I change between activities. If I could have them all on at once, I could Set It And Forget It ™.

6 Likes
2

Haha @W9TEF thanks for the detailed note. I know @K4AZE is also passionate about this, and I think he might be actively working with another developer on it too.

I think this is very important.

2 Likes
3

@N0WRL @W9TEF Yes this is on the feature request list :wink:

4

Hi ,

I have been testing WRL CAT Control with a more complex FT8 station and would like to share my findings.

My setup:

  • WSJT-X Improved 3.1.0

  • Logger32 (master log)

  • Wait & Pounce

  • GridTracker v2.260705.2

  • WRL CAT Control v1.1.5

  • HamLog V2.0.1

What works

If I run only:

WSJT-X → WRL CAT Control

using localhost (127.0.0.1:2237), every logged FT8 QSO immediately appears in WRL.

What does not work

When I introduce GridTracker as described in the documentation:

WSJT-X → GridTracker → WRL

I have verified the following:

  • GridTracker receives WSJT-X correctly.

  • GridTracker reports “Logged to HRD Logbook”.

  • HRD Logbook output is enabled.

  • UDP forwarding is enabled.

  • Wireshark confirms that GridTracker actually transmits UDP packets on the configured forwarding port.

  • WRL CAT Control is listening on that UDP port (verified with netstat).

  • Despite this, WRL never imports the QSO.

I also tested:

  • different UDP ports (2238, 2240)

  • multicast and localhost forwarding

  • N1MM output

  • different startup orders

with identical results.

My conclusion is that the problem does not appear to be UDP transport itself, since the packets are visible in Wireshark. It looks more like WRL CAT Control does not recognize or process the packets generated by the current GridTracker HRD/N1MM forwarding.

Has anyone successfully used the current GridTracker (v2.260705.2) together with WRL CAT Control 1.1.5?

I’d be happy to perform additional tests if that helps identify the incompatibility.

73,
ON7NQ Danny

5

@ON7NQ Hey Danny,

It works. I use it in this configuration daily. Its just a configuration issue. The way it works is rig control is handle via the WRL integrations app. WSTJX uses rig control via the WRL integrations app. When you log a contact in WSJTX (or JTDX) it sends the QSO data to Gridtracker and gridtracker will then forward the QSO broadcast data to WRL (and any other app you have setup to forward to).

Here is a screen recording I did for another user on how to set this up. In this example its not only sending to WRL but its also sending to N1MM. if you aren’t using N1MM just dont setup the N1MM settings in Gridtracker.

If you want to send to HRD instead of N1MM you’ll need to set the UDP port for WRL up in the Logging Settings Tab of Gridtrack under “ADIF UDP /N1MM” instead of the “HRD Logbook” section which i am using in the video and then set the correct port you are using in HRD for the “HRD Logbook” section.

Multicast is not setup and working in the integrations app currently but we will be adding it as well as multiple UDP listeners simultaneously in the future.

Let me know if you have any trouble.

Thanks & 73
Brad K4AZE

6

Hi Brad,

First of all, thanks for publishing the UDP Splitter solution. It looks like a very elegant approach.

I’ve been debugging a fairly complex WSJT-X Improved setup with:

  • Logger32

  • Wait & Pounce

  • GridTracker

  • Hamlog.Agent

  • WRL CAT Control

After several days of testing with Wireshark and netstat I found that every individual component works, but the combination GridTracker → WRL CAT Control does not reliably deliver logged QSOs in my setup, even though GridTracker reports “Logged to HRD Logbook” and UDP packets are visible leaving the PC.

Your splitter approach looks like it avoids this entire class of problems.

Before I reinvent the wheel, I have one question:

Does your UDP Splitter forward all WSJT-X message types, including the Logged ADIF messages, or only the normal WSJT-X status/decode packets?

If it forwards the complete WSJT-X protocol, I think this may be the ideal solution for my station.

73,
ON7NQ Danny

7

@ON7NQ Its just sending the QSO broadcast data from wsjtx to gridtracker then to WRL. its not sending the status/encode/decode packets.