yes that is exactly what I meant. On Mon, Jul 22, 2019 at 10:07 PM John Kludt <[email protected]> wrote:
> Roeland, > > Agree. In the CQWW VHF contest the rules make it clear the signal report > is *not* part of the exchange. Maybe that is your point - can't quite > tell from your email. > > John > > On Mon, Jul 22, 2019 at 10:07 AM Roeland Jansen < > [email protected]> wrote: > >> >> contest stations generally only want valid contacts (according to the >> contest rules) to prevent >> a penalty. That also is a thing. >> >> On Mon, Jul 22, 2019 at 2:31 PM Ryan Tourge <[email protected]> >> wrote: >> >>> A bit prissy to exclude a station that lacks a signal report. You both >>> ack'd each other. obviously the call took place. >>> >>> On Mon, Jul 22, 2019 at 6:53 AM Fred Price <[email protected]> wrote: >>> > >>> > Ed, >>> > >>> > You do know that if you are using LoTW to confirm your QSO's then all >>> that is needed for a valid QSO is: >>> > Exchange of calls >>> > Band >>> > Date >>> > Time +/-30 minutes >>> > >>> > So it makes no difference if your signal report is a SNR or a grid >>> square. However since it is your station it is your choice on how you log. >>> > Have fun n enjoy after all it's not life of death it's just a hobby. >>> > >>> > Fred >>> > N2XK >>> > >>> > On Jul 22, 2019 12:01 AM, Ed Muns <[email protected]> wrote: >>> > >>> > Great tip, Laurie. >>> > >>> > This is a good technique if one can reasonably assume that the >>> majority of >>> > QSO partners sending a signal report will not complete the QSO, or log >>> it, >>> > if the contester only sends a Grid Square. >>> > >>> > IOW, if a contester set to NA VHF Contest mode connects up with a >>> > "non-contester" set to normal mode (Special Activity unchecked), and >>> both >>> > are configured for Auto Seq, then the QSO will complete without any >>> operator >>> > intervention. However, the contester will not have sent a signal >>> report to >>> > the non-contester. That may be an issue, because the non-contester may >>> > continue to send his SNR message, hoping to elicit an SNR in return. >>> Or, he >>> > may not log the contact because he never received an SNR from the >>> contester. >>> > This may not be a problem for the contester, because the non-contester >>> is >>> > unlikely to submit a Cabrillo log, so the contester will avoid a NIL. >>> > >>> > Back to your tip of setting up two instances of WSJT-X, one with NA VHF >>> > Contest mode enabled and one with Special Activity unchecked. This is >>> a >>> > good technique for the contester to get another QSO in the log that >>> > otherwise would not happen, IF the assumption is the majority of >>> "mixed" >>> > QSOs as described above will not complete successfully because the >>> > non-contester is concerned that he didn't receive a signal report. >>> > >>> > The contester has to decide whether to power through the QSO in the NA >>> VHF >>> > Contest mode, or to on-the-fly switch to his "SNR Configuration" that >>> uses >>> > the standard non-contest message sequence and indeed sends an SNR >>> message to >>> > the non-contester. >>> > >>> > Ed W0YK >>> > >>> > -----Original Message----- >>> > From: Laurie, VK3AMA <[email protected]> >>> > Sent: 21 July, 2019 16:04 >>> > To: [email protected] >>> > Subject: Re: [wsjt-devel] Contest confusion >>> > >>> > On 22/07/2019 7:16 am, Jim Brown wrote: >>> > > so I quickly switched out of contest mode to work him. :) >>> > > >>> > > What I WOULD like is to able to do this without going to Settings >>> > > Advanced. All those clicks loses a TX cycle. >>> > > >>> > > 73, Jim K9YC >>> > >>> > Simple and only requires a single mouse click. Setup two configurations >>> > in WSJT-X, one for you desired contest and the other non-contest. Once >>> > setup, it is a single click using the "Configuration" menu to switch >>> > between contest and non-contest. >>> > >>> > de Laurie VK3AMA >>> > >>> > >>> > >>> > _______________________________________________ >>> > 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 >>> > >>> > >>> > _______________________________________________ >>> > 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 >>> >> _______________________________________________ >> 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 >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
