I have used the Logikey for years. Stated as simply
as possible, it's Elecraft-grade. If you haven't used one, your should try it. I'd pay for an add-in of the Logikey to the K2, were that possible. Ideally, taking the keyer function out of the main CPU would free up code space for other functions. __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
> Ideally, taking the keyer function out of the main CPU would > free up code space for other functions. Fortunately, this idea is a non-starter. Removing the internal keyer from the K2 would obviously reduce the K2's portability significantly, requiring one to take, and power, an additional box in /p operation. Bad idea. Also, for what it's worth. I've used both the Logikey and the K2 internal keyer, both now for a number of years. Initially, I used the Logikey attached externally, and I really didn't like the K2 internal keyer, whose timing and response were sufficiently different from the Logikey to cause me problems. But I decided to make an effort to learn the K2 keyer, precisely because I was not happy with the idea of having to trek the Logikey around for portable use. It actually didn't take long to master the K2 internal keyer, although I found, rather strangely, that I liked it in B mode better than A, which I had used with the Logikey. And -- once I had learned it, I found I preferred it to the Logikey -- not just a little, but a lot. best wishes, dave belsley, w1euy _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
On Wed, 10 Nov 2004, David A. Belsley wrote:
> >> Ideally, taking the keyer function out of the main CPU would >> free up code space for other functions. > > Fortunately, this idea is a non-starter. Removing the internal keyer from > the K2 would obviously reduce the K2's portability significantly, requiring > one to take, and power, an additional box in /p operation. Bad idea. Have you seen the size of tiny pic keyers nowadays? If the keyer had to be taken out of the CPU, I sure wouldn't miss it, I'd replace it. -- Hisashi T Fujinaka - [hidden email] BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
Administrator
|
In reply to this post by David A. Belsley
PICs are notorious for the lelev of hackery necessary to make things
work and fit, but the K2's PIC18 with its 31 stack levels just might allow for a level of modularity that would let the firmware be customized on a module level at some point in the future. Or maybe Microchip will come out with a pin@icompatible PIC18 with 4x the codespace and Elecraft can offer it as an optin. On Wed, 10 Nov 2004 8:33 am, David A. Belsley wrote: >> free up code space for other functions. > Removing the internal keyer from the K2 would obviously reduce the K2's > portability _______________________________________________ Elecraft mailing list Post to: [hidden email] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com |
Free forum by Nabble | Edit this page |