Date   

locked Re: Block specific callsign from decoding

Tony Collett
 

A slightly different viewpoint from European side of the pond - I accept duplicate QSO's might be a pain but there might be valid reasons for one (Data modes or contesting in General)

It is just possible that the caller is trying to work you again because the first QSO was not complete in his log. Either miscopied the call/report or plain didn't see your RR73.
Imagine their frustration if you then refuse to acknowledge them - recipe for DQRM??? Other people just like to see how many DXCC/WAS they can work each year I guess?

Apart from working them to get them out of the way, (which may well invite other unwanted calls), I've seen a nice, polite answer to the problem - simply send a free text message "their call" WKD B4

Loses you one period of sending and at least they will know you saw them but won't log them!

I sympathise with the original post re MSK144 though, can be a real problem if stations hog a calling channel like that, especially if they won't use the TX timer......

Keep safe everyone
73
Tony G4NBS


locked Re: Block specific callsign from decoding

careyfisher@...
 

It's not occasional repeat calls. The problem is robots or button pushers that keep calling the same station over and over after making a contact.
73, WB4HXE

On Sat, May 9, 2020 at 7:55 PM Danny Douglas <n7dc@...> wrote:
I'll be some newbies to FT8 are reading these posts. Avoid duplicate FT8 contacts. If I hear an old friend on FT8, and have worked him or her on that band, I won't bother calling again.

On the other hand, if it is indeed a contest, and you dont have him/her on the band/mode (during the test), it is another counter, for the both of you.  I would enjoy hearing from my friends, in that case. 



N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On May 9, 2020 at 5:47 PM Bill Mader <K8TE.Bill.Mader@...> wrote:

Amen to all those who want to avoid answering repeated calls (dupes as we call them in contesting)!  It is bad behavior and it's often learned by those who don't know any better or don't care.  In the USAF, our second value was "Excellence in all we do." which is why I enjoy contesting.  That's were I find better operators per capita.  It's also why I am not enthused about operating FT8.

If I have you in the log with an FT8 QSO, why on earth would I want to work you again on the same band?  Don't tell me it's to check propagation.  I already did that by having your call print on my screen.  PSKReporter tells me where I'm getting out.

I'll be some newbies to FT8 are reading these posts.  Avoid duplicate FT8 contacts.  If I hear an old friend on FT8, and have worked him or her on that band, I won't bother calling again.  If I want to chat, I'll use a conversational mode, certainly not FT8.  With 45-60% of HF contacts using WSJT-X now, there is plenty of room for the "other" modes for chewing the rag.

73, Bill Mader, K8TE
Duke City Hamfest BoD Vice-Chairman  www.dukecityhamfest.org 18-20 Sep 2020
Secretary and Past President, Albuquerque DX Association
W6H NM Coordinator, Route 66 On-the-Air 12-20 Sep 2020


--
73, Bill, K8TE
W6H NM Coordinator, Route 66 On-the-Air 7-15 Sep 2019
ARRL New Mexico Section Manager
ARRL - The national association for Amateur Radio
Duke City Hamfest BoD  www.dukecityhamfest.org 20-22 Sep 2019
President, Albuquerque DX Association


 



--
Carey Fisher


--
73, Carey, WB4HXE


locked Re: Block specific callsign from decoding

a c <jerseyj2@...>
 

I’ve had the same situation many times. I try to see if they are on JT-Alert and send a message offering to schedule a qso another time but that right now I”m looking for x.

This seems to get them to behave.

Jerry
KB2GCG

On May 9, 2020, at 7:59 PM, Jim Nuytens via groups.io <jim.kj3n@...> wrote:

And that's one thing I will not do. If I'm making a directed call, and you're not my in target area, show some courtesy and don't call.

Just before I typed this response, I was calling for UT when someone from TN started calling me. He didn't even wait to see if I got a response from UT. Called me the instant after my first TX.

If you can't show me a little respect for what I'm trying to do, I feel no obligation to award your rude behavior.


On 5/9/2020 20:59, Jim Shorney wrote:
We call that "encouraging bad behavior".

73

-Jim
NU0C





locked Re: Block specific callsign from decoding

Bob Lewis
 

It's not always intentional. Occasionally, in the heat of the moment I've
clicked on a needed call before I realize that he is calling CQ for a
specific area.

-----Original Message-----
From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Jim Nuytens via
groups.io
Sent: Saturday, May 09, 2020 8:00 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Block specific callsign from decoding

