Why a dedicated TNC when there's plenty of
computer power available in the system? (There's nothing magic about
the KPC3 and its functionality; there's ample open source software for
Linux to emulate everything it does. The one advantage is that it's a
standalone box that's good for not involving a general purpose
computer, like for the Personal Message Box.)
|
The
Technologic TS-7200 ARM Linux board is, at
least in the ultra-portable version, only on when "net-enabling" the
system or doing other clever things... the Atmel would require quite a
bit of custom code including the AFSK and demodulating stuff. But
I do agree in principle, and would rather
use the open source Linux app for "real packet," but not long term APRS
tracking where the milliamps add up. Although... now that I think
about it, maybe we should
eventually add tracking to the task list for the Atmel chip and eliminate a
dedicated piece of hardware. The RigNexus already has GPS data
and is controlling the radios anyway; it could easily assemble APRS
strings and manage modulators and filters, and we could fire up the Linux board for mail and messaging
apps where more file space is needed. Thanks for the thought-provoking question!
|
What's all this junk in here?
|
I wasn't going to make this a FAQ entry, but it
really is frequently asked... usually by folks who understand the
radios but don't recognize any of the bare circuit boards stuffed in
every nook and cranny around them. Basically, the idea here is to
pull together all the communication tools that I find interesting,
incorporating their various user interfaces into a single "front end"
system that is pleasant to use. Formerly stand-alone products,
like a TNC or speech synthesizer, become components in a larger
system. There is no reason to hold on to bulky old enclosures, so
they typically get reduced to circuit boards, interfaced as needed, and
packaged as densely as possible.
|