Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "David A. Ranch" <dranch@trinnet.net>
To: Linux-Hams <linux-hams@vger.kernel.org>
Subject: Fldigi and RTTY decodes
Date: Sat, 05 Sep 2009 18:01:29 -0700	[thread overview]
Message-ID: <4AA309E9.3040004@trinnet.net> (raw)
In-Reply-To: <4AA2AA78.5000605@radagast.org>

	
Hello Everyone,

I'm a new HAM but not new to Linux.  I've been using Fldigi for
monitoring BPSK31, etc. with good luck but I've been finding that RTTY
rarely works.  It maybe decodes 10% of the time even with a strong
signal.  It also seems the good decodes are specific to a given remote
handle's QSO.

I stumbled upon something today which I bet has a major impact on the
RTTY decoding and I was curious about the group's thoughts.


In researching HF Nets, there is the 3950 Century Club's RTTY NET:

   http://www.3905ccn.com/newsite/netsched.htm

In that URL, it specifies LSB *regardless* of the band and they also
specify specific "mark tones".   In studying for my General ticket, the
current ARRL "General Class License Manual" (section 2-12 & 5-5) mentions:

   - RTTY is usually FSK

   - the ARRL docs *does* mention the existence of AFSK RTTY to use LSB

   - Usual RTTY Mark is at 2125hz and Space at 2295 (170hz diff.)



Now, looking at the Fldigi docs on RTTY, this is where things become
obvious there are issues:

    http://www.w1hkj.com/FldigiHelp/RTTYFSK.html


  - FLdigi's RTTY is "AFSK is not FSK - All of the modem signals that
fldigi produces are audio signals"

  - they mention a Pseudo FSK-RTTY support mode with a external circuit:

   http://www.w1hkj.com/FldigiHelp/PseudoFSK.html

  - "You MUST run the radio is USB to have the correct polarity."  This
conflicts with what the the above Century Net URL and the ARRL docs
specify to use LSB.


So my questions for the net are:

  1. What's more common on the digital bands?  FSK RTTY or AFSK RTTY?
If it's FSK RTTY, are people using TNCs to do RTTY vs. soundcard-based
solutions?

  2. Is there a way to determine if a given RTTY transmission is FSK vs.
AFSK?  I have fairly good ears but maybe it's impossible to hear the
difference with background noise?

  3. Can FLdigi still decode FSK-based RTTY?  Maybe this is only a Tx
limitation?

  4. Maybe Fldigi's RTTY decode (and maybe CW) isn't so hot.  Any
recommendations on alternative Linux packages?  I'd love to hear other
user's thoughts on their favorite Linux apps for HF digital modes (maybe
another email thread).


--David
KI6ZHD

  reply	other threads:[~2009-09-06  1:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31 14:27 AX25 help site Douglas Cole
2009-08-31 22:48 ` Curt, WE7U
2009-09-01  1:06   ` Bob Nielsen
2009-09-01 22:06 ` w8iss
2009-09-01 22:59   ` Dave Platt
2009-09-05  1:32     ` Curt, WE7U
2009-09-05 16:04     ` Matti Aarnio
2009-09-05 18:14       ` Dave Platt
2009-09-06  1:01         ` David A. Ranch [this message]
2009-09-06  2:43           ` Fldigi and RTTY decodes Dave Platt
2009-09-06  3:29             ` David A. Ranch
2009-09-06  4:52               ` Dave Platt
2009-09-05 20:40     ` AX25 help site David Ranch
2009-09-05 22:20       ` Dave Platt
2009-09-05  1:01   ` Curt, WE7U

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=4AA309E9.3040004@trinnet.net \
    --to=dranch@trinnet.net \
    --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