On May 3, 2009, at 6:40 PM, wayne burdick wrote:
Meanwhile, I save all of the suggestions I receive (or see posted)
regarding future K2 functionality.
Wayne was collecting these ideas starting two years ago, just as the
K3 was announced:
On May 4, 2009, at 5:19 AM, David Woolley (E.L) wrote:
hen I started in the software industry, one of
the first things one was told was that one should document code as
though one expected to be run over by a bus, the next day.
As a fellow software professional, I agree with you in theory.
Bill Coleman wrote:
You can probably count the number of programmers who have written K2
firmware on the fingers of one hand. With such a small community, it
may be simpler to communicate using tribal knowledge than extensive
documentation.
My guess is that you could count them on the
You can probably count the number of programmers who have written K2
firmware on the fingers of one hand.
My guess is that you could count them on the fingers of one finger!
Double that if you include the KDSP2 :-)
73,
Lyle KK7P
wayne burdick wrote:
Even though the code is well-documented, I'd want to create
theory-of-ops and maintenance documentation before I tried to hand it
off to another programmer. This is often necessary for projects where
you don't have the luxury of writing everything in an encapsulated,
I have the latest 2.04 firmware revision for my K2. Are there any future
firmware revisions planned that will allow different modes to be saved for
VFO A and VFO B. It would be nice to save CW in A and USB in B.
Mike AC6JA
**The Average US Credit Score is 692. See Yours in
@mailman.qth.net
Sent: Sunday, May 03, 2009 2:10 PM
Subject: [Elecraft] Saving K2 VFO modes
|I have the latest 2.04 firmware revision for my K2. Are there any
future
| firmware revisions planned that will allow different modes to be saved
for
| VFO A and VFO B. It would be nice to save CW in A and USB
You got my vote on open source or finding someone to work on updates on
occasion...
--
Mike
WE0H
K2 #6698
Mike H wrote:
Hi Mike,
This request goes back years, way before the K3. K2 development has
stalled with the introduction of the K3. I suspect the only way to get it
moving again
Mike-WE0H wrote:
You got my vote on open source or finding someone to work on updates
on occasion...
Mike (et al),
The K2's present MCU is maxxed (no code space left). That's the main
reason there's been no further development on it. But it's also a very
mature product. Requests for
Thanks for the update. This will remain on my wish list.
Until then, looks like it might be time to upgrade to the K3 as it seems to
have all that I want!
Thanks for all your hard work that brings us joy!
Mike AC6JA
In a message dated 5/3/2009 3:39:06 P.M. Pacific Daylight Time,
Hi Wayne,
Excellent to hear there is a future to the K2's software. Thank you for
the update on this. C-U- @ Dayton
--
Mike
WE0H
K2 #6698
Wayne wrote:
Mike-WE0H wrote:
You got my vote on open source or finding someone to work on updates
on occasion...
Mike (et al),
The K2's
11 matches
Mail list logo
