Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: braddock@braddock.com (Braddock)
To: Kevin <lists@gnosysllc.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: VHF/UHF frequency monitoring
Date: Mon, 2 May 2005 19:44:17 -0400	[thread overview]
Message-ID: <20050502234417.GA6281@braddock.com> (raw)
In-Reply-To: <200504281537.09707.lists@gnosysllc.com>

Kevin,

I've had similar interests before I dove into HAM radio...it always
seemed that I should just be able to plug a radio IF into a big-ole
ADC and slup down then entire HF band at once, and have that dream
"TiVo" web site that allows perusal of all morse QSOs across a band
from all day.  That is effectively the dream of many of the GnuRadio
folks.

However, what I needed to do first is just to buy a scanner and get a
no-code HAM license (not at all hard for the technically minded...I
think I studied about 4 hours total for my technician exam) and buy a
handie-talkie.  Then play with the scanner the "old fashioned way" and
get a real feel for the RF spectrum.  I went from there straight to
jacking the scanner into the sound port and tracking APRS GPS signals,
packet, controlling and programming my handie-talkie via the Linux HAM
radio libraries, putting up antennas of various effectiveness...I love
my little Kenwood TH-F6A, probably perfect for you as well.  Then you
can help the GnuRadio/USRP folks, which need all the experienced help
they can get to achieve prime-time usability.

Radio can be a frustrating thing, and GnuRadio/USRP is definitely the
deep deep deep end of the pool right now.  I'm sure GnuRadio won't be
much fun at all if you haven't at least put in some time learning how
to seek out the interesting bits of the spectrum with a simple scanner.

	-braddock

On Thu, Apr 28, 2005 at 03:37:09PM -0400, Kevin wrote:
> Hi List-
> 
> I'm new to the list and have never done any radio frequency surfing with 
> Linux, but I'm a longtime (10 year) Linux enthusiast with a pretty good 
> understanding of the electromagnetic spectrum (no HAM experience although I 
> hope to change that soon) and would like to learn more about this subject and 
> in particular, would like to try and do something akin to what TiVo and 
> MythTV do for TV except with strictly radio on the VHF/UHF part of the 
> spectrum.  I've been reading and noticed a receiver (PCR-1000) and linux 
> software to work with it.  I've also read about GnuRadio and the USRP.  The 
> GnuRadio/USRP route seems like it would offer the greatest long-term 
> flexibility, but I'm not sure if the combination would allow me to do what 
> I'm after in the short term.
> 
> Can anyone offer some suggestions to this linux-ham newbie on the best 
> hardware route to go with initially given my short and long-term goals?
> 
> Thanks.
> 
> -- 
> Kevin
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2005-05-02 23:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 19:37 VHF/UHF frequency monitoring Kevin
2005-05-02 23:44 ` Braddock [this message]
2005-05-03  0:22   ` M Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050502234417.GA6281@braddock.com \
    --to=braddock@braddock.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=lists@gnosysllc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox