[WT-support] Advanced SO2R mode on phone doesn't work well right now

[Bob Wilson, N6TV]

2010/10/21 José Nunes CT1BOH <ct1boh at gmail.com>

>
> Situation:
> Runing on 14220; S&P on 21
> You spot a multiplier on 21 on 21221
> You stop RUN on 14220 and push Shift+F4 to send call into 21221
> Now two things can happen, station comes back to you or not
>
> Imagine station comes back to you
> In CQWW you send F2 to send report and zone and thats it
> but this is not CQWW but WPX so you need to send report
> What you want is program to remember you have pushed Shift+F4 and keep
> route to secondary radio so that next microphone or paddle CW goes to
> secondary radio
>

No, not if you press Shift+F4.  Only if you press CapsLock, then F4 or
another message key, would the mic/paddle be directed to the secondary
radio.  Press CapsLock again and I *think* paddle / mic focus should *
immediately* return to primary, but that may not be the way it works today.

Imagine now that station does not get back to you
> You want to keep pile-up going on primary radio, so push F1 or whatever,
> and close the route to secondary radio, so that, even if you say something
> on the mic or send CW paddle it goes to primary radio
>
> Is this it?
>

Yes.


>  As of today, on SSB if you push SHIFT+F4 to send call on secondary radio
> and station gets back to you, you don't want to push * to A/B active radios
> and after QSO push * again to A/B back to original setting
>

Correct.  Shift binds to secondary radio should work much differently than
CapsLock binds to secondary radio.  I am a touch typist so I don't like
constantly alternating between left shift and right shift while trying to
type a callsign on the secondary radio, which is why I never use shift binds
to secondary radio.  I hate pressing star as it swaps the left / right
windows around, and is very distracting.

The AltD scripts (http://www.kkn.net/~n6tv/AltDScripts3.zip) are one way I
have attempted to work around these Win-Test SO2R usability problems, though
momentarily changing the behavior of the spacebar takes a little
getting-used to.

Why don't you give them a try and let me know what you think?  Note that you
can enter *two* callsigns at once and the script automatically enters and
dupe checks the first call in the secondary radio window, and copies the
second call (from pileup) into the primary, no shift keys or caps lock
required.

73,
Bob, N6TV


>
>
> On Thu, Oct 21, 2010 at 6:45 PM, Bob Wilson, N6TV <n6tv at arrl.net> wrote:
>
>> Please explain how you would say a serial number on secondary radio in the
>> WPX Phone contest.  Press the star key to complete *every* secondary
>> radio QSO??  Did you *always* have to do that?
>>
>> I believe a change was introduced when Task #137<http://flyspray.win-test.com/index.php?id=137&do=details>,
>> an issue with Altnernating CQs, was fixed in version 3.16.  There is a note
>> that Task #264 <http://flyspray.win-test.com/index.php?id=264&do=details>and Task #137 are "in conflict", but there ought to be a way to address both
>> issues.
>>
>> Please do not count $TR2 / $TR1 macros when considering "last
>> transmission," as they do not seem to affect paddle focus at all on CW.
>> Sorry if that wasn't explained in detail.  Similarly, Shift-F1 etc. should
>> continue to work as they do today; the Shift-Fx keys do not affect paddle or
>> mic. focus at all, if I recall correctly.
>>
>> All I want is, if you press CapsLock, then F4 or F2, then speak into the
>> mic. *while the window is still yello*w, the audio should go to the
>> secondary radio, not the primary radio.  If you press CapsLock again, I
>> think mic. audio should immediately go back to primary.  This same thing
>> should happen on CW.  This is a very minor fix I am requesting.  No major
>> changes.
>>
>> SO2R programming is very complex when you consider repeating CQs,
>> alternating CQs, keyboard, headphone and output focus.
>>
>> There are lot of different opinions as to how it should be done.  There is
>> widespread agreement that N1MM's SO2R implementation is simpler and more
>> natural than Win-Test's.  Fortunately Win-Test is flexible and customizable,
>> and I can simulate most of the N1MM behavior in Win-Test via Lua scripts,
>> but given the limitations of the Secondary Radio window (e.g., no column
>> headings, no keystroke that works like star without swapping windows,
>> inconsistencies between phone and CW), there is a limitation as to how close
>> I can get.
>>
>> 73,
>> Bob, N6TV
>>
>> 2010/10/21 José Nunes CT1BOH <ct1boh at gmail.com>
>>
>>  OK
>>> To sum up things.
>>>
>>> We all agree that:
>>> 1. CW and SSB should work he same (there is a difference now)
>>> 2. The (Shift)/(caps on) that moves focus and the advanced SO2R scenarios
>>> are working properly
>>>
>>> We are discussion now what should happen when a manual transmission
>>> occurs (CW paddle or Microphone).
>>>
>>> As a matter of interest let me tell you that I do not use paddles in
>>> contests. I don' even take one to Madeira CR3E. I learned long time ago that
>>> paddle slow down the rate and it is an addiction having it on the side. If I
>>> need to send manual CW I use ALT K. I never use manual transmission, and
>>> only need it in case of QSY request, where specific QSY scenario fits my
>>> desire.
>>>
>>> When Bob says:
>>> -"not quite"
>>> to the question (Where should any manual transmission go? All the time to
>>> the primary radio, and it is up the op to control that with "*", with the
>>> exception that after pressing a message key if you send something more, the
>>> output goes to the highlighted secondary radio")
>>> and explains his idea by saying:
>>> - The output of a manual transmission (sending by paddles or speaking
>>> into the mic.) should  go to the *last* radio where a message was sent,
>>> which can be either the primary or secondary radio.  The star key can be
>>> used to override this default behavior.
>>>
>>> I also say not quite
>>>
>>> In a simple scenario configuration where for instance you send (shift +
>>> F10 and F10=pse QSY 10?) to send the content of F10 to secondary radio, N6TV
>>> proposal of any next transmission should go to the last radio where a
>>> message was sent, seems to be OK
>>>
>>> BUT in a more complex scenario configuration where for instance you send
>>> (shift+ F10 and F10=PSE QSY 10? $TR2 $F4)  then with N6TV proposal using the
>>> paddle after the last message was sent would send CW paddle transmission  to
>>> the wrong radio....
>>>
>>> I prefer simple things.
>>> In that regard I prefer to control manual (paddle or mic transmission) by
>>> pressing * and thus deciding which radio to route manual transmission.
>>>
>>> But as I said in the beginning I don't use paddles I use Atl+k and I like
>>> to use the * to send the TX to the radio I want...
>>>
>>>
>>> 73
>>> José
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.win-test.com/pipermail/support/attachments/20101021/1afb8b19/attachment.htm>