FCC report

Dennis Rosenauer drac7ft at gmail.com
Sat Aug 25 08:16:50 PDT 2012

Ok, this is great.

I know we have some people here who can clarify any legal wording, but
my read on this is that we are limited to a symbol rate of 300 bauds,
and that I have to document publicly the technical characteristics of
the modulation coding etc.

So let's just say I want to run OFDM with 64 carriers.  And for the sake
of not getting too many people out of joint I am going to use 2.4KHz of
bandwidth total.  So each OFDM bin is 37.5 Hz wide and say I BPSK
modulate it and use 1/2 bit/Hz which gives me a 2:1 guard band.  This
should give me 64 * 18.75 = 1200 bits/sec.

So now I publish this on the web and in the DCC.  I consider that public
documentation.  I am running 18.75 bauds/sec, clearly less than 300 and
I am doing 1200 bits/sec.

What would the FCC do?

Of course I can always file for an STA and it would most likely be granted.

Dennis, AC7FT.

On 08/24/12 23:48, Jeremy McDermond wrote:
> On Aug 24, 2012, at 11:03 PM, Dennis Rosenauer <drac7ft at gmail.com> wrote:
>> Let's be technical here for one moment.  Are the FCC rules 300 baud, or
>> 300 bits/sec?  It matters!
> 47 CFR 97.307(f)(3):
> Only a RTTY or data emission using a specified digital code listed in §97.309(a) of this part may be transmitted. The symbol rate must not exceed 300 bauds, or for frequency-shift keying, the frequency shift between mark and space must not exceed 1 kHz.
> The specified codes in §97.309(a) include:
> (4) An amateur station transmitting a RTTY or data emission using a digital code specified in this paragraph may use any technique whose technical characteristics have been documented publicly, such as CLOVER, G-TOR, or PacTOR, for the purpose of facilitating communications.
> --
> Jeremy McDermond NH6Z
> nh6z at nh6z.net
> _______________________________________________
> Seatcp mailing list
> Seatcp at wetnet.net
> http://wetnet.net/mailman/listinfo/seatcp

More information about the Seatcp mailing list