[WT-support] SO2R Question

[Joe Subich, W4TV]

> Despite spending a long time working through the USB control protocol
> settings on the router and WT, I have never found the CW message
> sending on USB control to be "instant". There seem to be apparently
> random delays introduced, which simply do not occur with Classic
> control.

Since CW PTT is normally generated by the WinKey chip and/or in the
transceiver using semi break-in (transceiver VOX), any delays are
introduced by delays within the application software in sending the
CW message to WinKey.  Delays are typically due to out of order
execution, waiting for a response that has already occurred or missing
an echo from the WinKey itself.

Win-Test is the only major logger that does not use the WinKey 32 byte
(128 byte in WinKey 2/WinKey USB).  Instead it maintains a buffer in
the the program which causes intermittent delays depending on other
program activity (e.g., managing cluster connections) or operating
system activity (e.g. running anti-virus software or otter "hidden"
OS activity) - particularly if the application misses a "ready"
response or echo of the character sent.

73,

    ... Joe, W4TV


On 7/28/2013 3:52 AM, Don Beattie wrote:
> I agree with Bob.  Despite spending a long time working through the
> USB control protocol settings on the router and WT, I have never
> found the CW message sending on USB control to be "instant". There
> seem to be apparently random delays introduced, which simply do not
> occur with Classic control. (I am using a u2R). On SSB the USB
> setting seems OK, although occasionally there is a delay in starting
> the DVK. But on CW, CLassic control has been essential here.
>
> In the IOTA contest this weekend, however, I experienced a problem
> with the SO2R settings which I had not come across before. The u2R
> would suddenly switch to listening on the wrong receiver, without any
> manual intervention. It always seemed to be after I have switched to
> the second rig and back again (using "*"), and I found that the
> headphone setting on WT had changed from "Listen to primary radio" to
> one of the other options, which seemed to be the cause of the
> problem. I've not yet got to the bottom of the problem, but it was
> annoying when it happened. Given the relative complexity of the key
> stroke to move the headphone setting (and so the low probability of
> and accidental instruction to WT) I feel there is something else
> going on which I plan to investigate.
>
> 73
>
> Don, G3BJ / G5W
>
>
>
>> ________________________________ From: "Bob Wilson, N6TV"
>> <n6tv at arrl.net> To: Win-Test Reflector <support at win-test.com> Sent:
>> Sunday, 28 July 2013, 3:58 Subject: Re: [WT-support] SO2R Question
>>
>>
>>
>> I was suggesting to use Classic Auto Control via COM ports (if LPT
>> not available).  It works perfectly well with Windows loggers such
>> as Win-Test, and it is far faster and more reliable than the
>> microHAM control protocol, especially when using Win-Test.  It
>> never experiences any "delays" thay others have reported when using
>> the microHAM control protocol.
>>
>>
>>
>> The microHAM support code in Win-Test is unlikely to be updated any
>> time soon, hence the suggestion of the workaround which has solved
>> these types of switching problems for many Win-Test users in the
>> past.
>>
>>
>>
>> 73,
>>
>> Bob, N6TV
>>
>> On Sat, Jul 27, 2013 at 6:21 PM, Joe Subich, W4TV
>> <lists at subich.com> wrote:
>>
>>
>>>> I recommend that you switch to Classic Auto Control,
>>>
>>>
> That is absolutely the *worst* thing to do.  Parallel Port Control
>>> (Classic Auto Control) is provided for use by *DOS* loggers
>>> only. LPT (Classic Auto Control) was *never* intended to be used
>>> when Router was in operation.  Use the USB configuration
>>> documented in the MK2R area at the web site
>>> www.microHAM-USA.com/support.html or in Router at "Help |
>>> Download Documents"
>>>
>>> I am away from the equipment at the present time due to a death
>>> in the family - however, the most likely cause for the issue at
>>> hand is that the logging software is sending commands out of
>>> order - it is doing a custom receive configuration *first*
>>> followed by a change focus command which recalls Router's stored
>>> settings (Function).
>>>
>>> Either fix the stored settings or fix the out of order commands.
>>>
>>> 73,
>>>
>>> ... Joe Subich, W4TV microHAM America, LLC.
>>> http://www.microHAM-USA.com
>>> http://groups.yahoo.com/group/microHAM
>>>
>>>
>>> _______________________________________________ Support mailing
>>> list support at win-test.com
>>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>>
>>
>> _______________________________________________ Support mailing
>> list support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
>>
>>
>>
>>
>>
>> _______________________________________________ Support mailing
>> list support at win-test.com
>> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support