From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: ad5oo@arrl.net
Cc: linux-hams@vger.kernel.org, Jim Meehan <jmeehan@vpizza.org>
Subject: Re: YAM/Tekk help
Date: Wed, 23 Nov 2005 14:01:52 +0000 [thread overview]
Message-ID: <20051123140152.GC2699@linux-mips.org> (raw)
In-Reply-To: <4382C162.7090202@onr.com>
On Tue, Nov 22, 2005 at 12:57:38AM -0600, David Rivenburg wrote:
> Only 3-4%? That's actually pretty good. Reliable 9600 baud packet is
> practically nonexistant without using hardware specifically designed for
> 9600 baud baseband fsk. I am not aware of any commercial radio or tnc
> that is. They may *try* to do 9600, and even have modest success with
> it, but they are flawed from the start and cannot be counted on for
> reliable operation.
I've made pretty positive experience with the PR-430 radio (available
through www.wimo.com). They're not cheap but the combination of a TNC
and a radio virtually eleminates the delicate adjustment procedure
otherwise needed for 9k6 and the 12ms RX -> TX and 10ms TX -> RX switching
times means this radio isn't a hazard to the whole network.
Downside - the radio is running a variant of the 6pack protocol that needs
extensive changes to the Linux 6pack driver; while I do have such a
driver it's not yet in the shape for going to kernel.org ...
Ralf
next prev parent reply other threads:[~2005-11-23 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 15:17 YAM/Tekk help Jim Meehan
2005-11-16 16:29 ` Ralf Baechle DL5RB
2005-11-16 16:43 ` Jim Meehan
2005-11-16 17:08 ` Bill Vodall
2005-11-16 17:27 ` Mike Murphree
2005-11-17 3:41 ` Wilson G. Hein
2005-11-22 6:57 ` David Rivenburg
2005-11-22 14:17 ` Mike Murphree
2005-11-22 15:01 ` Chuck Hast
2005-11-23 14:01 ` Ralf Baechle DL5RB [this message]
2005-11-23 15:38 ` Chuck Hast
2005-11-23 15:48 ` Ralf Baechle DL5RB
2005-11-23 18:02 ` Gérard / F6FGZ
2005-11-23 19:03 ` Chuck Hast
2005-11-23 19:05 ` Chuck Hast
2005-11-23 23:11 ` Ralf Baechle DL5RB
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=20051123140152.GC2699@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ad5oo@arrl.net \
--cc=jmeehan@vpizza.org \
--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.