Log4OM

I created a cluster utility which allows you to curate spots.
Biggest thing is it does a QRZ lookup of the callsigns to ensure they are valid. That eliminates virtually all bad spots.
Allows you to filter CW Skimmer spots based on a minimum dB level.
Dumps spot by default ever 60 seconds at 2 seconds after the minute.
Has a 10 minute spot cache to eliminate duplicates.
You can curate spotters to ignore them or show them as reviewed.
I use this filter for North America since I don't do CW.
spottercont = na and unique > 2 and not skimmer
You connect this utility to the spot server of your choice then set Log4OM to 127.0.0.1:7373
https://github.com/mdblack98/DxClusterUtil

Thanks for your contribution. I'll check this out once I have my station all setup.

73, Jason KD9ZHF

New version with some bug fixes and enhancements
https://www.dropbox.com/scl/fi/7urg1koh ... zprwv&dl=1

Do I need to make a youtube video about this? Or is it intuitive enough?

Time to ask for help. Apologies for the basic question.

All seems to be working fine with the utility.

My challenge is where to enter 127.0.0.1:7373 in Log4OM.

Thanks,

Vince

Connect
Telnet Cluster
Connection tab
Add a new entry
Host = 127.0.0.2
Port = 7373
Save it
Then select it to move it to Active servers

Thanks for the prompt reply.

Is the host 127.0.0.2 or 127.0.0.1?

I'm being overwhelmed with error messages saying: "DXClusterUtil says callsign <real callsign here> does not have a DXCC field in QRZ xml...need to notify the operator!!"

Next question...if I recall there is a limit to the number of queries a free QRZ account can make per day. Does it apply to these DXClusterUtil checks?

This is it for now.

Thanks again, Mike.

Oops -- yes 127.0.0.1

And you do need an XML subscription for the QRZ lookups. But that's what prevents all the bad call signs...at times 100's per day during a contest.

Can I stop the QRZ lookups as I don't have a subscription?

Hmmm...it does not work with 127.0.0.1 but did with 127.0.0.2.

Investigating.

I think the QRZ error messages are causing havoc. I cannot close them fast enough, and if any is open, nothing can be changed.