Adrian,
The Linux, Mac and Windows versions of the K3 Utility Terminal all work the same way. As Dick mentioned in his previous response to this same question, the K3 itself will not allow "lock on" indefinitely:
"I could remove the code that cuts off "diddle" upon running out of input
buffer, **but the K3's MCU will time out the diddle after a few seconds
anyway**, so it won't "lock on" for an indefinite period. I'm looking into
other ways to do this, but there are a lot of things on my task list ahead
of this."
You might consider FLDigi for a more feature rich RTTY mode app.
David, W4SMT
--- On Sat, 2/4/12, Adrian <
[hidden email]> wrote:
> I'm not sure if I'm missing something
> in trying to qso with k3utility
> terminal in RTTY mode (K3 > FSK-D).
> However I can send the cqdx macro tapping the macro then
> tapping transmit
> etc. I get a response, then
> type in the ops call etc, and tap transmit to get things
> going, however I
> cannot type at 45 bps and the tx stops
> before I'm done. This makes a mess of the qso bigtime.
>
> Why can't the tx be locked and still allow rx and tx auto on
> keyboard input
> such that I can key in my
> message without having to re-tap transmit?
>
> Adrian ... vk4tux
______________________________________________________________
Elecraft mailing list
Home:
http://mailman.qth.net/mailman/listinfo/elecraftHelp:
http://mailman.qth.net/mmfaq.htmPost: mailto:
[hidden email]
This list hosted by:
http://www.qsl.netPlease help support this email list:
http://www.qsl.net/donate.html
Locked
