From: M Taylor <mctylr@privacy.nb.ca>
To: linux-hams@vger.kernel.org
Subject: Re: VHF/UHF frequency monitoring
Date: Tue, 3 May 2005 01:22:13 +0100 [thread overview]
Message-ID: <20050503012213.A18202@pull.privacy.nb.ca> (raw)
In-Reply-To: <20050502234417.GA6281@braddock.com>; from braddock@braddock.com on Mon, May 02, 2005 at 07:44:17PM -0400
On Mon, May 02, 2005 at 07:44:17PM -0400, Braddock wrote:
>
> 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
...
> 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.
I want to agree with your ideas, I think it is important that Kevin
take the time to get his (in the US) Technician license as a first step,
because if he wants to "market" (commercially or even just a successful
and popular open source project) his ideas he needs to understand the
ham community (their demographics are funny). I figure most people who
are good at learning can easily past a no-code Tech in a weekend.
The second thing is I thing the GNU/Radio and USRP (or SSRP) are an
excellent choice for a ham interested in experiencing with a truly
affordable, flexible, and powerful Software Defined Radio. However
GNU/Radio and USRP (or other Hardware) are not plug-and-play. They
require some skills and patience of a software tinker (comfortable
compiling and install software with many dependencies under Linux or BSD)
and at least some homebrew skills (can use a soldering iron and build a
simple SMT project for maximium experimentation).
I have USRP with the Basic RX & TX boards and plan on doing some more
experimenting this summer.
Good luck,
prev parent reply other threads:[~2005-05-03 0:22 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
2005-05-03 0:22 ` M Taylor [this message]
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=20050503012213.A18202@pull.privacy.nb.ca \
--to=mctylr@privacy.nb.ca \
--cc=linux-hams@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.