And that's one thing I will not do. If I'm making a directed call, and
you're not my in target area, show some courtesy and don't call.

Just before I typed this response, I was calling for UT when someone from TN
started calling me. He didn't even wait to see if I got a response from UT.
Called me the instant after my first TX.

If you can't show me a little respect for what I'm trying to do, I feel no
obligation to award your rude behavior.


On 5/9/2020 20:59, Jim Shorney wrote:
We call that "encouraging bad behavior".

73

-Jim
NU0C


locked Re: Block specific callsign from decoding

Robert Lorenzini
 

Don't tell anyone.

Making directional CQ's is not very effective. PSKreporter is your friend. It will tell you if
you are being heard in that area and if there are any stations even active there and
if they are hearing you. I have worked states where I found a station monitoring only
and hearing me by making a blind call to that station. It works sometimes.

Bob - wd6dod


locked Re: Block specific callsign from decoding

Jim Brown
 

On 5/9/2020 3:24 PM, K8BL BOB LIDDY wrote:
I can't believe you people being so "offended" by someone calling
you that would take merely a MINUTE to respond and carry on!
Hi Bob,

Not so ridiculous if you're using WSJT-X to work weak signals during a short band opening. For example, double-hop E-skip on 6M, or EU from NorCal on 160M at EU sunrise. Or to work a DXpedition on any band. These are the situations in which I use WSJT-X -- to make QSOs I probably couldn't make another way.

Respecting directional CQs has been good operating practice for as long as I've been a ham (64 years). So has not calling someone who's working someone else, EXCEPT for careful tail-ending. With modes like FT8, it's OK to tail-end by call someone at the end of their QSO if you're not on their frequency or the frequency of the station they're working (for example, when they're sending RRR or RR73). How do you know you're not on the frequency of the station they're working? You listen a lot more than you transmit!

73, Jim K9YC


locked FT8 Logging Problem!

Lance Collister, W7GJ <w7gj@...>
 

I noticed during the 6m sprint today that if I was in the NA Contest mode and I was called by someone who was NOT in the NA Contest mode, the program would not let me log the contact because I did not send a numbered report.

So, in order to be able to log the contacts, I switched OUT of contest mode and was able to log the contacts even when stations called me who WERE in contest mode.

It sure would be nice if the logging would work for both situations! Maybe if it doesn't see a numbered report being sent, it could log how strong the station was on his last transmission or something. It just doesn't seem to want to log the grid square as a report...

GL and VY 73, Lance

--
Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, TX7MB)
P.O. Box 73
Frenchtown, MT 59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11/6m DXCC #815

Interested in 6m EME? Ask me about subscribing to the Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!


locked Re: Block specific callsign from decoding

Jim Nuytens
 

And that's one thing I will not do. If I'm making a directed call, and you're not my in target area, show some courtesy and don't call.

Just before I typed this response, I was calling for UT when someone from TN started calling me. He didn't even wait to see if I got a response from UT. Called me the instant after my first TX.

If you can't show me a little respect for what I'm trying to do, I feel no obligation to award your rude behavior.

On 5/9/2020 20:59, Jim Shorney wrote:
We call that "encouraging bad behavior".

73

-Jim
NU0C


locked Re: Block specific callsign from decoding

Jim Nuytens
 

Happens to me all the time. The curse of being a ham from Delaware. I feel your pain.

On 5/9/2020 21:19, Jim Brown wrote:
Once you've spent more time on the air, you'll understand why. Some folks can be a nuisance, for example, calling you when you're working someone else, or when you're making a directional CQ that's not in your direction. Or locals who call you when the band is open.

73, Jim K9YC


locked Re: Block specific callsign from decoding

Jim Cooper
 

On 9 May 2020 at 18:43, Brad, N8GLS wrote:

would make those that do get decoded
quicker and easier to find.
is there an option to 'not show Worked B4 calls" ??


locked Re: Block specific callsign from decoding

Brad, K8ZM
 

Ha !!

 

Love my Smarty !!  Bet you can’t park perpendicular to the curb and still be inside the lines AND out of traffic…..…WoooHooo !!!  Works great behind Prius’s when they pull up too far, also those small diagonally lined spaces near a driveway……fits perfectly inside the triangle !!  Ok, well, back to the hobby…..

 

Get that 6m pile of aluminum up….you’ll have a blast on 6m, any mode !!

 

Never thought you to be “opinionated”, well, except for those “hands” with prominent finger in salute to certain figures in society…….

 

Ok, guess this topic has been beaten to a sufficient death !!

 

