From: Gordon JC Pearce <gordonjcp@gjcp.net>
To: Robert Eliassen <robel@vktv.no>
Cc: linux-hams@vger.kernel.org
Subject: RE: two way radio
Date: Thu, 18 Nov 2010 18:54:51 +0000 [thread overview]
Message-ID: <1290106491.21069.6.camel@localhost.localdomain> (raw)
In-Reply-To: <003b01cb873e$a8e96020$fabc2060$@no>
On Thu, 2010-11-18 at 17:35 +0100, Robert Eliassen wrote:
> Eduardo,
>
> You still have to explain what your intentions are. Are you going to use the
> FRS/GMRS-radio to transmit and receive data?
>
> PTT (Push To Talk) would be the trickiest part I guess. You may have to
> modify the unit.
>
> Regards
> Bob, LA6GHA
Most of these wee cheapy radios have a stereo 2.5mm or 3.5mm jack socket
with an earphone pin, a mike pin and ground. To put them into transmit,
you connect a smallish resistor (typically 1k or so) across the electret
mike element. The PTT circuit in the radio looks to see if you've
pulled the mike line down - not totally to ground, but typically to
about 1.5 to 3V - and switches to transmit.
As other posters have said, there may be legal issues with using
unlicensed radios for data comms. If you're controlling a remote PC,
you may also find that you want to encrypt your traffic - except with an
amateur licence you can't. Owing to the legal aspects, I can't
recommend that you use these radios - if you get caught you could be in
quite a lot of legal trouble, assuming your local equivalent of Ofcom
aren't too busy catching pirate FM stations.
Gordon MM0YEQ
next prev parent reply other threads:[~2010-11-18 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 11:07 two way radio Eduardo
2010-11-18 12:15 ` Nate Bargmann
2010-11-18 14:50 ` Eduardo
2010-11-18 16:35 ` Robert Eliassen
2010-11-18 17:31 ` Eduardo
2010-11-18 20:41 ` Robert Eliassen
2010-11-18 18:54 ` Gordon JC Pearce [this message]
2010-11-18 14:15 ` John Goerzen
2010-11-18 16:19 ` Dave Platt
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=1290106491.21069.6.camel@localhost.localdomain \
--to=gordonjcp@gjcp.net \
--cc=linux-hams@vger.kernel.org \
--cc=robel@vktv.no \
/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