[Elecraft] Missing first piece of dash or dot when sending CW with K3S USB input with Wintest.

[Don Wilhelm]

Gilles,

As long as you are dependent on an application running on the PC for 
timing, you will have similar problems. Windows prioritizes the timing 
of events to its own pleasure, and servicing the application is not 
necessarily of the highest priority. It is normally not noticed, but 
with things like CW keying where timing is critical, the operating 
system gets in the way.
Back in the old DOS days when the currently running application had the 
full attention and command of computer resources, this was not a problem 
- back then, there was no "background processing".
The Winkey is the solution normally employed to attack that problem.

If you do not want to invest in the Winkeyer, then confine yourself to 
running only the application that is doing the CW keying.  The more 
applications you have running at the same time, the worse the contention 
for computer resources becomes.

73,
Don W3FPR

On 7/13/2017 6:31 PM, VA2EW wrote:
> Hi all,
> 
> Last WE during the IARU HF I have tested the use of the USB input of the 
> K3S in replacement of a RIGEXPERT TI-5 box.
> 
> Everything looked great until I experimented that sometimes randomly the 
> beginning of the first dash or dot was missing when sending CW via 
> Wintest under Windows 10.
> 
> I guess it is a real-time related problem with USB under Windows.
> 
> Is there someone who have a solution to fix that or must I come back to 
> the RIGEXPERT or eventually add a Winkeyer ?
>