CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] 40M FT4 Frequency

To: Jeff Clarke <ku8e@ku8e.com>, cq-contest@contesting.com
Subject: Re: [CQ-Contest] 40M FT4 Frequency
From: cosson-dimitri <cosson-dimitri@bbox.fr>
Date: Tue, 06 Aug 2019 07:30:06 +0200
List-post: <mailto:cq-contest@contesting.com>
Hi Jeff,
Maybe because there are some other countries than USA in the world... (with 
diferents band plan) 😉
73 de Dimitri F4DSK 


Envoyé depuis mon smartphone Samsung Galaxy.-------- Message d'origine 
--------De : Jeff Clarke <ku8e@ku8e.com> Date : 05/08/2019  22:44  (GMT+01:00) 
À : cq-contest@contesting.com Objet : Re: [CQ-Contest] 40M FT4 Frequency 
Why not move all digital communications (including FT8/FT4) above 7100 ?

Here is the FCC frequency allocation for the lower part of 40 meters the US:

7.025-7.125 MHz : CW, RTTY/Data

The same applies to 20/15/10 meters as well.

14.025 -14.150 MHz CW, RTTY/Data

21.025-21.200 MHz: CW, RTTY/Data

28.000-28.300 MHz: CW, RTTY/Data

I don't think that segments above .100 are used much by anyone in the 
US. I've never understood why the digital mode frequency recommendations 
are in the top part of the CW band to begin with. Maybe one of you 
serious digital guys can explain this reasoning?

Jeff KU8E



On 8/5/2019 10:34 AM, donovanf@starpower.net wrote:
> I fully support K9YC's recommendation that ARRL members contact
> their directors so that they become aware of the need to quickly act
> force a change in the unfortunate choice of 7047.5 kHz for routine
> and rapidly growing FT4 activity.
>
>
> 73
> Frank
> W3LPL
>
> ----- Original Message -----
>
> From: donovanf@starpower.net
> To: "PVRC Mailman" <pvrc@mailman.qth.net>
> Cc: "k1jt" <k1jt@arrl.net>, "W3TOM" <w3tom@arrl.org>, w2ru@arrl.org
> Sent: Monday, August 5, 2019 2:29:13 PM
> Subject: Re: [CQ-Contest] 40M FT4 Frequency
>
>
> What are PVRC members opinions and recommendations about the
> unwise choice of 7047.5 kHz for FT4 activity? While the FT4
> development team naively expected FT4 to be used only during
> contests, inevitably FT4 use is rapidly growing for routine QSOs.
>
>
>
> In my opinion the obvious 40 meter FT4 frequency range is in
> the much more lightly used 7100-7125 kHz segment.
>
>
> Something must be done soon.
>
>
> 73
> Frank
> W3LPL
>
> ----- Original Message -----
>
> From: "Jim Brown" <k9yc@audiosystemsgroup.com>
> To: "cq-contest" <cq-contest@contesting.com>
> Sent: Monday, August 5, 2019 7:57:41 AM
> Subject: [CQ-Contest] 40M FT4 Frequency
>
> 7047 has been chosen, and many fans of WSJT modes have observed that
> it's likely to start a war. That range is widely used by W1AW, state QSO
> parties, QRP and QRS operation, county hunters, most CW contests, and
> many others. Sure, the WSJT team think it's only for contests, but if
> you build it, they will come, and they are coming. I had QRM from FT4
> operators during NAQP CW.
>
> I am a huge fan of the work of K1JT and his team (I use FT8 extensively
> on 160M and 6M), but they ain't perfect, and this is a massive screw-up.
> The default 40M FT4 frequency ought to be somewhere north of 7070 kHz.
> OTOH, I have no issue with the DXpedition mode frequency around 7058. I
> urge all contest clubs to contact both the WSJT team and their ARRL
> representatives about this.
>
> 73, Jim K9YC
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
>
>
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
<Prev in Thread] Current Thread [Next in Thread>