[WriteLog] Winkey and Writelog Issues

[Joe Subich, W4TV]

> 2. If I send some message on the paddle, immediately followed 
> by an F key (for example I send 73 TU followed by the F key 
> with callsign message) then the F key is not always 
> recognised, unless I leave a deliberate pause after my paddle 
> generated message. 

There is a finite amount of time - generally one word space - 
that the WinKey chip will signal that the paddles are in use 
following their use.  

WriteLog and many other programs use the "paddle busy" signal as 
an "escape" to dump any message being transmitted ... it is 
likely that the "busy" response from Winkey is causing Writelog 
to dump all or part of the message if you activate the F-key 
too soon.  There is also probably nothing that can be done in 
the program to change that behavior if "paddle interrupt" is 
to be maintained.  The program interrupt is independent of 
any paddle interrupt built into the WinKey itself. 

73, 

   ... Joe, W4TV 
  



> -----Original Message-----
> From: writelog-bounces at contesting.com 
> [mailto:writelog-bounces at contesting.com] On Behalf Of John 
> Warburton G4IRN
> Sent: Wednesday, February 10, 2010 3:21 AM
> To: Writelog Reflector
> Subject: [WriteLog] Winkey and Writelog Issues
> 
> 
> All
> 
> Please excuse me if these issues have come up on the 
> reflector before, I have tried to dig them out without any success.
> 
> I am using a Microkeyer II unit with Writelog version 10.74 
> and get the following issues when running CW. I friend of 
> mine has tried this with a vanilla K1EL Winkey unit and come 
> up with similar results.
> 
> 1. If a enter a partial call, press the exchange key and then 
> carry on typing the call, the final part of the call is not 
> always picked up in the outgoing message. There seems to be a 
> point in the outgoing message where new characters cannot be 
> picked up, even if it hasn't got to the end of sending the 
> original typed characters.
> 
> 2. If I send some message on the paddle, immediately followed 
> by an F key (for example I send 73 TU followed by the F key 
> with callsign message) then the F key is not always 
> recognised, unless I leave a deliberate pause after my paddle 
> generated message. Not much fun doing that in the heat of a contest.
> 
> 3. Occasionally, I won't wait quite long enough for the 
> required pause for the F key to send and it will send just 
> part of the message buffer (but if I don't wait at all, then 
> it sends nothing).
> 
> I'm wondering if I have some parameters set up incorrectly? 
> Everything is set at default at the moment. Any assistance 
> would be appreciated.
> 
> Thanks
> 
> John G4IRN.
> 
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com 
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/