73 de Brad, N8GLS

 

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of K8BL BOB LIDDY
Sent: Saturday, May 9, 2020 7:29 PM
To: wsjtx@groups.io
Subject: Re: [WSJTX] Block specific callsign from decoding

 

Hi Brad - Neighbor, Fellow Club(s) Member....

 

Hornet's nest, for sure. Unfortunately, we are all in a situation where

it's easy to become irritated over things that usually we wouldn't. In

my case, those Smart-Car drivers really frost my peaches!! (HIHI, Brad)

 

I'm not familiar with MSK144 (yet), so whatever happens there would be

a total mystery to me. Soon, I'll have a decent 6M antenna and be sure to

bother you as much as possible. Good Luck with that issue.

 

I've said my piece, so far, on the problems of unwanted callers responding

to directed CQs. That situation WILL happen no matter what and it does

no good to be upset about it.

 

I knew when I voiced my opinion in a "Group" that I would be bombarded

with contrary opinions and some would be quite harsh. But, you probably

know me well enough to know that I am the opinionated type that doesn't

shrink away from challenges. Also, when people have things meant for me

that go to the Group versus a direct message, I always answer the same way.

 

73,    Bob  K8BL

 

P.S. If I'm calling "CQ P5", you BETTER NOT call me, dammitt!!!!!!

 

 

On Saturday, May 9, 2020, 06:43:44 PM EDT, Brad, N8GLS <n8gls@...> wrote:

 

 

Ok, wow, lots of replies and geeze what a hornets nest !!  Hi neighbor Bob !

 

This was just a simple question……….so I guess a little explanation may be needed.  This has nothing to do with anybody answering my CQ’s or calling me in general, I answer any and all calls no matter who or how many times I may have worked them before, it’s what we do, and it is a hobby right ??

 

This has to do with a situation where a station is incessantly calling CQ in 15 sec intervals for 6-8 hrs straight every single day.  Its tolerable on FT8 but intolerable on MSK144.  After hours of general CQ’ing and no answers the tactic changes to attempting to call another station, for 30-40 minutes, when that cq fails (and 90% do), it continues with yet another 30-40 min attempt with a different station, and then another, and another, then right back to general CQ’ing……this is non-stop, continuous, EVERY 15s interval, EVERY single day.   WSJT-X decodes every one, MSK144 could be multiples of 2, 3, 4, or 5 lines per interval, so one ends up with literally hundreds of lines of useless decodes from that single station.

 

I’m NOT looking to run anyone out of Dodge, nor am I looking to educate anyone on operating ethics, nor am I trying to limits one’s right to call CQ for as many times as they wish on any band at any time………I’m merely looking to see if it’s possible to block a specific callsign from being decoded.  This obviously wouldn’t help decode any other signals, but would make those that do get decoded quicker and easier to find.

 

73 de Brad, N8GLS

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of K8BL BOB LIDDY
Sent: Saturday, May 9, 2020 4:45 PM
To: wsjtx@groups.io
Subject: Re: [WSJTX] Block specific callsign from decoding

 

It takes about a minute to work someone on FT8/4. Just work

them and move on. What's the big deal? OMG!!!! Otherwise,

they might just keep calling and clog up the Bandpass for

others. Some folks don't realize you've worked B4 or care. You

have no idea why they'd want to call you, so just work them!!!

(BREAKING NEWS: Ham Radio is a HOBBY!!)

GL/73,    Bob  K8BL

P.S.  Call me any time and for any reason. It's fun making QSOs!

 

 

On Saturday, May 9, 2020, 04:33:04 PM EDT, Dave Garber <ve3wej@...> wrote:

 

 

I would kind of like to know as well, beside blocking the callsign, is not going to block his signal

 

Dave Garber

VE3WEJ / VE3IE

 

 

On Sat, May 9, 2020 at 4:28 PM JP Tucson, AZ <samcat88az@...> wrote:

Jim,

 

Uh, why would you want to?

 

Kinda against the spirit of ham radio... 

73 - John - N7GHZ

 

On Sat, May 9, 2020, 1:03 PM Jim Preston N6VH <N6VH@...> wrote:

 

On 5/9/2020 10:53 AM, Brad, N8GLS wrote:

Is it possible to block a specific callsign from being decoded, I looked in the archives but couldn't find anything.

Thanks,
73 de Brad, N8GLS

Brad,

Are you using JTAlert? If so, you can block individual callsigns there. That won't keep them from displaying in WSJT-X, but least they will be blocked there.

