The point is that you said you needed a block to prevent the impact of an unwanted caller on your receiver.  You just made that up.

The program was designed to require you to actually be an operator, which is why you have to enable each QSO instead of it being fully robotic.  "Call 1st" is merely a crutch for those of us who may not have the reflexes to select a new caller within the first 2 seconds of the next frame.  I sincerely doubt its primary purpose was to remove all thought process from making QSOs.

In order to achieve such significant weak signal performance certain rigid operating constraints are inherently necessary.  The requirement for locked time windows, predetermined message format, and fixed coding schemes are there to facilitate the weak signal result.  In order to mitigate that rigidity certain "automation" features exist in the application ... such as "Call 1st", "odd/even", and having TX Enable locked to the beginning of a time frame.  I'm pretty sure they weren't put there to remove the need for functioning brain cells.

Dave   AB7E


On 12/3/2019 10:15 AM, Ron WV4P wrote:
If he's not tripping my Call First so I can use the program as it was designed, I don't give a damn what he's doing... Ron, WV4P

On Tue, 3 Dec 2019 at 10:51, Gary McDuffie <mcduf...@ag0n.net <mailto:mcduf...@ag0n.net>> wrote:



    > On Dec 2, 2019, at 19:57, Carey Fisher <careyfis...@gmail.com
    <mailto:careyfis...@gmail.com>> wrote:
    >
    > That's ridiculous. A "block" wouldn't keep a station from
    transmitting, just from being displayed. Can't you just ignore it?

    Exactly.  Blocking your program from showing him won’t do a thing
    about the way his signal affects your receiver or how much
    spectrum is being used.  It only keeps you from seeing him.

    Gary - AG0N

    _______________________________________________
    wsjt-devel mailing list
    wsjt-devel@lists.sourceforge.net
    <mailto:wsjt-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/wsjt-devel



_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to