<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16735" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">I should have followed this more closely, but notice the
problem of failure of the MK2R Winkeyer shortly after start-up of Win-Test. I've
experience similar issues and have discover part of the
problem.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">One the problems I've experience is when starting the Device
Router the Winkeyer port settings under the Ports tab are gone, i.e. ports are
none. So I reload the preset settings for the particular setup and things work
better.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">However, it is not 100%. Sometimes when opening Win-Test,
something happens to the MK2R WinKeyer settings that when I try sending a
message only the first character is sent and it doesn't work any more. When this
happens I sometimes find the MK2R WinKeyer port has reverted back to
none.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">I'm using the Device Router 7.1.5. I'm not sure if this
occurred after an update to the Device Router or after a update to
Win-Test.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">In the process of trying to figure out what is happening I at
least determine a method to make sure I have functional CW about 98% of the time
when starting Win-Test. May be kind of goofy but it works. Briefly here it
is.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">Open Device Router</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">Reload Preset settings</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">Do not minimize Device Router</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">Manually send short CW (test, call sign,
etc)</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">Now open Win-Test</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">Once Win-Test is running press a function key to send
message.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">Keep Diver Router Window open for a while</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">If the message is properly sent I usually will have no
problems after that. I also found that I need to keep the device router open for
a while until I've made a few QSO's. Once a few QSO's are in the log then you
can minimize the device router with little risk of a failure. However,
minimizing the router right a way tends to increase the likelihood of loosing
the ability to send CW from the computer.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">Hopefully this helps,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">Bill</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New">AC0W</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=903361903-27012009><FONT
face="Courier New"></FONT></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> support-bounces@win-test.com
[mailto:support-bounces@win-test.com] <B>On Behalf Of </B>Bob Wilson,
N6TV<BR><B>Sent:</B> Monday, January 26, 2009 9:06 PM<BR><B>To:</B>
support@win-test.com<BR><B>Subject:</B> Re: [WT-support] WT winkey MK{2R}
problems<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=gmail_quote>2009/1/26 Nick F5VIH/SV3SJ <SPAN dir=ltr><<A
href="mailto:f5vih@sinanis.com">f5vih@sinanis.com</A>></SPAN><BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV class=gmail_quote>
<DIV>The table is stable and I am very calm during a contest :-))) Though,
I'll try to crosscheck the big-bang theory you suggest, next time
:-)</DIV></DIV></DIV></BLOCKQUOTE>
<DIV><BR>:-)<BR> <BR></DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV class=gmail_quote>
<DIV></DIV>
<DIV></DIV>
<DIV>The problem occurs with a fairly high chance at the very startup of WT
(and synergy). Sometimes several restarts (wt, router and MK2R) are needed. It
never occurs once wt is running!</DIV></DIV></DIV></BLOCKQUOTE>
<DIV><BR>Oh, so it is only a start-up issue? Do you have the WinKey
sending CW while you start Win-Test, then it halts? I think Win-Test or
microHAM router does a Win-Key "reset" when it initializes communications at
start-up, so that could cancel active CW. You can see this by pressing the
microHAM [MON] (monitor) button next to the WinKeyer2 port, then on the next
panel click [Start], then start Win-Test. <BR><BR>Capturing this Winkeyer2
log data is very valuable for diagnosing WinKey problems.<BR><BR>73,<BR>Bob,
N6TV<BR></DIV></DIV><BR></BODY></HTML>