[Elecraft] P3 TX Mon: FEATURE REQUEST - Monitoring of RTTY

Mon Sep 14 15:16:40 EDT 2015

 Waveform
To: elecraft at mailman.qth.net
References: <[email protected]>
From: "Lynn W. Taylor, WB6UUT" <KX3 at ColdRocksHotBrooms.com>
Message-ID: <55F71D19.1020401 at ColdRocksHotBrooms.com>
Date: Mon, 14 Sep 2015 12:16:41 -0700
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <[email protected]>
Content-Type: multipart/alternative;
 boundary="------------060809070606000101030600"

This is a multi-part message in MIME format.
--------------060809070606000101030600
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Interesting to note that none of the waveforms in the article cited are 
the traditional "plus" display.

The plus display comes from taking the mark filter and putting it on the 
"x" axis, and the space filter on "y" and looking at the picture.

Since the mark filter and space filter are in the demodulator, and as 
someone else observed really speak to how closely you're tuned to the 
received signal, that just doesn't seem useful.

The spectrum graphs might be.

73 -- Lynn

On 9/14/2015 11:55 AM, Luis V. Romero wrote:
> However, I can't monitor other issues that can rear their ugly heads in
> RTTY, be it modulated by FSK or AFSK with the existing functionality
> available:  The reason I was looking for a better visual representation of
> these issues in this tool is explained in an excellent article by Andy
> Flowers, K0SM.
>
>   
>
> http://frontiernet.net/~aflowers/k3rtty/k3rtty.html

--------------060809070606000101030600
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Interesting to note that none of the
      waveforms in the article cited are the traditional "plus" display.<br>
      <br>
      The plus display comes from taking the mark filter and putting it
      on the "x" axis, and the space filter on "y" and looking at the
      picture.  <br>
      <br>
      Since the mark filter and space filter are in the demodulator, and
      as someone else observed really speak to how closely you're tuned
      to the received signal, that just doesn't seem useful.<br>
      <br>
      The spectrum graphs might be.<br>
      <br>
      73 -- Lynn<br>
      <br>
      On 9/14/2015 11:55 AM, Luis V. Romero wrote:<br>
    </div>
    <blockquote cite="mid:[email protected]"
      type="cite">
      <pre wrap="">However, I can't monitor other issues that can rear their ugly heads in
RTTY, be it modulated by FSK or AFSK with the existing functionality
available:  The reason I was looking for a better visual representation of
these issues in this tool is explained in an excellent article by Andy
Flowers, K0SM.

<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://frontiernet.net/%7Eaflowers/k3rtty/k3rtty.html">http://frontiernet.net/~aflowers/k3rtty/k3rtty.html</a></pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060809070606000101030600--