logo
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Blocking specific callsigns from Spot Log
Options View
Previous Topic Next Topic
N5XZ
#1 Posted : Friday, August 22, 2025 5:30:19 PM(UTC)
Rank: Advanced Member

Groups: Registered, Beta Testers
Posts: 433
Location: Richmond, TX

Thanks: 40 times
Was thanked: 65 time(s) in 60 post(s)
How can I block or ignore specific callsigns? Some guys just spot too often...
73, Allen N5XZ
Back to top
Sponsor
Note: We receive a commission from Amazon when you purchase via this link. It does not affect your cost. Thank you!
Back to top  
W5GA
#2 Posted : Saturday, August 23, 2025 10:33:12 AM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 436
Location: Missouri

Thanks: 85 times
Was thanked: 142 time(s) in 127 post(s)
Allen, VE7CC user software allow you to reject spots by spotter callsign.

73 Doug W5GA
Back to top
1 user thanked W5GA for this useful post.
WN4AZY on 8/24/2025(UTC)
wa4pgm
#3 Posted : Saturday, August 23, 2025 3:05:54 PM(UTC)
kchavis

Rank: Advanced Member

Groups: Administrators, Registered, Beta Testers
Posts: 386
Man
Location: Farmville, VA

Thanks: 39 times
Was thanked: 235 time(s) in 203 post(s)
If you don't use VE7CC.

Here are the steps for blocking a specific user or callsign from appearing on your DX cluster feed:

Identify the cluster software: you are using.
Enter the blocking command: in your Telnet or cluster interface.

For DXSpider: set/badspotter <callsign> or reject/spots by <callsign>
For AR Cluster: set/filter dxkeyword/reject <callsign>
For CC Cluster: set/filter keyword/reject <callsign>

73 Kyle
Back to top
2 users thanked wa4pgm for this useful post.
N5XZ on 8/23/2025(UTC), WN4AZY on 8/24/2025(UTC)
N5XZ
#4 Posted : Saturday, August 23, 2025 4:08:28 PM(UTC)
Rank: Advanced Member

Groups: Registered, Beta Testers
Posts: 433
Location: Richmond, TX

Thanks: 40 times
Was thanked: 65 time(s) in 60 post(s)
Thanks, Kyle. I'll try that...
73, Allen N5XZ
Back to top
WN4AZY
#5 Posted : Sunday, August 24, 2025 8:14:53 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,164
Man
Location: Auburn, GA

Thanks: 1063 times
Was thanked: 517 time(s) in 431 post(s)
I think Doug/Kyle's solution is the cleanest. To do it in LOGic, set the Prefilter in the options tab of the spot log:

SPOTBYCONT=GLOBAL.MY_CONTINENT AND SPOTBY<>"WN4AZY" AND SPOTBY<>"N6MRQ"

The problem that you might run into is that there is a limit to the size of the filter, and hence the number of calls you can reject.
Back to top
WWW
 |  Edit by user
N5XZ
#6 Posted : Monday, August 25, 2025 9:37:59 AM(UTC)
Rank: Advanced Member

Groups: Registered, Beta Testers
Posts: 433
Location: Richmond, TX

Thanks: 40 times
Was thanked: 65 time(s) in 60 post(s)
Originally Posted by: WN4AZY Go to Quoted Post
I think Doug/Kyle's solution is the cleanest. To do it in LOGic, set the Prefilter in the options tab of the spot log:

SPOTBYCONT=GLOBAL.MY_CONTINENT AND SPOTBY<>"WN4AZY" AND SPOTBY<>"N6MRQ"

The problem that you might run into is that there is a limit to the size of the filter, and hence the number of calls you can reject.


Thanks, Dennis. I tried your way...there's only one call I want to block. BTW, SPOTBY command is actually SPOT_BY. Thanks to everyone, we'll see if it works. This guy was just spotting everything he worked on FT4 which kept coming up as CW on my Mode column...very distracting... I don't feel you need to spot every generic DX contact you make, especially on FT modes
73, Allen N5XZ
Back to top
1 user thanked N5XZ for this useful post.
WN4AZY on 8/28/2025(UTC)
W5GA
#7 Posted : Monday, August 25, 2025 12:52:10 PM(UTC)
Rank: Advanced Member

Groups: Registered
Posts: 436
Location: Missouri

Thanks: 85 times
Was thanked: 142 time(s) in 127 post(s)
I bet your guy has contest mode turned on in whatever software he's using, so that spotting is done automatically. A diplomatic email will probably suffice to fix it.

73 Doug W5GA
73 Doug W5GA
Back to top
1 user thanked W5GA for this useful post.
WN4AZY on 8/28/2025(UTC)
N5XZ
#8 Posted : Tuesday, August 26, 2025 3:25:48 PM(UTC)
Rank: Advanced Member

Groups: Registered, Beta Testers
Posts: 433
Location: Richmond, TX

Thanks: 40 times
Was thanked: 65 time(s) in 60 post(s)
Dennis, I had the following in the Spotlog Prefilter:

SPOTBYCONT=GLOBAL.MY_CONTINENT AND SPOT_BY<>"K4CAE"

It seemed to be working, but today more excessive spots by K4CAE. So I checked the Prefilter and the AND SPOT_BY<>"K4CAE" had been deleted for some reason. When I restoart logic, does it erase the prefilter and load in the default SPOTBYCONT=GLOBAL.MY_CONTINENT ? If so, how do I prevent that?

Thanks,
73, Allen N5XZ
Back to top
WN4AZY
#9 Posted : Thursday, August 28, 2025 3:40:18 AM(UTC)
admin

Rank: Administration

Groups: Administrators, Beta Testers
Posts: 3,164
Man
Location: Auburn, GA

Thanks: 1063 times
Was thanked: 517 time(s) in 431 post(s)
Thanks for the heads-up on SPOTBY vs SPOT_BY.

Not having any problem with LOGic saving the prefilter. I even made a change, and closed LOGic without even tabbing out of the field.

I tried your exact expression, and it saves that too.

Does closing the spot log and reopening it without exiting LOGic lose it? What about going to another tab and back to Options?
Back to top
WWW
Users browsing this topic
Guest (5)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF 1.9.5.5 | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.040 seconds.