From: Martin Ewing <martin@aa6e.net>
To: Andrea Borgia <borgia@cs.unibo.it>, linux-hams@vger.kernel.org
Subject: Re: newbie question - hamlib and gMFSK
Date: Sat, 01 May 2004 13:58:33 -0400 [thread overview]
Message-ID: <4093E549.2090001@aa6e.net> (raw)
In-Reply-To: <4093C38B.3040303@cs.unibo.it>
Sorry! I wasn't aware of that option in gMFSK. (It's nice to read the
freq., but not essential.) Hamlib 2.3 apparently doesn't have Orion
support, which is what I need. I took a quick look at the code to see
what to do to add a new rig, but it's not completely trivial. I wonder
if it wouldn't have been possible to implement most of a rig's
personality in a higher-level way -- in table- or rule-driven form.
(Like sendmail -- not! :-)
The hamlib / gMFSK / xlog philosophy looks like a good one, as long as
we are in the "Unix" world. One might wish for a true cross-platform
solution, but that's harder.
Cheers,
Martin
Andrea Borgia wrote:
> Martin Ewing wrote:
>
>
>> 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.
>
>
> Hold it, timeout ;-)
>
> gMFSK does indeed use hamlib to display true frequencies in the
> waterfall display and to send accurate qso data to xlog, that also
> supports hamlib.
>
next prev parent reply other threads:[~2004-05-01 17:58 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 [this message]
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=4093E549.2090001@aa6e.net \
--to=martin@aa6e.net \
--cc=borgia@cs.unibo.it \
--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 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.