From: Stephane Fillod <f8cfe@free.fr>
To: Martin Ewing <martin@aa6e.net>
Cc: linux-hams@vger.kernel.org
Subject: Re: newbie question - hamlib and gMFSK
Date: Tue, 4 May 2004 00:56:12 +0200 [thread overview]
Message-ID: <20040503225612.GJ1599@charybde.local> (raw)
In-Reply-To: <4093B61F.6090305@aa6e.net>
Hi Martin,
On Sat, May 01, 2004, Martin Ewing wrote:
> 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.
http://hamlib.org/app.html
It's up to you to add more ;-)
> 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.
gMFSK relies on Hamlib. I'd be happy to help authors of KPSK/jLog/..
to integrate with 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.
Next version of Hamlib will have basic support for the Orion rig,
I've just added it in CVS of Hamlib tonight :-)
Do you want to be the maintainer of this backend?
FYI, Hamlib has also a Python wrapper.
73,
Stephane - F8CFE
next prev parent reply other threads:[~2004-05-03 22:56 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
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 ` Stephane Fillod [this message]
2004-05-01 15:26 ` newbie question - hamlib and gMFSK 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=20040503225612.GJ1599@charybde.local \
--to=f8cfe@free.fr \
--cc=linux-hams@vger.kernel.org \
--cc=martin@aa6e.net \
/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