[Elecraft] FCC 60m Band Change Rules Published InFederalRegister On 03 February 2012 - Correction

[Sandy]

All correct!  It makes no difference what frequency you use on PSK!  As long 
as the pair of tones are within the 2.8 Khz bandwidth of the "Channel". 
There is a 100 Hz. "guard band at the top and bottom edges of the "Channel" 
therefore the channel is only 2.8 Khz wide.

Sandy W5TVW

-----Original Message----- 
From: Fred Jensen
Sent: Saturday, February 04, 2012 12:48 PM
To: elecraft at mailman.qth.net
Subject: Re: [Elecraft] FCC 60m Band Change Rules Published 
InFederalRegister On 03 February 2012 - Correction

I think we all need to be careful.  In the case of USB, we put our
"suppressed carrier" [i.e. dial reading on a K3] 1.5 KHz below the
authorized center frequency.  The USB energy is above that and fills the
2.8 MHz channel, and it's "one QSO per channel."

For CW, we are told to put our keyed RF signal *on* the channel center
frequency.  There is only one "center frequency" per channel, so again,
it's "one QSO per channel."  CW and USB seem pretty clear.

The two data modes aren't quite as clear.  "Data", as the FCC uses it is
a 2K80J2D emission which wiki.radioreference.com defines as "HF
PACTOR-III."  Again, the emission fills the channel and it's "one QSO
per channel."  The FCC's "RTTY" is a 60H0J2B emission which
radioreference.com defines as PSK31, which precludes what we hams define
as RTTY [45.5 baud 170 Hz shift FSK].

What's not clear is where to place your PSK31 signal.  If your PSK31
signal extends upward from your dial frequency, then the R&O seems to
say you put your dial frequency 1.5 KHz below the channel center
frequency.  Where you actually transmit your PSK31 signal above that
doesn't appear to be specified as long as it isn't 2.8 KHz or more,
which is a little strange.  Given the "one QSO per channel" philosophy
for CW, Phone, and PACTOR-III, I would think that they would want my
PSK31 signal centered in the channel and it would be "one PSK31 QSO per
channel" like the other emissions.  It just doesn't say that explicitly.

There are several references in the R&O to various techniques for
minimizing interference to Federal users, and that seems to be a driving
factor behind the "one QSO per channel" requirement.  If it's just me
and you conversing, there will be natural, frequent breaks for a primary
user to claim the channel.  If the 60H0J2B emission type is intended to
allow multiple QSO's within the channel, as happens now above 14070,
there will be no breaks and no way for a primary user to claim the channel.

I don't have the answer, if someone does I'd really like to hear it, but
do I think we all need to be careful as 5 March rolls around.

73,

Fred K6DGW
- Northern California Contest Club
- CU in the 2012 Cal QSO Party 6-7 Oct 2012
- www.cqp.org

On 2/3/2012 7:14 PM, Rick Bates wrote:
> Hi Sandy,
>
> If I read it correctly, we can use RTTY, Pactor and PSK modes (using USB 
> if
> AFSK) and are limited to 2.8 KHz.  It said we were NOT limited to those
> modes for data as it would suppress experimentation.

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft at mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.1913 / Virus Database: 2112/4788 - Release Date: 02/04/12