Re: [Elecraft] Request for Elecraft K3 Utility program

2009-02-25 Thread Bill Feidt
Julian, G4ILO wrote:

> I don't think the terminal function in the Elecraft Utility was intended for
> this sort of use. It was meant for testing out command sequences. Why, may I
> ask, are you using it like this? There are various other programs that can
> send CW from the keyboard, with the kind of macro support you are
> requesting, including my own program KComm.

Thank you, Julian.  I was not aware of KComm.  I downloaded it. The set 
up was straightforward and it seems to work quite nicely.  Will 
definitely explore its capabilities as it seems to be very close to what 
I'm looking for.  Thanks for making this program available.

73,

Bill/NG3K

__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

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


Re: [Elecraft] Request for Elecraft K3 Utility program

2009-02-25 Thread Julian, G4ILO


Bill Feidt wrote:
> 
> I second Jim's enthusiasm regarding the little terminal program included 
> with the K3 utility software.  His idea about having an "immediate send" 
> option is a good one.
> 
> Another modification that would be immensely useful for casual contest 
> participants would be the creation of two variables that would be 
> callable from within any of the function key macros:
> 
>$serial
>$callsign
> 
> $serial would be a number that would be assignable as part of the user 
> interface.  An associated "increment" button would allow the user to 
> increment the number by 1.  The number could also be changed to any 
> desired value on the screen by the user.  Whatever number currently 
> appears in the field would be sent to the send buffer when called from 
> within a user macro, e.g.
> 
>F3: 599 nr $serial bk
> 
> $callsign would be set up in a similar fashion and would be changeable 
> by the user on the screen.  The value of $callsign would be sent to the 
> send buffer when called from within a user macro, e.g.
> 
>F3: $callsign tu 599 nr $serial bk
> 
> 

I don't think the terminal function in the Elecraft Utility was intended for
this sort of use. It was meant for testing out command sequences. Why, may I
ask, are you using it like this? There are various other programs that can
send CW from the keyboard, with the kind of macro support you are
requesting, including my own program KComm.

-
Julian, G4ILO. K2 #392  K3 #222.
http://www.g4ilo.com/ G4ILO's Shack   http://www.g4ilo.com/blog.html G4ILO's
Bloghttp://www.g4ilo.com/kcomm.html KComm for Elecraft K2 and K3 
-- 
View this message in context: 
http://n2.nabble.com/Request-for-Elecraft-K3-Utility-program-tp2381160p2384511.html
Sent from the Elecraft mailing list archive at Nabble.com.

__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

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


Re: [Elecraft] Request for Elecraft K3 Utility program

2009-02-25 Thread Bill Feidt
I second Jim's enthusiasm regarding the little terminal program included 
with the K3 utility software.  His idea about having an "immediate send" 
option is a good one.

Another modification that would be immensely useful for casual contest 
participants would be the creation of two variables that would be 
callable from within any of the function key macros:

   $serial
   $callsign

$serial would be a number that would be assignable as part of the user 
interface.  An associated "increment" button would allow the user to 
increment the number by 1.  The number could also be changed to any 
desired value on the screen by the user.  Whatever number currently 
appears in the field would be sent to the send buffer when called from 
within a user macro, e.g.

   F3: 599 nr $serial bk

$callsign would be set up in a similar fashion and would be changeable 
by the user on the screen.  The value of $callsign would be sent to the 
send buffer when called from within a user macro, e.g.

   F3: $callsign tu 599 nr $serial bk

73,

Bill/NG3K
__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

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


[Elecraft] Request for Elecraft K3 Utility program

2009-02-24 Thread jpk5lad

The Elecraft K3 Utility program, is a great thing to have and is 
handy as an extra pair of hands.  It provides, not only the conduit 
to upload firmware and make changes in the K3 but it also has a 
really nice terminal program to display what the K3 has decoded.  
My request is for an addition in the Terminal section.   

If I had a chance to suggest an addition to this program, however, 
I would ask that the use of the Memory keys be available as a 
one click operation rather than two but to make that addition as 
an option.  Now, one must click on the Memory button and then 
on the Transmit button when you want to actually send it.  Often 
this is exactly how you want to use this feature, however, if an 
option was added (TX data immediately) to just click on the 
Memory button and it adds the memory data to the buffer and 
immediately transmits it, that would save a step and often times, 
this could be extra helpful.  I also would hope it could be optional 
so the times where you want to have the message "locked and 
loaded" and ready to be sent at just the right time as it is now.  
Also the current way allows multiple messages to be combined in 
the buffer.  This request is for an "in addition to" and not an "in 
place of" which, by the way is the same answer I gave my wife 
when I told her I was ordering a K3 and she asked, "Which radio 
does it replace?"

A second request along the same line, is to have an "Ooops" 
button to clear the transmit buffer like the current Clear button 
which flushes the received buffer.  Obviously, if the first request 
above was made (immediate TX on Memory button click) but not 
made optional, there would be no need for this second request.

Personally, I'd like to see both options implemented.

Still, the K3 Utility program is a super addition to K3 operation, 
just the way it is now.

Thanks and 73,
Jim - K5LAD



"It's so simple to be wise. Just think of something
stupid to say and then don't say it." -- Sam Levenson
=
My Web Page - http://www.hayseed.net/~jpk5lad


__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

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