On 1/2/2019 7:02 PM, Neil Zampella [email protected] [wsjtgroup] wrote:
I see it as a good test of the FT8 decoder's ability to pull out the data from all the dross.
I see it as an opportunity for FT8 ops to piss off RTTY ops, and it's not our fault. Thanks to a massive screw-up by the FCC the last time allocations by mode were made, all digital ops got badly short-changed on 80M, and the Commission doesn't seem willing to admit their mistake. RTTY ops are not permitted above 3600, which jams them (us) into what's left between CW (ending about 3560, with nets as high as 3585) and 3600 kHz.
I've always been primarily a CW op, but I work SSB and RTTY for contests to support my club (NCCC) and work a lot of FT8, JT65, JT9, and MSK144, mostly on 160 and 6M. I'm really positive about FT8 in contesting, and hope that it will bring lots of new folks into contesting. But let's all be good neighbors on the bands when we do it. Did anyone notice that during the Stew Perry contest on 160M last weekend, CW ops gave our FT8 watering hole a wide berth? Let's not be the ones to screw up that relationship!
73, Jim K9YC _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
