[WT-support] WinKey

[sm5ajv at qrq.se]

Thanks Bob for your reply!

The WAIT_MASK was reported by portmon.exe and I think it
is some low level setting in the serial communications.
I think its used to set up an interrupt for changes in the
serial communications, so the host process don't have to
poll the serial port all the time. It has nothing to do
with the WK protocol.

I am using the supplied driver from K1EL.

N1MM is working with no problem on the very same computer,
so I don't think it is a driver problem. For instance
N1MM is starts the communications with several 'NULL' commands
as recommended by K1EL, while WT doesn't.

Still when using portmon.exe I monitor the WK-port and
I can't see any other process communicating with the WK.
And I haven't seen any process issuing the Farnsworth
command.

I am not sure, but I have not found any way of make save
of settings in the HOST MODE. Settings done in STANDALONE
MODE are not valid in HOST MODE.


I am still curious to hear the developers view on this?
And I am quite interested to get this working for the upcoming
Scandinavian Activity Contest.

73
Ingo SM5AJV / SE5E


> 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
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>