[WT-support] WinKey

[Bob Wilson, N6TV]

On Sat, Aug 29, 2009 at 3:37 PM, SM5AJV <sm5ajv at qrq.se> wrote:

>  N1MM sets up a WAIT_MASK instead. I think this may be the reason
> behind the bad response of the paddle when as long as WT is running.
>

What's a "wait mask"?  I can't find anything about wait masks in the
WinKeyUSB manual.

I wonder if these problems are unique to the WKUSB product made by K1EL?
 Are you using the supplied FTDI Virtual COM port drivers?  Perhaps the
problems are unique to that driver.

Is anyone using a WinKey in a microHAM device experiencing this problem?
 I've never seen it myself (using MK2R+ with WinKey V22).  But I'm obviously
using a different driver.

Perhaps at boot time WindowsXP, or some other software, writes some data to
the virtual COM port that you are using for the WinKey, and that sets it to
Farnsworth mode.

There a number of WinKey test
programs<http://k1el.tripod.com/software.html>available at the K1EL
site.  Maybe one of them can reset the keyer out of
Farnsworth mode.  Once you get it fixed, power down and power up your PC
with the WinKey disconnected.  Then after Windows boots, plug in the WinKey
USB.  Then start Win-Test.

You might trying using a different virtual COM port to see if that makes any
difference.

73,
Bob, N6TV
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20090831/1ab40667/attachment.htm