QRZ station info lookup going wonky

[n8sqt]

Greetings,

Over the last few days, I noticed a new "issue". The QRZ lookup appears to be doing so about 10 times for each time window of WSJT-X. The actual data transfer between the two programs seems OK (i.e., double-clicking on a WSJT-X CQ line causes the call info to appear in RumLogNG).

Here's a video of what's happening: https://www.icloud.com/iclouddrive/02cR ... 2.58.05_PM

Here are my RumLogNG settings:

and my WSJT-X settings

Nothing out of the ordinary there. At least I don't think so.

I originally had WSJT-X going to the broadcast address, then GridTracker relaying from 2237 to 2238 and RumLogNG listening on 2238. The reason for this is that I also have HamClock running on a Raspberry Pi which needs to listen for the UDP packets as well. I noticed the odd lookup behavior with this configuration so I figured I'd remove HamClock and GridTracker and try the above settings to eliminate as many variables as possible. The recording above is with only the two programs running (WSJT-X and RumLogNG).

Has anyone seen this? Any thoughts on what settings to change?

Thanks!!
Bob N8SQT

[n8sqt]

Forgot to include the versions:
RumLogNG: 5.11.3 (563)
WSJT-X: 2.5.4

[n8sqt]

I attached some Wireshark scans for localhost, broadcast, and multicast settings over on WSJT-X.

Happy New Year!
Bob N8SQT

[DL2RUM]

There is a problem in the latest versions with the WSJT-X integration. An updated version is currently in the Apple review process.

[n8sqt]

Thanks for the update. I'll keep an eye out for the new version.

[n8sqt]

That did the trick! v5.11.4 is clean. Thanks!