KDSP2 development: How 'open source' is the code?

[Andrew Moore-3]

I recently acquired a KDSP2 from a fellow list member, and would like to do
some KDSP2 development - ideas include

- implementing a continuously-variable bandwidth DSP filter (like on K3) by
interfacing to an external rotary encoder
- implementing APF
- simplifying the user interface (fewer pushbuttons/menus)
- using external rotary encoder to vary noise reduction paramters
- ditch RTTY/SSB support, preserve RTC support

I don't want to get into a debate about which features you'd like to see
(everyone's different) - this is probably just a one-off project for now,
for myself.

What I'm wondering is given the appropriate development tools, how much of
the KDSP2 code can be rewritten?  Do we have access to only the the shapes
of the filters, for example, or is it possible to take over the KDSP2 and do
external I/O, write functions, etc. as if it's an embedded system? So as not
to reinvent the wheel, do we have access to code that's already been written
for AuxBus communication, startup/init, routines to read pushbuttons, etc.?

If I do custom coding like this, how does it "hook" into the K2 for button
presses and display stuff -- is this where the AuxBus comes in? Is there
counterpart code inside the K2 that needs to be written, or is there some
sort of API that I'd go through for button reads / display updates / etc?

Help from anyone who has been this route would be appreciated --
recommendations for tools, description of K2/KDSP2 architecture, etc...  I
understand Lyle KK7P has loads of knowledge about this, and I've
communicated with him some, but I've trying to give him some elbow room
until he's got more availability in a few weeks.

Thanks,
--Andrew, NV1B
..
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Eugene Balinski]

Andrew,

   I heartily agree. Those would be very useful changes and
would add to the utility and convenience of the K2.  It
would also "refresh" the K2 and confirm Elecraft's
 commitment to the K2.

   I also hope that there will be a clean interface to the
KPA-500 as well.

73
Gene K1NR

K2 6XXX
On Tue, 15 Feb 2011 09:38:17 -0500
 Andrew Moore <[hidden email]> wrote:

> I recently acquired a KDSP2 from a fellow list member,
> and would like to do
> some KDSP2 development - ideas include
>
> - implementing a continuously-variable bandwidth DSP
> filter (like on K3) by
> interfacing to an external rotary encoder
> - implementing APF
> - simplifying the user interface (fewer
> pushbuttons/menus)
> - using external rotary encoder to vary noise reduction
> paramters
> - ditch RTTY/SSB support, preserve RTC support
>
> I don't want to get into a debate about which features
> you'd like to see
> (everyone's different) - this is probably just a one-off
> project for now,
> for myself.
>
> What I'm wondering is given the appropriate development
> tools, how much of
> the KDSP2 code can be rewritten?  Do we have access to
> only the the shapes
> of the filters, for example, or is it possible to take
> over the KDSP2 and do
> external I/O, write functions, etc. as if it's an
> embedded system? So as not
> to reinvent the wheel, do we have access to code that's
> already been written
> for AuxBus communication, startup/init, routines to read
> pushbuttons, etc.?
>
> If I do custom coding like this, how does it "hook" into
> the K2 for button
> presses and display stuff -- is this where the AuxBus
> comes in? Is there
> counterpart code inside the K2 that needs to be written,
> or is there some
> sort of API that I'd go through for button reads /
> display updates / etc?
>
> Help from anyone who has been this route would be
> appreciated --
> recommendations for tools, description of K2/KDSP2
> architecture, etc...  I
> understand Lyle KK7P has loads of knowledge about this,
> and I've
> communicated with him some, but I've trying to give him
> some elbow room
> until he's got more availability in a few weeks.
>
> Thanks,
> --Andrew, NV1B
> ..
>

______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[hidden email]
>
> This list hosted by: http://www.qsl.net
> Please help support this email list:
> http://www.qsl.net/donate.html

---------------------------------------------------------------------
Web mail provided by NuNet, Inc. The Premier National provider.
http://www.nni.com/
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Andrew Moore-3]

K1NR> Those would be very useful changes and would add to the utility and
convenience of the K2.  It would also "refresh" the K2

Exactly.  I think there's great potential in the K2 that can be brought out,
and the KDSP2 is the key to injecting some new life into it - bringing it
closer to the features/capabilities - or even some of the "feel" - of the
K3.

