You're assuming they are not calling blind. You have no idea if they are
calling blind until you send them TX2 and they don't send you TX3.
This is noticeable all the time on dxpeditions where you will see a dozen
people constantly calling and if you check their spot history (for those that
have PSKReporter or JTAlert running) they've never seen the dx station.
Les hit the problem with a bunch of European stations trying to work him
(Alaska being somewhat rare) and was sending TX2 and never getting replies from
numerous ops.
I think one way to do this is for call first to use a queue and when you work
somebody they go to the bottom of the queue. So until such time as they bubble
up to the top they won't get worked again. Call first would take each call
coming in and check the queue, if not in the queue work it and stick it in the
queue at the bottom. If all decodes are in the queue pop the top one off and
work it. Keep the queue depth to a limit or add time to it to time out entries
after a programmable limit.
Mike
On Saturday, November 30, 2019, 10:17:58 PM CST, Jim Brown
<[email protected]> wrote:
On 11/30/2019 2:15 PM, Black Michael via wsjt-devel wrote:
> who was complaining about operators calling him in the blind. And when
> you have Call First checked the blind callers become a PITA.
Hmmm. If I'm not mistaken, "Call First" would apply to those answering a
CQ. I rarely call CQ, so I don't use that function much. On more than
one occasion, I've been calling EU stations on 160M (I'm near San
Francisco), and some turkey in the next county calls and calls and
calls, why I don't know. But since I have "Auto-Complete" checked but
not "Call First," WSJT-X dutifully ignore the caller, and waits for a
call from the guy I'm calling. This happened a few nights ago when I was
trying to work an island expediton.
Same thing happens on 6M in the middle of a double-hop opening. Again, I
don't call CQ much, but when I do, I usually turn off "Call First" to
avoid those locals, instead trying to be fast to respond to one of the
stations I want to work.
BTW -- I suspect the root cause of the problem is that these callers are
only looking at JTAlert, and haven't learned to recognize when a decode
is not a CQ. :)
73, Jim K9YC
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
