Elecraft is 30 miles down the road from me, and many of those who work there are my neighbors (Elecraft also employs designers and support people who are not within driving distance). In my 60+ years as a ham and working engineer, I've encountered NO other companies whose OWNERS monitor their email support reflector, UNDERSTAND the questions, comments, and ideas expressed there, and DO something positive in response. EVERY company and person makes mistakes or has bad days. What they do in response is a large part of what separates the great companies from the others.

Old timers can testify that one of the major JA radio companies (starts with a Y) took three models to correct AWFUL key clicks in their flagship (expensive) radio, and to get that fix, you had to sell the old one and buy the new one. And they didn't learn from it -- much later, very different designs of their flagship models (twice the cost of a K3S) had very bad clicks and took years to fix with a firmware update. And they didn't do that until I published a detailed analysis of ARRL Lab test data showing how bad they were. With that update, they're better, but still not great. But, thanks to limitations of the design, that's the best they can do without starting over. :)

73, Jim K9YC

On Tue,6/13/2017 8:46 AM, G4GNX wrote:
THIS is why I'm proud to own Elecraft equipment and will continue to do so.

73,

Alan. G4GNX

-----Original Message----- From: Wayne Burdick
Sent: Tuesday, June 13, 2017 4:09 PM
To: Andrew Holman
Cc: Elecraft Reflector
Subject: Re: [Elecraft] Frustration with Elecraft

Hi Andrew,

I’m the CTO of Elecraft and principal designer of our transceivers. I’ll try to address your issues:........................................
______________________________________________________________
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