[Elecraft] K3_CW_Data_Mode

Joe Subich, W4TV lists at subich.com
Wed Dec 30 20:17:38 EST 2009



> There doesn't appear to be any other input line that could be 
> used for this purpose, though :/

One might conceivably use multiple input lines ... while it 
would take some work, pull the FSK and Key lines low at the 
same time (diodes like the straight key/paddle "fix" for the 
K2).  I suspect the controller could be programmed to work with 
that.  If FSK and Key are inconvenient, how about Key and PTT? 
Again, as long as PTT proceeds Key input (when using computer 
keying), it should not be too difficult to distinguish between 
normal operation and external "tune" ... 

I only avoid the Inh line because of the conflict with its 
use for Inhibit and its alternate function "K3 on" for XVTR 
use.  

73, 

   ... Joe, W4TV 
 



> -----Original Message-----
> From: elecraft-bounces at mailman.qth.net 
> [mailto:elecraft-bounces at mailman.qth.net] On Behalf Of Iain 
> MacDonnell - N6ML
> Sent: Wednesday, December 30, 2009 6:26 PM
> To: Gary Hinson
> Cc: elecraft at mailman.qth.net
> Subject: Re: [Elecraft] K3_CW_Data_Mode
> 
> 
> On Wed, Dec 30, 2009 at 2:53 PM, Gary Hinson <Gary at isect.com> wrote:
> >> >  A while back, I made a suggestion to Wayne that perhaps the "TX 
> >> > inhibit" pin on the ACC port could be given another purpose
> >> > - to invoke "TUNE".  I envisaged a new config setting like 
> >> > "CONFIG:TX INH" = "HI=Tun" or "LO=Tun". Wayne seemed to think it 
> >> > wasn't a bad idea, but would be very low priority, based 
> on demand.  
> >> > It seems like this model may work for the Quadra 
> application too, 
> >> > without having researched it at all.
> >>
> >> While repurposing the "TX Inh" pin has appear for 
> non-Quadra users, 
> >> it is a step backward
> >
> > Sounds to me like an inadvisable combination of controls 
> sharing the 
> > one line: TX inhibit and key TX clearly are opposites.  If someone 
> > accidentally misconfigures their K3 (not altogether unlikely), this 
> > could get messy if a TX inhibit command actually keys the rig.
> 
> Fair point.. whilst I'm not a fan of wrapping everything in 
> cotton-wool, I can see how that could lead to an expensive "oops!".
> 
> 
> > I'm not arguing against the facility to tune the rig if that's what 
> > you really need, just not on the TX inhibit line.
> 
> There doesn't appear to be any other input line that could be 
> used for this purpose, though :/
> 
>     ~Iain / N6ML 
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html



More information about the Elecraft mailing list