<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Thanks for the info.<br>
<br>
I know the built-in PTT and CW keying of modern radios, but I like
the cw keying independent form windows load.<br>
And second, I use a MKII for PTT sequencing PA & LNA and this
works only in combination with the internal WinKey.<br>
<br>
The behaviour whether internal WinKey in MKII or stand alone WinKey
is identical.<br>
<br>
With a stand alone WinKey (V9) and WinKey properties, as shown by
bob below, after every space in text, PTT switches.<br>
Paddle hang time is "Fixed Tail" to 30ms.<br>
When I set the PTT-Tail to 100ms, then there is no more PTT
switching.<br>
If I set the PTT tail between 1.00 and 2.00 word spacing, PTT will
also switch again after each space.<br>
This is regardless of the speed set.<br>
<br>
The internal WinKey in MKII (V10) behaves absolutely identically.<br>
In MKII PTT - DeviceRouterSetup, there are the same setup options.<br>
Also there, only with a fix PTT-Tail time about 100ms and more, PTT
doesn't switches.<br>
<br>
One request, can someone check this PTT behaviour with this PTT-Tail
2.0 wordspace setting?<br>
<img src="cid:part1.gFSBbd0e.gkZPHt08@googlemail.com" alt=""><br>
Does this behaviour also occur on other setups?<br>
<br>
A long PTT tail prevents but does about the long tail-time not solve
this issue.<br>
<br>
73, Sigi<br>
DL8NAS<br>
<br>
<div class="moz-cite-prefix">Am 31.10.2024 um 20:03 schrieb Bob
Wilson, N6TV:<br>
</div>
<blockquote type="cite"
cite="mid:CAOmNKGJ3eqiowJJMJUrOdXq2Ne0wE=8dsSgpm9cv4VhnPEuX0w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">If you disconnect the CW cable from the MKII, the
one connected to your rig's KEY jack, is PTT still activated
when you play a message (with no CW, just key down, no RF)?
If the rig doesn't go into TX mode, it means the WinKey PTT
connection is not enabled or not working, and everything is
working as set by the rig's "CW VOX Delay".</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Check the microHAM Router settings regarding
"winKey PTT" settings.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">You may need to set "Second output (pin 5)" to
PTT to make it work:</div>
<div dir="ltr"><br>
</div>
<img src="cid:part2.elbW0scX.5elmu3gk@googlemail.com"
alt="image.png" width="562" height="342" class=""><br>
<div dir="ltr">
<div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">73,
<div>Bob, N6TV</div>
</div>
</div>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Oct 31, 2024 at
8:04 AM Siegfried Kleinöder <<a
href="mailto:s.kleinoeder@googlemail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">s.kleinoeder@googlemail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello
Larry,<br>
<br>
the K1EL WinKey switches PTT during CQ.<br>
When I send my CQ message to WinKey, after every space (20h)
in text, <br>
the PTT line switches!<br>
<br>
This is an absolute disaster, when we work with PA and
Preamps on coming <br>
VHF CW CT.<br>
<br>
I thought it worked fine before, I checked versions 4.40 to
4.54, same <br>
problem.<br>
This is independent of the speed.<br>
<br>
I also tested it with UCXLog. It works correctly there.<br>
<br>
Attached are two log files recorded with MK-II WinKey
Monitor.<br>
One WT-4.54 and one UCX-Log.<br>
UCX fills the pauses with 7Ch characters.<br>
<br>
Best 73, Sigi<br>
DL8NAS-- <br>
support mailing list<br>
<a href="mailto:support@win-test.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">support@win-test.com</a><br>
<a
href="https://lists.win-test.com/cgi-bin/mailman/listinfo/support"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.win-test.com/cgi-bin/mailman/listinfo/support</a><br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>