73,

Jim N6VH

 

 


locked Re: Block specific callsign from decoding

K8BL BOB LIDDY <k8bl@...>
 

Jim NU0C,

I believe you were responding to me.

I'm sorry that you don't seem to understand that people WILL call
you no matter WHAT you could be sending as a Directed CQ. I've
been an active Ham since 1961 and have seen just about everything
regarding Ham Radio operating there is to see. There's NOTHING
you can do about someone calling you unexpected/undesired. You
shouldn't let it upset you.

Enjoy Our Hobby.        GL/73,       Bob  K8BL

 

On Saturday, May 9, 2020, 06:46:47 PM EDT, Jim Shorney <jshorney@...> wrote:



So if after reading that and K9YC's reply there is no point in trying to explain further because you don't understand.




On Sat, 9 May 2020 22:05:41 +0000 (UTC)
"K8BL BOB LIDDY" <k8bl@...> wrote:

>  Jim.... I did. So what?     ....  73,  Bob  K8BL
>
>    On Saturday, May 9, 2020, 05:34:56 PM EDT, Jim Shorney <jshorney@...> wrote: 


>
> See reply from G0HDB.
>
> 73
>
> -Jim
> NU0C
>
>
> On Sat, 9 May 2020 21:10:00 +0000 (UTC)
> "K8BL BOB LIDDY" <k8bl@...> wrote:
>
> >  Jim,
> > Who is "we"?  And, what is the "bad behavior"?
> > Educate us.
> > 73,    Bob  K8BL
> >
> >    On Saturday, May 9, 2020, 05:00:04 PM EDT, Jim Shorney <jshorney@...> wrote: 
> > 
> > 
> > We call that "encouraging bad behavior".
> >
> > 73
> >
> > -Jim
> > NU0C
> >
> > On Sat, 9 May 2020 20:45:17 +0000 (UTC)
> > "K8BL BOB LIDDY" <k8bl@...> wrote:
> > 
> > >  It takes about a minute to work someone on FT8/4. Just workthem and move on. What's the big deal?  
> >  


locked Re: Block specific callsign from decoding

Danny Douglas <n7dc@...>
 

I'll be some newbies to FT8 are reading these posts. Avoid duplicate FT8 contacts. If I hear an old friend on FT8, and have worked him or her on that band, I won't bother calling again.

On the other hand, if it is indeed a contest, and you dont have him/her on the band/mode (during the test), it is another counter, for the both of you.  I would enjoy hearing from my friends, in that case. 



N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On May 9, 2020 at 5:47 PM Bill Mader <K8TE.Bill.Mader@...> wrote:

Amen to all those who want to avoid answering repeated calls (dupes as we call them in contesting)!  It is bad behavior and it's often learned by those who don't know any better or don't care.  In the USAF, our second value was "Excellence in all we do." which is why I enjoy contesting.  That's were I find better operators per capita.  It's also why I am not enthused about operating FT8.

If I have you in the log with an FT8 QSO, why on earth would I want to work you again on the same band?  Don't tell me it's to check propagation.  I already did that by having your call print on my screen.  PSKReporter tells me where I'm getting out.

I'll be some newbies to FT8 are reading these posts.  Avoid duplicate FT8 contacts.  If I hear an old friend on FT8, and have worked him or her on that band, I won't bother calling again.  If I want to chat, I'll use a conversational mode, certainly not FT8.  With 45-60% of HF contacts using WSJT-X now, there is plenty of room for the "other" modes for chewing the rag.

73, Bill Mader, K8TE
Duke City Hamfest BoD Vice-Chairman  www.dukecityhamfest.org 18-20 Sep 2020
Secretary and Past President, Albuquerque DX Association
W6H NM Coordinator, Route 66 On-the-Air 12-20 Sep 2020


--
73, Bill, K8TE
W6H NM Coordinator, Route 66 On-the-Air 7-15 Sep 2019
ARRL New Mexico Section Manager
ARRL - The national association for Amateur Radio
Duke City Hamfest BoD  www.dukecityhamfest.org 20-22 Sep 2019
President, Albuquerque DX Association


 


locked Re: FT991A issue with WSJT-X

George Nelson <grn@...>
 

John,

The laptop is only a few years old and has neither as serial port or a VGA port. As I said in my previous post, I am relying on an earth from the USB connection but quite happy to open up the laptop to try a better earth just to see if it solves the problem.

This issue is driving me crazy.

73 George M0MGN


locked Re: WSJT-x (FT8) not working with Commander

