[Elecraft] K3 Shipping Delays

[Tree]

On Mon, Aug 27, 2007 at 11:39:58AM -0700, Jim Brown wrote:

> So, while we're anxious to see the finished product on our operating 
> bench, the second sort of delays are to be expected from any mfr who 
> is reasonably picky about what parts they buy and where they buy 
> them, and the first sort of delays will result in a better radio. So 
> cool your jets, and give Wayne and Eric the breathing space to do 
> their jobs. They have a long history of doing that very well.

It isn't my place to add much data to this, but I think I can make a couple
of general observations.

I have used this radio now for some 7 weeks now.  I didn't even open it
up for the first few weeks and thus far have added one component to a 
board.  The stability of the hardware is fantastic.  This is the main 
gate I would think to starting shipping.  I believe that mostly it is 
logistics of getting the first batch all built - integrated and tested.

That's a lot of radios to ship at once.  

There will continue to be lots of work to do with the firmware.  There
are two different firmware programs - the MCU, which is what controls
everything except the DSP firmware.  These are split up between two 
different people and there are already a number of "nice to have" 
features that have been judged to be something that can wait until after
"FCS" (first customer ship).  

So - your K3 will continue to improve after you get it...  but what you 
get out of the box will be better than you probably expected.

Why - just this weekend, my DSP noise blanker was totally redesigned and
really works well on the electric fence noise. :-)  Yours will work this
well out of the box.

Hope this helps - I can't answer when - but just that the hardware is 
stable and I believe the "right" decisions are being made - and no, they
aren't waiting until every last feature is included in the firmware - 
since that can be updated after you get your radio.

73 Tree N6TR
K2 S/N 2411
K3 S/N 00000000013 (I think - still no label)