[K3] Macro enhancement suggestion

[Carl W Clawson]

I set out to make four macros so that I could select either of two mics
(CM500 & HC4) in either of two modes (contest/DX & net/ragchew). This
involves setting mic HI/LO and bias ON/OFF that toggle by a keypress, so you
can't be sure whether you need to do a keypress unless you know the initial
state. In other words, you can't write a macro that's guaranteed to work. In
practice, you'll have about a 50% failure rate.

Am I missing something?

If not, I have a suggestion: In addition to the UP and DN commands, have a
command to reset the menu entry to a known ground state. This could possible
be a press of the CLR button, or maybe a new command. One could then proceed
with confidence to set up the desired parameters. Adding commands to cover
specific menu items would be another approach.

This would also cover the case of not knowing how many DN commands to send
if in the future more knob-selectable menu entries were added. Elecraft
could add more selections and your macros wouldn't break.

73 and thanks for listening
Carl WS7L
K3 #486

______________________________________________________________
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

[wayne burdick]

Hi Carl,

I like your idea of a reset-to-known-state command usable with macros.  
I'll add this to my list.

tnx
Wayne
N6KR

On Jul 28, 2011, at 10:19 PM, Carl Clawson wrote:

> I set out to make four macros so that I could select either of two  
> mics
> (CM500 & HC4) in either of two modes (contest/DX & net/ragchew). This
> involves setting mic HI/LO and bias ON/OFF that toggle by a  
> keypress, so you
> can't be sure whether you need to do a keypress unless you know the  
> initial
> state. In other words, you can't write a macro that's guaranteed to  
> work. In
> practice, you'll have about a 50% failure rate.
>
> Am I missing something?
>
> If not, I have a suggestion: In addition to the UP and DN commands,  
> have a
> command to reset the menu entry to a known ground state. This could  
> possible
> be a press of the CLR button, or maybe a new command. One could then  
> proceed
> with confidence to set up the desired parameters. Adding commands to  
> cover
> specific menu items would be another approach.
>
> This would also cover the case of not knowing how many DN commands  
> to send
> if in the future more knob-selectable menu entries were added.  
> Elecraft
> could add more selections and your macros wouldn't break.
>
> 73 and thanks for listening
> Carl WS7L
> K3 #486
>
> ______________________________________________________________
> 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

______________________________________________________________
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