From: "Øyvind Hanssen" <oyvind@cs.uit.no>
To: linux-hams@vger.kernel.org
Subject: Baycom USCC noise
Date: Wed, 29 Oct 2003 11:50:12 +0100 [thread overview]
Message-ID: <200310291150.12893.oyvind@cs.uit.no> (raw)
We are using a Baycom USCC card with DF9IC modem with
a T7F radio. It works ok, but since the radio is not squelched
there is a high number of rx interrupts and error rx packets.
Also, some bad packets seems to slip through. Much garbage is
seen in the mheard list.
Is this normal? Is there a way to workaround this?
73 de LA7ECA
The sccstat returns (for instance):
speed : 9600 baud
txdelay : 5
persist : 64
slottime : 8
txtail : 8
fulldup : 0
waittime : 2
mintime : 3 sec
maxkeyup : 7 sec
idletime : 3 sec
maxdefer : 120 sec
group : 0x00
txoff : off
softdcd : off
Status:
HDLC Z8530 Interrupts Buffers
-----------------------------------------------------------------------
Sent : 147746 RxOver : 0 RxInts : 30689899 Size : 384
Received : 212184 TxUnder: 0 TxInts : 4982360 NoSpace : 0
RxErrors : 1804229 ExInts : 7823901
TxErrors : 0 SpInts : 1006105
Tx State : busy
next reply other threads:[~2003-10-29 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 10:50 Øyvind Hanssen [this message]
2003-10-29 11:00 ` Re : Baycom USCC noise Jean-Luc Coulon (f5ibh)
2003-10-29 16:56 ` pa3gcu
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=200310291150.12893.oyvind@cs.uit.no \
--to=oyvind@cs.uit.no \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox