From: Martin Ewing <martin@aa6e.net>
To: n5nw@n5nw.org, linux-hams@vger.kernel.org
Subject: Re: newbie question - hamlib and gMFSK
Date: Sat, 01 May 2004 10:37:19 -0400 [thread overview]
Message-ID: <4093B61F.6090305@aa6e.net> (raw)
In-Reply-To: <1083420366.4194.8.camel@dhcppc3>
Marty,
Hi. I'm relatively new to the ham/linux game myself, but I have a
pretty long experience with hamming and Linux separately.
The general state of Linux stuff for ham radio is primitive, IMO. The
linux-ham group apparently originated to serve the "ham" extensions to
the Linux kernel -- mainly AX.25 -- which are now pretty dated. (The
group will correct me if I'm wrong!) However, this group may be a good
way to reach the "right" kind of folks. You may also have discovered
http://radio.linux.org.au .
Hamlib seems to be an effort to make a device-independent layer between
rigs, with various interfaces, and rig-control software. Coverage is
incomplete, and there don't seem to be many software packages built to
use hamlib.
I have been using KPSK and gMFSK with some success, and also jLog
software (Java). These are all self-contained packages with their own
audio and/or rig interfaces -- no relationship to hamlib.
I have written some Python-based software to operate the PSKmeter device
and for Orion rig control (www.aa6e.net/aa6e), but again no connection
with hamlib.
The reality seems to be that the intersection of Linux and ham radio is
a great place to be if you're a programmer or experimenter, but the vast
ham market share is in the Windows world. It takes a pretty farsighted
developer to put in lots of time to make advanced (user friendly, device
independent, multi-mode) software for Linux when nearly all the
potential users are on Windows. So, we have MixW, MultiPSK, etc. for
Windows and nothing similar AFAIK in Linux.
I wish it were otherwise, and I'm doing my small part.
73, Martin, AA6E
N5NW Marty wrote:
>I have finally successfully installed gMFSK and hamlib, but gMFSK
>doesn't seem to recognize that hamlib exists. No options for
>configuration under preferences.
>
>Hamlib works, as I can use rigctl and query the TS-570DG and get
>frequency and mode.
>
>Any thoughts? I'm trying to move completely away from the Microsoft
>environment in the shack, and this seems like a critical step. I am
>very much the newbie with linux - not much beyond the
>./configure|make|make install stage. I'm using Mandrake 9.2 in a triple
>boot environment (DOS/Win98/Linux).
>
>If there is a more appropriate forum for the question, please advise.
>
>de N5NW (Marty)
>Bellbrook (Dayton), Ohio
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
>
next prev parent reply other threads:[~2004-05-01 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 14:06 newbie question - hamlib and gMFSK N5NW Marty
2004-05-01 14:37 ` Martin Ewing [this message]
2004-05-01 15:34 ` Andrea Borgia
2004-05-01 17:58 ` Martin Ewing
2004-05-03 16:14 ` Curt, WE7U
2004-05-05 15:55 ` Martin Ewing
2004-05-05 16:14 ` newbie question - hamlib and gMFSKX Curt, WE7U
2004-05-05 19:03 ` cross-platform sound (was newbie...) Martin Ewing
2004-05-03 22:56 ` newbie question - hamlib and gMFSK Stephane Fillod
2004-05-01 15:26 ` Andrea Borgia
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=4093B61F.6090305@aa6e.net \
--to=martin@aa6e.net \
--cc=linux-hams@vger.kernel.org \
--cc=n5nw@n5nw.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.