[Elecraft] K1 DDS VFO Retrofit?

John J. McDonough John J. McDonough" <[email protected]
Thu Dec 25 10:41:05 2003


Brad

That sounds like a pretty neat idea.

There are a couple of challenges around bandswitching, though.  The K1 has a
bunch of processors in it, apparently to help with the parts count and board
interconnections.  Somehow, you would want to communicate the K1's band
position back to the processor controlling the DDS (or vice versa).  Since
Elecraft doesn't publish their source, this might be a bit of a challenge.
I suppose you could just have a band button on your DDS controller and push
it when you pushed the K1's band button, but it seems like it would be nice
to get it all integrated.  To make that happen will take a fair bit of
reverse engineering.

Still, sounds like a fun experiment if I could ever find the time <g>.  I
actually have the predecessor card to the DDS daughtercard laying on top of
my K1.  Never occurred to me to merge them, but I could see some benefits!

72/73 de WB8RCR    http://www.qsl.net/wb8rcr
didileydadidah     QRP-L #1446 Code Warriors #35



----- Original Message ----- 
From: "Brad Hedges" <[email protected]>
To: <[email protected]>
Sent: Thursday, December 25, 2003 7:37 AM
Subject: [Elecraft] K1 DDS VFO Retrofit?


> Best Holiday Greetings to one and all,
>
> I'm ordering a K1 kit (after payday), and I would like to integrate a DDS
> VFO (using the DDS daughtercard from NJQRP
> http://www.njqrp.org/dds/index.html ).
>
> Has anybody done anything like this? Is there some
> firmware/software/hardware reason it can't reasonably be done? Has anybody
> tried/done this and can provide some help or guidance or share some
> pitfalls?
>
> Thanks,
>
> K0BHC
> Brad
>
> _______________________________________________
> Elecraft mailing list: [email protected]
> You must be subscribed to post to the list.
> To subscribe or unsubscribe see:
http://mailman.qth.net/mailman/listinfo/elecraft
> Elecraft Web Page: http://www.elecraft.com
> Also see: http://www.elecraft.com/elecraft_list_guidelines.htm
>