Andrew OBrien
 

Relayed  from DXLab
Andy K3UK 



"On the General tab of
Commander Configuration, click on the "Net Serv"
button. In the window that appears, check that the TCP Network Service
is "Listening", and note the port number - it generally should be
52002 (base port + 2).

Now look in WSJT-X Settings, Radio tab, for "Network Server". It
should be "localhost:52002" (or whatever port number you noted above).

73,"

    ~iain / N6ML


locked Re: Block specific callsign from decoding

Bill Mader <K8TE.Bill.Mader@...>
 

Amen to all those who want to avoid answering repeated calls (dupes as we call them in contesting)!  It is bad behavior and it's often learned by those who don't know any better or don't care.  In the USAF, our second value was "Excellence in all we do." which is why I enjoy contesting.  That's were I find better operators per capita.  It's also why I am not enthused about operating FT8.

If I have you in the log with an FT8 QSO, why on earth would I want to work you again on the same band?  Don't tell me it's to check propagation.  I already did that by having your call print on my screen.  PSKReporter tells me where I'm getting out.

I'll be some newbies to FT8 are reading these posts.  Avoid duplicate FT8 contacts.  If I hear an old friend on FT8, and have worked him or her on that band, I won't bother calling again.  If I want to chat, I'll use a conversational mode, certainly not FT8.  With 45-60% of HF contacts using WSJT-X now, there is plenty of room for the "other" modes for chewing the rag.

73, Bill Mader, K8TE
Duke City Hamfest BoD Vice-Chairman www.dukecityhamfest.org 18-20 Sep 2020
Secretary and Past President, Albuquerque DX Association
W6H NM Coordinator, Route 66 On-the-Air 12-20 Sep 2020


--
73, Bill, K8TE
W6H NM Coordinator, Route 66 On-the-Air 7-15 Sep 2019
ARRL New Mexico Section Manager
ARRL - The national association for Amateur Radio
Duke City Hamfest BoD www.dukecityhamfest.org 20-22 Sep 2019
President, Albuquerque DX Association


locked Re: Block specific callsign from decoding

Andrew OBrien
 

This thread will be locked after 1200 UTC May 10.   Have your final say while you can.

Andy K3UK 


locked Re: Block specific callsign from decoding

Jim Shorney
 

Of course you are right, but I was assuming that the OP would know that was in reference to FT8...

73

-Jim
NU0C

On Sun, 10 May 2020 00:21:04 +0100
"Bill Somerville" <g4wjs@...> wrote:

Hi Brad,

you can't notch out an MSK144 signal, they fill the whole width of your
rig's SSB filter.

73
Bill
G4WJS.

On 10/05/2020 00:19, Brad, N8GLS wrote:
Jim,

Not a robot but I hadn't thought of trying to notch him out.

Thanks for that tip !!

73 de Brad, N8GLS

-----Original Message-----
From:WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Jim Shorney
Sent: Saturday, May 9, 2020 7:13 PM
To:WSJTX@groups.io
Subject: Re: [WSJTX] Block specific callsign from decoding


Sounds like a robot station. If you rig has a notch filter you could try notching out his CQ frequency.

73

-Jim
NU0C

On Sat, 9 May 2020 18:43:32 -0400
"Brad, N8GLS"<n8gls@...> wrote:

I’m merely looking to see if it’s possible to block a specific callsign from being decoded.


locked Re: Block specific callsign from decoding

K8BL BOB LIDDY <k8bl@...>
 

Hi Brad - Neighbor, Fellow Club(s) Member....

Hornet's nest, for sure. Unfortunately, we are all in a situation where
it's easy to become irritated over things that usually we wouldn't. In
my case, those Smart-Car drivers really frost my peaches!! (HIHI, Brad)

I'm not familiar with MSK144 (yet), so whatever happens there would be
a total mystery to me. Soon, I'll have a decent 6M antenna and be sure to
bother you as much as possible. Good Luck with that issue.

I've said my piece, so far, on the problems of unwanted callers responding
to directed CQs. That situation WILL happen no matter what and it does
no good to be upset about it.

I knew when I voiced my opinion in a "Group" that I would be bombarded
with contrary opinions and some would be quite harsh. But, you probably
know me well enough to know that I am the opinionated type that doesn't
shrink away from challenges. Also, when people have things meant for me
that go to the Group versus a direct message, I always answer the same way.

73,    Bob  K8BL

P.S. If I'm calling "CQ P5", you BETTER NOT call me, dammitt!!!!!!
 

