[WT-support] AUTOCW on Secondary Radio?

[Bob Wilson, N6TV]

Maybe there is confusion because normally you would use the secondary radio
to check multipliers, but that's not the case here, because we're
discussing the behavior when the secondary radio is set to RUN mode, not
S&P mode.

Why should RUN mode + AUTOCW in the Primary radio window operate
differently than RUN + AUTOCW in the Secondary radio window?

When the Secondary radio window is active (yellow background) what's the
difference between typing 4 characters and pressing [Insert] to start
sending vs. typing 3 characters and typing the 4th to start sending?  Both
actions will immediately interrupt sending on the Primary radio *unless* you
wait for that sending to complete before you press that last key.

For consistency alone, if both windows are set to RUN mode (there are
independent settings, one for each window), I think both windows should
work the same with respect to AUTOCW.

The way it works now seems to be a coding oversight, not the intended
behavior.  AUTO-Sending was added in version 3.0.1, long before RUN/S&P
switching was added in version (3.13.0), so maybe this AUTOCW behavior made
sense in the old days, when you could not set the Secondary radio to RUN
mode, but it doesn't make much sense now.

73,
Bob, N6TV

On Tue, Feb 9, 2016 at 11:52 AM, Laurent HAAS - F6FVY <f6fvy at free.fr> wrote:

> Hi Bob et al.
>
> Le 09/02/2016 20:24, Bob Wilson, N6TV a écrit :
>
> So, I see no reason why AUTOCW cannot work in the secondary radio window
>> when the secondary radio window is active (yellow) and in RUN mode.  If
>> the start of transmission interrupts something like a CQ on the primary,
>> I think that's OK, and that is what is wanted when you are trying to CQ
>> on two different radios at the same time.
>>
>
> And what if the start of transmission interrupts the "call + exchange"
> sent on the primary ? It's *not* OK at all... And it will happen every
> time, if you want to manage a "double run".
>
> Getting back to Ingo's original question, I wonder why you like to use
>> AUTOCW?  Did you know that you can press the INSERT key, then finish
>> typing the rest of the call and the CW will catch up?  You don't have to
>> enter a complete callsign before pressing INSERT.  Yes, AUTOCW saves one
>> keystroke, but it means you have to wait before you type that 3rd of 4th
>> letter of the call, and memorize the rest of it, otherwise sending may
>> start too soon.
>>
>
> AUTOCW is working well only in specific conditions, ie the speed of the
> other station is not too fast, and not too slow, and the number of
> characters of his callsign is 4 or 5. Good luck if OM2015TITANIC calls you
> with AUTOCW... ;-)
>
> It's theoretically a great idea, but not in reality. You have to adapt
> yourself with its constraints, which is contrary to its purpose. The best
> way to be in-sync is to start sending when the other station stops with
> INSERT (or another key).
>
>
> 73
>
> Larry - F6FVY
>
> --
> Remember Jan. 7 2015 - #JeSuisCharlie
> Remember Nov. 13 2015 - #JeSuisParis
> _______________________________________________
> Support mailing list
> support at win-test.com
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20160209/addb1b55/attachment-0001.html>