Hi Paul, I believe mechanism for the current version of HRD is that JTAlert uses the HRD TCP/IP server API to enter QSOs. That means that the internal logic of HRD to derive fields is used. I also bel

Hi Clovis, you must use multicast UDP if you have multiple servers, I think you mentioned you are using both Gridtracker and JTAlert in which case you are indeed using multiple servers. JTAlert needs

David, if you do not log QSOs in WSJT-X then they will not go to your log.

Hi Charlie, having WSJT-X UDP communications working, but only occasionally, when you are using a unicast server address like 127.0.0.1 is a sign that more than one server is trying to listen for traf

Ron, that's not correct, the "QSO Logged" pop up window is from JTAlert. 73 Bill G4WJS.

Jim, are you using multicast UDP to communicate between WSJT-X an d JTAlert?

OM, I was under the impression that JTAlert was a MS Windows only application, how are you running it on Linux?

Hi Gary, I can speak about how JTAlert and WSJT-X exchange information. WSJT-X instances are configured to send information packets (UDP datagrams) to a specified server application (an IP address or

Thanks Mike!

#FT8

Hi Bill, please pass on the fix so others can find the solution.

#FT8

Hi Bill, make sure that neither WSJT-X nor JTAlert are running with Administrator rights. 73 Bill G4WJS.

#FT8

Hi Bill, have you checked the JTAlert "Menu->Settings->WSJT-X UDP Multicast on Loopback" option?

#FT8

Hi Norman, you can check using Windows Task Manager, go to the "Details" tab, click the Name column heading to sort by name, right-click any column heading and click "Select columns", check the "Eleva

Hi Norman, one way this can happen is if one of WSJT-X and JTAlert is running with Adminstrator rights.

Andrew, nothing unexpected there, the outgoing interfaces and multicast TTL settings are only relevant if the target server is listening on a multicast group address. 127.0.0.1 is a unicast address. 7

Hi Mike, Tom, and Laurie, yes, which is exactly what it does. Tom, have you selected the right band in WSJT-X? The band you set the IF offset for is the one you select. For example you might have -116

#FT8

Hi Monty, you should not be able to set the WSJT-X multicast outgoing interfaces to blank. As JTAlert and WSJT-X must run on the machine you should set the loopback interface as the outgoing interface

Jim, what makes you think memory is being exhausted? Have you eliminated any other processes or system services that might be consuming excessive memory?

#DXLAB #HamSpots #FT8

Jim, you said several things in your OP that seem wrong to me, you have failed to clarify what you are doing and when ask to you reply with unrelated details. Let;s try again with some specific querie

Hi Jim, the secondary ports are not relevant. The two different ports for each WSJT-X instance should be fine so long as no other application is using those ports. In you OP you talked about setting u