The key to expanding and refining the K2 is now software, and the KDSP2
seems to be the easiest way to get there.  If the end user can get access to
a processor and then hook into the K2 - which it seems the KDSP2 is already
doing - the possibilities are great.

--Andrew, NV1B
..
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Vic K2VCO]

One thing that would be hard would be to change the user interface. This would require
mods to the K2's main processor firmware. Only one person in the world can do that, and
his initials are WB.

On 2/15/2011 6:38 AM, Andrew Moore wrote:

> I recently acquired a KDSP2 from a fellow list member, and would like to do
> some KDSP2 development - ideas include
>
> - implementing a continuously-variable bandwidth DSP filter (like on K3) by
> interfacing to an external rotary encoder
> - implementing APF
> - simplifying the user interface (fewer pushbuttons/menus)
> - using external rotary encoder to vary noise reduction paramters
> - ditch RTTY/SSB support, preserve RTC support
>
> I don't want to get into a debate about which features you'd like to see
> (everyone's different) - this is probably just a one-off project for now,
> for myself.
>
> What I'm wondering is given the appropriate development tools, how much of
> the KDSP2 code can be rewritten?  Do we have access to only the the shapes
> of the filters, for example, or is it possible to take over the KDSP2 and do
> external I/O, write functions, etc. as if it's an embedded system? So as not
> to reinvent the wheel, do we have access to code that's already been written
> for AuxBus communication, startup/init, routines to read pushbuttons, etc.?
>
> If I do custom coding like this, how does it "hook" into the K2 for button
> presses and display stuff -- is this where the AuxBus comes in? Is there
> counterpart code inside the K2 that needs to be written, or is there some
> sort of API that I'd go through for button reads / display updates / etc?
>
> Help from anyone who has been this route would be appreciated --
> recommendations for tools, description of K2/KDSP2 architecture, etc...  I
> understand Lyle KK7P has loads of knowledge about this, and I've
> communicated with him some, but I've trying to give him some elbow room
> until he's got more availability in a few weeks.
>
> Thanks,
> --Andrew, NV1B

--
Vic, K2VCO
Fresno CA
http://www.qsl.net/k2vco/
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[ac0h]

On Tue, 15 Feb 2011 10:11:50 -0800
Vic K2VCO <[hidden email]> wrote:

> One thing that would be hard would be to change the user interface.
> This would require mods to the K2's main processor firmware. Only one
> person in the world can do that, and his initials are WB.
>

Last I heard all the on chip storage in the K2 is used up so there
can't be any new features added like the K3. It is a 10+ year old radio.


--
R. Kevin Stover
AC0H
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Andrew Moore-3]

Vic/K2VCO> One thing that would be hard would be to change the user
interface. This would require
mods to the K2's main processor firmware.

Yes I forgot the KDSP2 requires K2 firmware 2.01 or greater, indicating that
there's something on the K2 that communicates with the KDSP2 (this is
probably where the AuxBus comes in).

Maybe this expansion isn't as easy as I thought.

--Andrew, NV1B
..
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

[Mike Markowski-2]

This is somewhat related to the quoted text below.  In Jan 2010 I
started writing code that presents a trapezoid on the screen.  If you
drag it, you choose XFILs.  Then a trapezoid nested in that represents
the DSP filter.  It can be dragged to change center freq, or for SSB
edges can be individually dragged to adjust low and high cut freqs.  It
also allows for user entry of the various other DSP settings.

It hasn't been finished but really, ma, I have a good excuse.  I got a
K3.  The code is in Java, and when it starts up takes a good long while
to read the K2's current settings.  I was just beginning to write code
to store them to a file so the user can choose between a fresh, but time
consuming, rig read or trust the file settings as up to date.  And like
I say, that's when the K3 showed up.

If anyone has interest I'm willing to share the Java source.  Just drop
me a line.  The idea was to have an intuitive user interface that made
it a snap to mess with the DSP.  To quote Maxwell Smart, "Missed it by
that much!"

73,
Mike ab3ap

On 02/15/11 09:38, Andrew Moore wrote:
> I recently acquired a KDSP2 from a fellow list member, and would like to do
> some KDSP2 development - ideas include
>
> [...]
> - simplifying the user interface (fewer pushbuttons/menus)
> [...]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[hidden email]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html