<div dir="ltr">Chris,<div><br></div><div>OK I finally read the enclosure from your email. You should post it on the web because it explains things very clearly.</div><div><br></div><div>You have to understand that Win-Test 4.10 and earlier had a bug in the WinKey code. The old Win-Test code was changing the WinKey "weight" setting via <03> (Set weighting), which proportionally changes the length of every dot and every dash, but that was a mistake. The new version of Win-Test (4.11) changes the dot/dash "ratio" setting via <17> (Set dit/dah ratio), which was what it was supposed to be doing all along.</div>
<div><br></div><div>So, the old Win-Test code was doing it wrong. It was adjusting the wrong WinKey parameter ("weight").</div><div><br></div><div>The new Win-Test code is doing it right. It is adjusting the correct parameter ("ratio").</div>
<div><br></div><div>Even though Win-Test calls the menu "Weight", it should be called "Ratio" to match the intended purpose. In Win-Test, "weight" 3.2 means change the WinKey dot/dash <i><b>ratio</b></i> to 1:3.2, so every dash is 3.2 times longer than a dot. 3.0 means make dashes three times longer than a dot. Use 3.0 from now on. Do not use 2.0 any more. Do not use the old version of Win-Test any more.</div>
<div><br></div><div>There now is <b>no way</b> to adjust the WinKey "weight" setting in Win-Test any more. You can only adjust the WinKey "ratio" setting.</div><div><br></div><div>Frankly, neither weight nor ratio are good enough to compensate for keying issues found in most radios. What works well at one speed may sound bad at another speed.</div>
<div><br></div><div>For <i>both</i> the internal LPT/COM keyer and the WinKey, it would be <i>really nice</i> if Win-Test could support adjustments of Keying Compensation (WinKey command <11>"Set Key Comp"), and 1st element extension (<10> "Set 1st Extension"). These are very valuable settings that increase the length of every dot or dash, or only the first dot or dash, by a <i>fixed amount</i> that does <i>not</i> vary with the keying speed. That is the proper way to compensate for radios that shorten the first element, or every element, by a fixed amount, as most radios do, while maintaining a perfect 1:3 ratio over the air at all contest speeds.</div>
<div><br></div><div>If you are using a standone WinKey USB device and an FT-1000MP Mark V Field, you should set Comp to about 6 ms using the WinKey control program, then exit and restart Win-Test, the go back and see if the setting is still 6 ms. Leave weight at 3.0:1 (or "50/50" in the WinKey menu).</div>
<div><br></div><div>I suggest using 6 ms keying compenstation based on the keying waveform plotted on Page 15 of this <a href="http://www.arrl.org/files/file/protected/Group/Members/ProductReview/pdf/lab/mark-v-field.pdf" target="_blank">ARRL FT-1000MP Mark V Field Expanded Test Report</a>. This radio appears to shorten every dot and dash by about 6 ms, but that was in QSK mode. You may not need it in semi-breakin mode. The Elecraft K3 has the same issue in QSK mode.</div>
<div class="gmail_extra"><br clear="all"><div>73,<div>Bob, N6TV</div></div><div><div><br><div class="gmail_quote">On Wed, Nov 13, 2013 at 12:35 PM, SP5KP <span dir="ltr"><<a href="mailto:sp5kp@wp.pl" target="_blank">sp5kp@wp.pl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><u></u><div bgcolor="#ffffff"><div><font face="Verdana">Hi Bob</font></div>
<div><font face="Verdana"></font> </div><div><font face="Verdana">Tks for interest oneself problem.</font></div><div><font face="Verdana"></font> </div><div><font face="Verdana">Im using WinKey2 USB with FT1000MP Field.</font></div>
<div><font face="Verdana"></font> </div><div><font face="Verdana"><strong>My setting from WT for WinKey -> CWweight=2</strong></font></div><div><font face="Verdana"></font> </div><div><font face="Verdana">With WT 4.10 and also for WT4.11.rev Revison 525/2013/07/29 </font> <font face="Verdana">file:wt_dev_2013_07_29-20_46_48.zip</font></div>
<div><font face="Verdana">CW trnasmision is very good.</font></div><div><font face="Verdana"></font> </div><div><font face="Verdana">From WT4.11.rev Revison 526/2013/08/13 <font size="3"> </font><font face="Verdana">file:wt_dev_2013_08_13-16_48_50.zip and present WT 4.11</font></font></div>
<div><div><font face="Verdana">CW trnasmision is very bad.</font></div><div><font face="Verdana"></font> </div><div><font face="Verdana">I am careful that problem is in code of programme from WT4.11.rev Revison 526/2013/08/13 <font size="3"> </font></font></div>
<div><font face="Verdana"></font> </div><div><font face="Verdana">See enclosure in previous private email for you.</font></div><div><div><font face="Verdana"></font> </div><div><font face="Verdana">-----</font></div><div>
<font face="Verdana"></font> </div><div><font face="Verdana">Pozdrawiam<br>VY 73!</font></div><div> </div><div><font face="Verdana">Krzysztof "Chris"<br>SP5KP, 3Z5W, 3Z40KP, ex SN5N</font> </div></div></div><div>
Message -----</div><blockquote style="padding-right:0px;padding-left:5px;margin-left:5px;border-left-color:rgb(0,0,0);border-left-width:2px;border-left-style:solid;margin-right:0px"><div style="background-color:rgb(228,228,228);font-size:10pt">
<b>From:</b> <a title="n6tv@arrl.net" href="mailto:n6tv@arrl.net" target="_blank">Bob Wilson, N6TV</a></div><div style="font-size:10pt"><b>To:</b> <a title="support@win-test.com" href="mailto:support@win-test.com" target="_blank">Win-Test Reflector</a></div>
<div style="font-size:10pt"><b>Sent:</b> Wednesday, November 13, 2013 7:31 PM</div><div style="font-size:10pt"><b>Subject:</b> Re: [WT-support] Fw: Very bad CW transmission in WT 4.11 with WinKey</div><div><div><br></div>
<div dir="ltr">In the WinKey Configuration menu (text command shortcut: WKSETUP [Enter]), change PTT LEAD and TAIL to 0 ms. I think the default is 50 ms, which can make the WinKey keying sound bad.<div><br></div><div>If you installed WT 4.11 on a new computer or wiped out your WT.INI file, the deafult of 50 ms would be used.</div>
<div><br></div><div>Also, what type of transceiver are you using? Elecraft K3 needs special handling.</div><div class="gmail_extra"><br clear="all"><div>73,<div>Bob, N6TV</div></div></div></div></div></blockquote></div>
</blockquote>
</div></div></div></div><div class="gmail_extra"><br></div></div>