[WT-support] WT winkey MK{2R} problems

[Bob Wilson, N6TV]

Bill,

Very interesting!  Thanks for your post.  I am still using an older version
of Router (5.1?) so maybe that is why I haven't seen the problem.

Once you have selected your preset, maybe it would help to select "Device |
Store as Power-Up Settings" from the Router menu?  That way the WinKey port
would always be available, as soon as you power on the MK2R.

73,
Bob, N6TV

2009/1/26 AC0W <ac0w at charter.net>

>  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.
>
> 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.
>
> 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.
>
> 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.
>
> 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.
>
> Open Device Router
> Reload Preset settings
> Do not minimize Device Router
> Manually send short CW (test, call sign, etc)
> Now open Win-Test
> Once Win-Test is running press a function key to send message.
> Keep Diver Router Window open for a while
>
> 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.
>
> Hopefully this helps,
>
> Bill
> AC0W
>
>
>
>  ------------------------------
> *From:* support-bounces at win-test.com [mailto:support-bounces at win-test.com]
> *On Behalf Of *Bob Wilson, N6TV
> *Sent:* Monday, January 26, 2009 9:06 PM
> *To:* support at win-test.com
> *Subject:* Re: [WT-support] WT winkey MK{2R} problems
>
>  2009/1/26 Nick F5VIH/SV3SJ <f5vih at sinanis.com>
>
>>  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 :-)
>>
>
> :-)
>
>
>>   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!
>>
>
> 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.
>
> Capturing this Winkeyer2 log data is very valuable for diagnosing WinKey
> problems.
>
> 73,
> Bob, N6TV
>
>
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20090126/52dbdc00/attachment.htm