<html><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:10pt"><div><span>I agree with Bob. </span><span style="background-color: transparent;">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.</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: verdana, helvetica, sans-serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: verdana, helvetica, sans-serif; background-color: transparent; font-style:
normal;"><span>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.</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: verdana, helvetica, sans-serif; background-color: transparent; font-style:
normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: verdana, helvetica, sans-serif; background-color: transparent; font-style: normal;"><span>73</span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: verdana, helvetica, sans-serif; background-color: transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: verdana, helvetica, sans-serif; background-color: transparent; font-style: normal;"><span>Don, G3BJ / G5W </span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 10pt;"> <div style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font size="2" face="Arial"> <b><span
style="font-weight:bold;">From:</span></b> "Bob Wilson, N6TV" <n6tv@arrl.net><br> <b><span style="font-weight: bold;">To:</span></b> Win-Test Reflector <support@win-test.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Sunday, 28 July 2013, 3:58<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [WT-support] SO2R Question<br> </font> </div> <div class="y_msg_container"><br><div id="yiv797278707"><div dir="ltr"><div>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.<br>
</div><div><br></div><div><div>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.<br>
</div><div><br></div></div><div>73,<br></div><div><div class="yiv797278707gmail_extra"><div><div>Bob, N6TV</div></div><br><div class="yiv797278707gmail_quote">On Sat, Jul 27, 2013 at 6:21 PM, Joe Subich, W4TV <span dir="ltr"><<a rel="nofollow" ymailto="mailto:lists@subich.com" target="_blank" href="mailto:lists@subich.com">lists@subich.com</a>></span> wrote:<br>
<blockquote class="yiv797278707gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">
<div><br>
> I recommend that you switch to Classic Auto Control,<br>
<br></div>
That is absolutely the *worst* thing to do. Parallel Port Control<br>
(Classic Auto Control) is provided for use by *DOS* loggers only.<br>
LPT (Classic Auto Control) was *never* intended to be used when<br>
Router was in operation. Use the USB configuration documented in<br>
the MK2R area at the web site <a rel="nofollow" target="_blank" href="http://www.microham-usa.com/support.html">www.microHAM-USA.com/support.<u></u>html</a> or<br>
in Router at "Help | Download Documents"<br>
<br>
I am away from the equipment at the present time due to a death in<br>
the family - however, the most likely cause for the issue at hand<br>
is that the logging software is sending commands out of order - it<br>
is doing a custom receive configuration *first* followed by a change<br>
focus command which recalls Router's stored settings (Function).<br>
<br>
Either fix the stored settings or fix the out of order commands.<br>
<br>
73,<br>
<br>
... Joe Subich, W4TV<br>
microHAM America, LLC.<br>
<a rel="nofollow" target="_blank" href="http://www.microham-usa.com/">http://www.microHAM-USA.com</a><br>
<a rel="nofollow" target="_blank" href="http://groups.yahoo.com/group/microHAM">http://groups.yahoo.com/group/<u></u>microHAM</a><div><div><br>
<br>
______________________________<u></u>_________________<br>
Support mailing list<br>
<a rel="nofollow" ymailto="mailto:support@win-test.com" target="_blank" href="mailto:support@win-test.com">support@win-test.com</a><br>
<a rel="nofollow" target="_blank" href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support">http://lists.f5mzn.org/cgi-<u></u>bin/mailman/listinfo/support</a><br>
</div></div></blockquote></div><br></div></div></div>
</div><br>_______________________________________________<br>Support mailing list<br><a ymailto="mailto:support@win-test.com" href="mailto:support@win-test.com">support@win-test.com</a><br><a href="http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br><br><br></div> </div> </div> </blockquote></div> </div></body></html>