Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Jim Kusznir <jkusznir@gmail.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Linux Packet Interface Hardware
Date: Thu, 17 Jun 2010 01:29:13 +0300	[thread overview]
Message-ID: <20100616222913.GO898@mea-ext.zmailer.org> (raw)
In-Reply-To: <AANLkTikS7GnQ4hyLpIEk62IF43pX_NVvl_E1GhNwH9C9@mail.gmail.com>

On Wed, Jun 16, 2010 at 09:16:29AM -0700, Jim Kusznir wrote:
> Thanks everyone, lots of good info!
> 
> A few questions:
> 
> I've seen a few references to 6-pack, and know that its a "special
> firmware" that one would load on the TNCs...But I can't seem to find
> that firmware anywhere.  Does anyone know where I can actually get it,
> and find info about what TNCs it supports?

  http://www.baycom.org/bayweb/tech/tnc/firmware.htm
  http://www.symek.com/g/tnc2firmware.html
  http://www.flexnet.be/main/Firmware.htm

There are some advantages at 6PACK, but they relate to time of real
serial ports, not USB virtual devices that run at 500 or 20 000 times
the speed of 1200 bps packet...

But then we hams tend to prefer running with _old_ hardware instead of
doing something truly smart.  A GMSK modulation and some sort of FEC
coding would be smart, but as it is incompatible with 1960es landline
audio modulation used for 1200 bps packet, such ideas will never gain
any use.

> It seems that for hardware available today, the recommendation for
> infrastructure use is to use a TNC in KISS or 6-pack mode.  I've been
> using one at home in KISS mode for a while, and I've been noticing
> what I think now is the T1 timer problem, and its been causing very
> frustrating and massive reduction in throughput on my local 9k6
> channel, even though my radio and the node are the only two on
> frequency!  I often see my system try and send retransmits before the
> first packet ever even makes it out the radio (but on the other hand,
> I also think my TNC is sitting on packets way too long -- PacComm
> Spirit-2).  I am contemplating replacing the firmware chip with a
> KISS-only or 6-pack firmware chip and see what that does, if I can
> find one for this TNC.

Existing firmwares are available mainly for TAPR TNC2 clones.

I did recently search for source code of KISS firmware - and did find it
from my local archive.  Trying to get it to compile with some modern
Z80 compiler existing on UNIX is entirely different scale of adventure,
and I haven't done that yet completely..

  ftp://ftp.funet.fi/pub/ham/packet/tapr/kissv7.zip

I am trying to get that compiled with sdcc's z80 assembler, but...
there are a number of syntax differences, and available assembler syntax
documentation isn't clearest.. (neither original Z80, nor sdcc-as-z80)

I would like to improve that with two ways:
  - Strict transmission queue timeout of N seconds (10-15 seconds)
  - CRC on KISS frames (SMACK or FLEXNET way)

The first one is needed for avoiding packets to wait too long in Tx queue
waiting for silence on channel and thus tx permit.  The second one is
always a good idea.


> As to new installations, does anyone recommend a 9k6 TNC for a good
> cost/performance metric that can be used with linux effectively?  It
> should be external, as the embedded hardware I'm likely to run it on
> will not have PCI slots, and definitely will NOT have ISA slots.
> 
> I like the ideas about a BPQether USB device; from the description,
> though I gather one has not been made to date?  I'm curious, and I'll
> keep this in mind for a potential CE/EE project here (School of EECS,
> WSU and the W7YH Amateur Radio Club).

One related USB interface issue is that there is no specification for
serial port!  All that exist are proprietary chip vendor specific things.
(Unless something has crept up during last month.)

However there are good abstractions for ethernet-like devices, and
for some reason I didn't like "modem" specifications when I looked
at them a while back -- I think because they don't seem to offer
"packet oriented" interface, whereas "ethernet" does have that.
But I could remember wrong...

> The information on sound modems is well taken; I think I'll limit that
> deployment to end-user stations in my planning.
> 
> Thanks all for the ideas/input.  I think the BPQether driver best fits
> what I was hoping to find, except for the fact that it doesn't exist
> off-the-shelf yet....

Not even off-the-lab...
To be seen if I have time for the project this summer - an NXP LPC2368
with USB device interface, and a couple CML MX164 modems..
I made the hardware last summer, but didn't have time for the software.

> --Jim

73 de Matti, OH2MQK

  parent reply	other threads:[~2010-06-16 22:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 23:43 Linux Packet Interface Hardware Jim Kusznir
2010-06-16  1:19 ` Ray Wells
2010-06-16  1:24 ` Matti Aarnio
2011-02-15 18:36   ` Jim Kusznir
2010-06-16  2:05 ` Dave Platt
2010-06-16 12:45   ` Curt, WE7U
2010-06-16 16:16     ` Jim Kusznir
2010-06-16 16:46       ` Curt, WE7U
2010-06-16 23:25         ` Jim Kusznir
2010-06-17 12:49           ` Curt, WE7U
2010-06-21  6:17             ` walter harms
2010-06-16 22:29       ` Matti Aarnio [this message]
2010-06-16 23:53         ` Dave Platt
2010-06-16 22:29     ` Dave Platt
2010-06-16 22:49       ` Matti Aarnio
2010-06-16 23:33       ` Curt, WE7U
2010-06-17  0:02         ` Dave Platt
  -- strict thread matches above, loose matches on Subject: below --
2010-06-17  2:24 Andrew Errington

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=20100616222913.GO898@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=jkusznir@gmail.com \
    --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