On Saturday, May 9, 2020, 06:43:44 PM EDT, Brad, N8GLS <n8gls@...> wrote:


Ok, wow, lots of replies and geeze what a hornets nest !!  Hi neighbor Bob !

 

This was just a simple question……….so I guess a little explanation may be needed.  This has nothing to do with anybody answering my CQ’s or calling me in general, I answer any and all calls no matter who or how many times I may have worked them before, it’s what we do, and it is a hobby right ??

 

This has to do with a situation where a station is incessantly calling CQ in 15 sec intervals for 6-8 hrs straight every single day.  Its tolerable on FT8 but intolerable on MSK144.  After hours of general CQ’ing and no answers the tactic changes to attempting to call another station, for 30-40 minutes, when that cq fails (and 90% do), it continues with yet another 30-40 min attempt with a different station, and then another, and another, then right back to general CQ’ing……this is non-stop, continuous, EVERY 15s interval, EVERY single day.   WSJT-X decodes every one, MSK144 could be multiples of 2, 3, 4, or 5 lines per interval, so one ends up with literally hundreds of lines of useless decodes from that single station.

 

I’m NOT looking to run anyone out of Dodge, nor am I looking to educate anyone on operating ethics, nor am I trying to limits one’s right to call CQ for as many times as they wish on any band at any time………I’m merely looking to see if it’s possible to block a specific callsign from being decoded.  This obviously wouldn’t help decode any other signals, but would make those that do get decoded quicker and easier to find.

 

73 de Brad, N8GLS

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of K8BL BOB LIDDY
Sent: Saturday, May 9, 2020 4:45 PM
To: wsjtx@groups.io
Subject: Re: [WSJTX] Block specific callsign from decoding

 

It takes about a minute to work someone on FT8/4. Just work

them and move on. What's the big deal? OMG!!!! Otherwise,

they might just keep calling and clog up the Bandpass for

others. Some folks don't realize you've worked B4 or care. You

have no idea why they'd want to call you, so just work them!!!

(BREAKING NEWS: Ham Radio is a HOBBY!!)

GL/73,    Bob  K8BL

P.S.  Call me any time and for any reason. It's fun making QSOs!

 

 

On Saturday, May 9, 2020, 04:33:04 PM EDT, Dave Garber <ve3wej@...> wrote:

 

 

I would kind of like to know as well, beside blocking the callsign, is not going to block his signal

 

Dave Garber

VE3WEJ / VE3IE

 

 

On Sat, May 9, 2020 at 4:28 PM JP Tucson, AZ <samcat88az@...> wrote:

Jim,

 

Uh, why would you want to?

 

Kinda against the spirit of ham radio... 

73 - John - N7GHZ

 

On Sat, May 9, 2020, 1:03 PM Jim Preston N6VH <N6VH@...> wrote:

 

On 5/9/2020 10:53 AM, Brad, N8GLS wrote:

Is it possible to block a specific callsign from being decoded, I looked in the archives but couldn't find anything.

Thanks,
73 de Brad, N8GLS


Brad,

Are you using JTAlert? If so, you can block individual callsigns there. That won't keep them from displaying in WSJT-X, but least they will be blocked there.

73,

Jim N6VH

 

 


locked Re: Block specific callsign from decoding

Brad, K8ZM
 

Geeze………I’m not thinking, been sheltered in-place for too long !!

 

Thanks Bill !!

 

73 de Brad, N8GLS

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Bill Somerville
Sent: Saturday, May 9, 2020 7:21 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Block specific callsign from decoding

 

Hi Brad,

 

you can't notch out an MSK144 signal, they fill the whole width of your rig's SSB filter.

 

73
Bill
G4WJS.

 

On 10/05/2020 00:19, Brad, N8GLS wrote:

Jim,
 
Not a robot but I hadn't thought of trying to notch him out.
 
Thanks for that tip !!
 
73 de Brad, N8GLS
 
-----Original Message-----
From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Jim Shorney
Sent: Saturday, May 9, 2020 7:13 PM
To: WSJTX@groups.io
Subject: Re: [WSJTX] Block specific callsign from decoding
 
 
Sounds like a robot station. If you rig has a notch filter you could try notching out his CQ frequency.
 
73
 
-Jim
NU0C
 
On Sat, 9 May 2020 18:43:32 -0400
"Brad, N8GLS" <n8gls@...> wrote:
 
I’m merely looking to see if it’s possible to block a specific callsign from being decoded.