RTTY
[Top] [All Lists]

Re: [RTTY] If you care about CW and RTTY - time is of the essence

To: "rtty@contesting.com" <rtty@contesting.com>
Subject: Re: [RTTY] If you care about CW and RTTY - time is of the essence
From: Michael Adams <mda@n1en.org>
Date: Mon, 8 Aug 2016 18:36:14 +0000
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
While there's no doubt that fast data would help Winlink, there are at least 
two other groups that perceive a benefit:

1.  Emcomm folks chimed in during the initial comment period on 
interoperability grounds.  For example, MARS now almost exclusively uses an 
older MIL-STD mode that is 2.8kHz wide and works very well at speeds faster 
than US amateurs are authorized for; the change is partly for performance 
reasons, and partly because the mode is copyable on "green radios" unlike most 
amateur modes.

2. Don't I remember seeing a couple of mode variations in fldigi that aren't 
legal on HF in the US due to symbol rate issues?  I can see some folks getting 
excited about experimenting with fast, narrow data...and I think one or two of 
them chimed in during the first comment period.

-- 
Michael Adams | mda@n1en.org

-----Original Message-----
From: RTTY [mailto:rtty-bounces@contesting.com] On Behalf Of Jeff AC0C
Sent: Monday, 8 August, 2016 12:38
To: RTTY@contesting.com
Subject: Re: [RTTY] If you care about CW and RTTY - time is of the essence

Maybe it's my paranoia or imagination, but it seems to me that guys supporting 
11708 are generally very careful to avoid saying "it would be a huge boom for 
email-via-HF!"

The fact is the R&D for weak signal or low power work is all narrow band. 
The drivers for something wider outside of the voice segment seems only to be 
Pactor-4 and it's hand-in-hand use as a higher speed enabler to more 
email-via-HF on the bands.

73/jeff/ac0c
www.ac0c.com
alpha-charlie-zero-charlie
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

<Prev in Thread] Current Thread [Next in Thread>