meters!
73,
Sandy W5TVW
-Original Message-
From: Rick Bates
Sent: Friday, February 03, 2012 9:14 PM
To: 'Sandy'
Cc: elecraft@mailman.qth.net
Subject: RE: [Elecraft] FCC 60m Band Change Rules Published
InFederalRegister On 03 February 2012 - Correction
Hi Sandy,
If I read
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
?
Thanks es 73, de Jim KG0KP
- Original Message -
From: Fred Jensen k6...@foothill.net
To: elecraft@mailman.qth.net
Sent: Saturday, February 04, 2012 12:48 PM
Subject: Re: [Elecraft] FCC 60m Band Change Rules Published
InFederalRegister On 03 February 2012 - Correction
I think we all need
Sandy wrote:
I am planning on trying CW for the first time on 60 meters on the new
channel 3 on 5358.5. Just hope the PACTOR stuff doesn't jump on that
channel and claim it.
That channel will likely become the favorite 60 meter frequency for the
several military and vintage commercial
I guess the only thing not specified is where the PSK-31 signal shows
up above the carrier frequency. Don't most PSK-31 transmissions use
something around 1000 Hz?
In the discussion part of the Report and Order, the Commission made it
clear that the PSK31 signal *must* be located on the
First off, I'm not a lawyer (and reading it provided a headache) but my
interpretation is:
If USB, select the suppressed carrier on your display (K3).
If CW, go to the CHANNEL CENTER (up 1.5 KHz from suppressed carrier).
If PSK (RTTY) or PACTOR III, set as per USB; the suppressed carrier.
*BUT*
See remarks included below...
-Original Message-
From: Dave New
Sent: Saturday, February 04, 2012 11:55 AM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] FCC 60m Band Change Rules Published
InFederalRegister On 03 February 2012 - Correction
Now I'm really confused. I thought I
Message-
From: Fred Jensen
Sent: Saturday, February 04, 2012 12:48 PM
To: elecraft@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
: Saturday, February 04, 2012 12:48 PM
To: elecraft@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
channels.
73,
Sandy W5TVW
-Original Message-
From: Mike Morrow
Sent: Saturday, February 04, 2012 2:32 PM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] FCC 60m Band Change Rules Published
That channel will likely become the favorite 60 meter frequency for the
several military
W5TVW
-Original Message-
From: Joe Subich, W4TV
Sent: Saturday, February 04, 2012 2:45 PM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] FCC 60m Band Change Rules Published
I guess the only thing not specified is where the PSK-31 signal shows
up above the carrier frequency. Don't
To: Sandy
Cc: k6...@foothill.net ; elecraft@mailman.qth.net
Subject: Re: [Elecraft] FCC 60m Band Change Rules Published
InFederalRegister On 03 February 2012 - Correction
On 2/4/2012 4:52 PM, Sandy wrote:
All correct! It makes no difference what frequency you use on PSK! As
long as the pair of tones
have overlooked it!
73,
Sandy W5TVW
-Original Message- From: Joe Subich, W4TV
Sent: Saturday, February 04, 2012 2:45 PM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] FCC 60m Band Change Rules Published
I guess the only thing not specified is where the PSK-31 signal shows
up
-Original Message-
From: Joe Subich, W4TV
Sent: Saturday, February 04, 2012 4:12 PM
To: Sandy
Cc: k6...@foothill.net ; elecraft@mailman.qth.net
Subject: Re: [Elecraft] FCC 60m Band Change Rules Published
InFederalRegister On 03 February 2012 - Correction
On 2/4/2012 4:52 PM, Sandy wrote
I would believe that the purpose of that requirement is that the primary
user can take over the channel without undue effort - contact one user
and cause that user to cease and desist will get the task done.
73,
Don W3FPR
On 2/4/2012 5:56 PM, Joe Subich, W4TV wrote:
Did you see this indicated
Apologies to those who prefer top-posting- in this case, makes more sense to
respond in line.
Who is the referee determining the channel is empty? Propagation being
what it is, two stations may have QSO's going on and none of the group
, of 4 thinks hears the other pair. Another observer
The new FCC 60 meter band rules that were announced on 18 November 2012
http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1118/FCC-11-171A1.pdf
have finally been published in the Federal Register today, 03 February 2012
] FCC 60m Band Change Rules Published In Federal Register On
03 February 2012
The new FCC 60 meter band rules that were announced on 18 November 2012
http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1118/FCC-11-171A1.pdf
have finally been published in the Federal Register today
I wrote:
The new FCC 60 meter band rules ...
have finally been published in the Federal Register today, 03 February 2012
http://www.gpo.gov/fdsys/pkg/FR-2012-02-03/pdf/2012-2477.pdf
That means they become effective 30 days from today, on 04 March 2012.
The Ordering Clause of the published
Thanks for the update, Mike.
Just so nobody get in trouble, the effective date is March 5, 2012, as
specified in the notice. (I guess they don't know it's a leap year.)
73, Terry N6RY
On 2012-02-03 6:05 AM, Mike Morrow wrote:
The new FCC 60 meter band rules that were announced on 18 November
Did I miss the conversation about how the K3 will handle the rule
changes? Firmware update in the works, anyone, or do we have to
manually program all the weird mode offsets somehow ourselves, using
macros? Makes my head hurt...
73,
-- Dave, N8SBE
On 2/3/2012 2:23 PM, Mike Morrow wrote:
I
Did I miss the conversation about how the K3 will handle the rule
changes? Firmware update in the works, anyone, or do we have to
manually program all the weird mode offsets somehow ourselves, using
macros?
For my non-Elecraft HF rig, I just performed the obvious and simple.
I programmed
It's on my list. I want to be the first one to make a 60-meter CW QSO
anyway :)
73,
Wayne
N6KR
On Feb 3, 2012, at 12:42 PM, Dave New wrote:
Did I miss the conversation about how the K3 will handle the rule
changes? Firmware update in the works, anyone, or do we have to
manually program
Wayne,
Post when you'll be on if you can. You're WELL within my 'local' coverage
area here in the foothills. Lessee, that starts at 4 PM Pacific time on 4
Mar 12 (local date)...
You'll have to tolerate keyboard code, I've never been much on CW otherwise.
Rick wa6nhc
-Original
. bandwidth.
73,
Sandy W5TVW
Wonder if someone would be ready for a 60 meter RF card for the K1?
-Original Message-
From: Wayne Burdick
Sent: Friday, February 03, 2012 5:01 PM
To: Dave New
Cc: elecraft@mailman.qth.net
Subject: Re: [Elecraft] FCC 60m Band Change Rules Published
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.
Since PSK is usually sound card based, keeping everything within the
required 2.8 KHz
, 2012 9:14 PM
To: 'Sandy'
Cc: elecraft@mailman.qth.net
Subject: RE: [Elecraft] FCC 60m Band Change Rules Published
InFederalRegister On 03 February 2012 - Correction
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
27 matches
Mail list logo