[WT-support] WinKey

[SM5AJV]

The WinKeyUSB with WT is a real pain and I have tried to further
investigate
what's happening.

I have been using portmon.exe to monitor the COM communication between
WT and Winkeyer and compared who N1MM is behaving in the same
situation.

One big difference is that WT is polling the Winkeyer more frequently
compared
to N1MM. 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.

Maybe this also have some dependency towards the Farnsworth problem?
I could not see anything in the two dumps that are dealing with the
Farnsworth
at all. Perhaps all is related to some timing issue?

I would like to hear what the developers think about the Winkeyer issue?
I can provide communications dumps from portmon.exe  if you are interested
to compare the communications.

73
Ingo SM5AJV / SE5E


SM5AJV wrote:
> I can also confirm the problems with speed and Farnsworth or whatever
> causes this. At speeds above 30WPM the CW sounds OK. At speeds
> lower than 30WPM it sounds really crappy.
>
> I have found another issue when using the paddles. The CW sounds very
> much like having too long spaces between characters. I think this is
> regardless
> of speed. I think somethings is set up wrong during initialization.
>
> I am using WT 4.x.x and WK2USB
>
>
> So if this isn't fixed you can easily tell who is using WT with a
> WinKeyer by
> just listening :-)
>
> Please fix it soon!
>
> 73
> Ingo SM5AJV / SE5E
>
>
> Eugene Kuznetsov wrote:
>   
>> Bob, N6TV:
>>
>>   
>>     
>>> From the WinKey manual, it sounds like your keyer has somehow been
>>> set up to use "Farnsworth Mode" at 30 wpm or less:
>>>     
>>>       
>>   
>>     
>>> Set Farns WPM <0D><nn> nn is in the range of 10-99
>>>     
>>>       
>>   
>>     
>>> Example: <0D><12> for Farnsworth=18 WPM
>>>     
>>>       
>> Thanks for an explanation! WinKey has too many features, it's really
>> difficult to know and understand all of them.
>>
>>   
>>     
>>> Somehow you need to reset your WinKey and the problem should go
>>> away.  Note that in ASCII <0D> is the carriage return character (CR)
>>> and <20> is the ASCII blank (32 decimal), so maybe in Win-Test
>>> keyboard mode (Alt-K), if you type [Enter] or [Ctrl-Enter] and a
>>> blank, it sets the WinKey to Farnsworth mode at 32 WPM or less?
>>>     
>>>       
>> Reset doesn't help.
>> There is no possibility to send CR to Winkey from Win-Test.
>> I think it occurs during WinKey initialization from Win-Test.
>>
>> I checked WinKey with N1MM and found that it has worked without
>> Farnsworth feature.
>>
>> So, developers, please help!:)
>>
>> 73! Eugene RK1AA
>>
>>   
>>     
>
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
>
>