Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Nate Bargmann <n0nb@n0nb.us>
To: linux-hams@vger.kernel.org
Subject: Re: gMFSK ?
Date: Wed, 9 Jul 2008 06:05:58 -0500	[thread overview]
Message-ID: <20080709110558.GA4283@n0nb.us> (raw)
In-Reply-To: <48749367.8070701@mail.tele.dk>

* Erik Jakobsen <erik_ja@mail.tele.dk> [2008 Jul 09 05:33 -0500]:
> Erik Jakobsen wrote:
>
> Hi again..
>
> I installed fldigi and hamlib again, but used the cat from fldigi:
>
> It tells me there's no .xml file in the directory, and this is not correct:
>
> ~/.fldigi> fldigi
> No rig.xml file present
> erikja@erikja:~/.fldigi> ls -l *.xml
> -rw-r--r-- 1 erikja users 3827 2008-07-09 12:27 fldigi_def.xml
> -rw-r--r-- 1 erikja users 4491 2008-07-09 12:27 TS-570.xml
>
> What say ?

Please go to http://groups.yahoo.com/group/linuxham/ and sign up for
that mailing list which is the support list for Fldigi.  There are many
knowledgable members on that list including the Fldigi developers. 
They can really help you.

As one of the Hamlib developers, I'm puzzled why you're having a
problem.  As Dave wrote, it could be an obscure setting.  Looking at
the CVS source for the ts570.c I see that post_write_delay = 30 by
default.  Since I work with Yaseu code, I'm not much help here either.

Sometimes these things can be maddening as a lot of pieces must work
together perfectly.  Don't give up and do just the linuxham group.

HTH,

73, de Nate >>

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://n0nb.us/index.html

  reply	other threads:[~2008-07-09 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 19:55 gMFSK ? Erik Jakobsen
2008-07-08 21:34 ` Nate Bargmann
2008-07-09  5:40   ` Erik Jakobsen
2008-07-09  6:07     ` Dave Platt
2008-07-09  6:38       ` Erik Jakobsen
2008-07-09 10:31         ` Erik Jakobsen
2008-07-09 11:05           ` Nate Bargmann [this message]
2008-07-09 14:37             ` Erik Jakobsen

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=20080709110558.GA4283@n0nb.us \
    --to=n0nb@n0nb.us \
    --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