RTTY
[Top] [All Lists]

Re: [RTTY] Lids running RTTY on the JT65 Frequency

To: rtty@contesting.com
Subject: Re: [RTTY] Lids running RTTY on the JT65 Frequency
From: W2GR--- via RTTY <rtty@contesting.com>
Reply-to: W2GR@aol.com
Date: Tue, 6 Jan 2015 22:05:32 -0500
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
I'd like to know how he knows there was such a stomping on other  digi 
sigs. on all the bands?.....Were all the segments he is ranting  about packed 
with JTXX sigs all weekend all the way up to xx.80?.......just  wondering...
 
Mike W2GR
------------------
 
 
In a message dated 1/6/2015 9:45:24 P.M. Eastern Standard Time,  
john@kk9a.com writes:

Why are  you not complaining about CW on these frequencies.  During CQWW CW
the  bands were packed all the way to xx.100.

John  KK9A



To:    Mark n2qt <n2qt.va@gmail.com>, RTTY  <rtty@contesting.com>
Subject:    Re: [RTTY] Lids running  RTTY on the JT65 Frequency
From:    "Joe Subich, W4TV"  <lists@subich.com>
Date:    Mon, 05 Jan 2015 11:13:55  -0500
List-post:     <rtty@contesting.com">mailto:rtty@contesting.com>

> The  other problem is often the JTx guys run SSB type bandwidths

I  understand the SSB type bandwidth/tuning in the waterfall behavior.
However  setting that aside, there were dozens of RTTY signals dead on
top of JT9  and JT65 stations this weekend.  The issue is that RTTY
operators  don't know - or care - about the 48 seconds on/12 seconds
off/2 minute  cycle of JT65/JT9.  If a frequency is vacant for even a
second some  RTTY operator will press F1 there.

The only real solution is score  reductions for those who transmit
(particularly those who run) below  xx.0805 mark - particularly on
80/20/15/10.

73,

... Joe, W4TV

_______________________________________________
RTTY  mailing  list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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