On 1 Dec 2019 at 12:56, Gary McDuffie wrote: > > On Nov 30, 2019, at 15:15, Black Michael via wsjt-devel > > <wsjt-devel@lists.sourceforge.net> wrote: > > > > What is needed is the ability to block a callsign for an adjustable time > > out period defaulting perhaps to 15 minutes. > > I´m curious why you use Call 1st anyway. I never use it and have > never found a use for it. I want to have control over who I answer or > call.
You've absolutely hit the nail on the head, Gary - anyone who is troubled by their system replying to 'unwanted' callers simply needs to disable 'Call 1st' and then use a bit of skill and experience to decide which caller to respond to. That's how it's always been done when using the 'legacy' modes of CW, SSB and RTTY and there's no obvious reason why a different, de-skilled modus operandi should be adopted for the JT/FT modes. Although I do call CQ on a fairly regular basis I (almost) always prefer to leave 'Call 1st' unchecked which puts the onus on me to double-click on whichever callsign I decide I want to work in preference to others that appear in the list of decodes addressed to my callsign. I never, ever feel obliged to have a QSO with a caller just because they've called me - I decide who I want to have the QSO with, and I regularly ignore persistent callers that I'm not interested in working! As for it taking maybe a couple of seconds to decide which callsign from the list of decodes to work, that isn't usually an issue because the software at the distant end is generally quite capable of getting a good decode from my transmission even if it's started a bit late in the 15sec timeslot. However, there can be occasions when a retry is needed, but again that's no different to operating using the 'legacy' modes. With regard to stations not sending their Tx3 message in response to a 'DX' station's (eg. the KL7 mentioned by the OP) Tx2, there can be numerous reasons (eg. QSB, QRM, QRN, etc etc) why the Tx2 message might not have been received by the caller - there's no way of knowing what the factors are so I'd suggest that if the 'DX' station hasn't received the caller's Tx3 message after say three or four retries then it's time to move on and try to complete a QSO with another caller. This is after all what DX stations have done for decades when working CW, SSB and RTTY pileups; all it needs is the operator of the 'DX' station to use their skill and experience and not rely too heavily on the automation facilities that the WSJT-X software provides. In summary, I don't see any need whatsoever for any modification of the 'Call 1st' capability to include any forms of queuing or callsign lockout - IMO they would be entirely superfluous and unnecessary. If a 'DX' station wants to have some form of queuing incoming callers then perhaps they should use the DXpedition Fox & Hounds mode. --- Martin, G0HDB _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
