I know about FT8 DXPedition mode.  I have used it a couple of times just for the hell of it but I never claim DXCC credit for FT8 contacts.  I also know that 14080 isn't one of the "recommended" frequencies for FT8.

I would argue about the efficacy compared to CW.  I know it reports all of those negative SNRs but they are bogus.  As to rates, when my friend Ned, AA7A, was operating RTTY from S. Georgia and S. Sandwich he was knocking them dead.  On 15 meters VP8SGI made almost the same number of RTTY contacts as SSB contacts.  They only operated RTTY on three bands yet about 10% of their total Qs were RTTY.

Wes  N7WS


On 3/22/2019 4:08 PM, Jim Brown wrote:
On 3/22/2019 3:29 PM, Wes wrote:
DXCC certificate that actually says "RTTY" on it. Today it's harder to find new ones, but I have 254 confirmed now with my modest station.

Congrats on that.  I too am quite happy with AFSK.


It's great fun and even though it's a "digital" mode, operator skill still makes a difference.

Yep. RTTY contesting can be a lot of fun, especially with SO2R. A couple of guys in our contest club, WK6I and W0YK, win RTTY contests running three radios.  And operator skill also matters with FT8, even though it's also possible to make QSOs with minimal operator involvement.

Unfortunately, I heard one of the current DXpeditions plopped on 14.080 using the abysmal FT8

That's because 1) RTTY is very difficult for the DXpedition operator in a pileup, making for slow QSO rates; 2)  the latest version of WSJT-X includes a "DXpedition mode" that allows far greater rates than RTTY; and the signal to noise advantage of FT8 over CW (moderate) and SSB (a lot) allows QSOs over more difficult paths and with more modest stations.

73, Jim K9YC

______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Reply via email to