Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Mike Markowski <mm@UDel.Edu>
To: Linux Hams <linux-hams@vger.kernel.org>
Subject: gMFSK/hamlib/parport
Date: Wed, 18 Feb 2004 10:27:45 -0500	[thread overview]
Message-ID: <20040218152745.GD16991@strauss.udel.edu> (raw)

Hi all,

A couple questions about the excellent gMFSK 0.6beta2:

	Feature request:
	- Are there any patches that allow gMFSK to use
	  a parport for PTT?  If not, I'll be glad to look into
	  possibly re-using the parport code from soundmodem-0.7.

	Bug report (but maybe in hamlib):
	- I'm using an ICOM 706 MkIIg with hamlib on ttyS0 and
	  PTT to "none" in gMFSK just for the sake of seeing how
	  gMFSK uses hamlib.  When I rotate the rig's tuning knob,
	  gMFSK works for a bit nicely updating the spectrum freqs,
	  but then I get a "Protocol error" and hamlib is disabled.
	  I assume the data out of the rig is changing too rapidly
	  for hamlib to capture it?  Or maybe gMFSK is trying to
	  reread the data too frequently?

I haven't played around with either yet just in case others are already
aware and working on it.

Oh, and I finally looked at gMFSK's "Help".  You know how it goes, when
all else fails read the manual...  I like how you included so many
URLs in there Tomi.  But I notice under the Usage section, it talks
about opening images and how to scroll them.  :-)  Reused text from
something else I guess?

	Thanks for any info,
	Mike  AB3AP

             reply	other threads:[~2004-02-18 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 15:27 Mike Markowski [this message]
2004-02-18 19:15 ` gMFSK/hamlib/parport Wilbert Knol
2004-02-18 19:42 ` gMFSK/hamlib/parport Stephane Fillod
2004-02-18 20:12 ` gMFSK/hamlib/parport Tomi Manninen
2004-02-19 16:58   ` gMFSK/hamlib/parport Mike Markowski
2004-02-19 17:28     ` gMFSK/hamlib/parport Tomi Manninen
2004-02-18 23:32 ` gMFSK/hamlib/parport Alex V Flinsch

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=20040218152745.GD16991@strauss.udel.edu \
    --to=mm@udel.edu \
    --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