What you say is true, and as a hard-core contester I take advantage of all the automation I can get to maximize my QSO rate.

The distinction is between transmitting and receiving. In receiving, the difference is that in CW and SSB my brain is an integral part of the process of getting the signal information from audio to log, no silicon required or desired. Development and maintenance of the skills required to do that accurately and efficiently are what I find most rewarding about operating. In that respect, I've been "geek free" since 1964.

73...
Randy, W8FN

On 6/1/2018 3:48 PM, Bob McGraw K4TAX wrote:
Be it CW, RTTY, PSK, SSB,  JT65 or other modes, today's computer integration into the ham shack as produced many automated contacts with little to no personal intervention.   Where as one says FT-8 mode is used to rack up countries........what about the automated CQ's from memory keyers in CW mode with the follow up always being a 599 report, or RTTY contacts structured with Function Keys for the exchange, and software which supports other like modes.   Even SSB contacts with CQ's in the operators voice with digital voice recorders will often prevail.   Yes, I know it is repetitive calling and it is done to save the voice or fingers, but really, automated is automated and the dreaded computer is the basis, ..............not the FT-8 software.   As Chicken Little said..........."it's everywhere, it's everywhere."

Just wait until the upcoming Field Day.  The FT-8 operations, with operators trying to modify the data exchange to comply with the reporting and confirmation of contacts for Field Day exchange is surely to be a little more than a "train wreck".   UGH! Banish the thoughts.

73

Bob, K4TAX

______________________________________________________________
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
Message delivered to [email protected]

Reply via email to