[CQ-Contest] Impact of FT* Modes on DXpeditions

Edward Sawyer EdwardS at sbelectronics.com
Fri Aug 16 08:39:21 EDT 2019

And then there the "inconvient truth" called Fox and Hound mode from the DX side.  Does cueing calls up in a stack on the window count for the language of the DXCC and Contesting rule?  And how about however long it takes to actually "work the station" that you have entered while you are out mowing the lawn.

The ARRL Board needs to be more pragmatic about the rules than the "lawyeresque language" that came out of the July Board Meeting.

Ed  N1UR

-----Original Message-----
From: CQ-Contest [mailto:cq-contest-bounces at contesting.com] On Behalf Of David Gilbert
Sent: Thursday, August 15, 2019 8:41 PM
To: cq-contest at contesting.com
Subject: Re: [CQ-Contest] Impact of FT* Modes on DXpeditions

I was dead wrong.  It looks to me like it is pretty easy to use JTDX in automatic mode, where it automatically calls CQ after your last contact.

Sorry for whatever confusion I added.

Dave   AB7E

On 8/15/2019 7:07 AM, Zack Widup wrote:
> Some of you may have seen the postings elsewhere that ARRL will no 
> longer admit fully automatic QSO's for contest and DXCC credit (CQ's 
> and QSO initiation are fully automatic, with no operator 
> intervention). I am guessing this primarily affects FT8 operation. I 
> have not operated much FT8 but the operation I did was fully 
> automatic. I am guessing there is a way to set it to semi-automatic 
> operation (a real operator initiates each CQ and each QSO) (which is a 
> valid QSO for those awards). And I don't know how how they would tell. But the ruling stands.
> 73, Zack W9SZ

CQ-Contest mailing list
CQ-Contest at contesting.com

More information about the CQ-Contest mailing list