Winkey and <stop>


f6gcp
 

Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite ok for CW operation using the keyer, and to avoid trcv to go to receive (of course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Using the opcode "stop" (while running the winkey test software), the PTT is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty return to RX (assuming VOX is not used!) or to create a command <stop_immediat> (or similar) for such purpose?

thanks


iain macdonnell - N6ML
 

On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@...> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a ‘PTT off’ buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

73,

~iain / N6ML


f6gcp
 

Hi Ian,

thanks on information. I have checked running Winkey2 software, and it shows firmware 2.3.
A <winkeycmd:> could be nice, for advanced settings (Up to now, I don't know what I can do with this but spot CW... later may be...)

73 - Pat

--- In dxlab@..., iain macdonnell - N6ML <ar@...> wrote:

On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@...> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a `PTT off' buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

73,

~iain / N6ML


Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Sunday, August 05, 2012 5:45 AM
To: dxlab@...
Subject: [dxlab] Winkey and <stop>


Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Using the opcode "stop" (while running the winkey test software), the PTT is
immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?

What commands are sent to the WinKey when the "WinKey Test Software" is
directed to "stop"?

73,

Dave, AA6YQ


iain macdonnell - N6ML
 

Hi Pat,

Then I think you just need to reduce your "Tail" setting, and increase
"Paddle Hang".

GL/73,

~iain / N6ML

On Sun, Aug 5, 2012 at 1:48 PM, f6gcp <f6gcp@...> wrote:



Hi Ian,

thanks on information. I have checked running Winkey2 software, and it
shows firmware 2.3.
A <winkeycmd:> could be nice, for advanced settings (Up to now, I don't
know what I can do with this but spot CW... later may be...)

73 - Pat

--- In dxlab@..., iain macdonnell - N6ML <ar@...> wrote:



On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@...> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is
quite
ok for CW operation using the keyer, and to avoid trcv to go to
receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as
set
to 500ms is a too long (the pile_up "TU" to confirm qso could be
missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a `PTT off' buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the
PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to
immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

73,

~iain / N6ML


f6gcp
 

Hi,
by using Winkeyer2 software, it sends "clrPTT" [N].
73
Pat

--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Sunday, August 05, 2012 5:45 AM
To: dxlab@...
Subject: [dxlab] Winkey and <stop>


Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Using the opcode "stop" (while running the winkey test software), the PTT is
immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?

What commands are sent to the WinKey when the "WinKey Test Software" is
directed to "stop"?

73,

Dave, AA6YQ


f6gcp
 

Hi,
I will have a look on this... "Hang" parameter could be the parameter I missed in WW. Currently I don't have the same bahaviour while running CW when WW is openned than running Winkey in standalone...
Pat

--- In dxlab@..., iain macdonnell - N6ML <ar@...> wrote:

Hi Pat,

Then I think you just need to reduce your "Tail" setting, and increase
"Paddle Hang".

GL/73,

~iain / N6ML


On Sun, Aug 5, 2012 at 1:48 PM, f6gcp <f6gcp@...> wrote:



Hi Ian,

thanks on information. I have checked running Winkey2 software, and it
shows firmware 2.3.
A <winkeycmd:> could be nice, for advanced settings (Up to now, I don't
know what I can do with this but spot CW... later may be...)

73 - Pat

--- In dxlab@..., iain macdonnell - N6ML <ar@> wrote:



On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is
quite
ok for CW operation using the keyer, and to avoid trcv to go to
receive (of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as
set
to 500ms is a too long (the pile_up "TU" to confirm qso could be
missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a `PTT off' buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the
PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to
immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

73,

~iain / N6ML


Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Sunday, August 05, 2012 6:34 PM
To: dxlab@...
Subject: [dxlab] Re: Winkey and <stop>


Hi,
by using Winkeyer2 software, it sends "clrPTT" [N].

There is no clrPTT command mentioned in the Winkeyer2 (v23) datasheet. Do
you mean "PTT Off", which is <18><0> ?

73,

Dave, AA6YQ


f6gcp
 

Hi Dave,
I have monitored Winkey2 application and the message starts with 18 01
and finishes with 18 00

18 01 20 44 45 20 46 36 47 43 50 20 54 55 20 1C .. DE F6GCP TU .
23 35 4E 4E 20 35 4E 4E 1C 14 20 54 55 18 00 #5NN 5NN.. TU..

The "clrPTT" is a command in the software (Winkey2.exe) only.

in WW, the "18 00" (as well as 18 01) does not exist
00 04 57 00 04 57 00 02 0A 15 05 05 1B 7F 03 32 ..W..W........2
04 03 32 10 14 11 00 17 32 12 32 0D 00 0E 45 01 ..2.....2.2...E.
05 02 1A 09 05 15 15 15 15 15 15 15 15 09 05 02 ................
1A 15 20 54 55 20 46 36 47 43 50 20 35 4E 4E 54 .. TU F6GCP 5NNT
55 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 U...............

73 - Pat




73 - Pat

--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Sunday, August 05, 2012 6:34 PM
To: dxlab@...
Subject: [dxlab] Re: Winkey and <stop>


Hi,
by using Winkeyer2 software, it sends "clrPTT" [N].

There is no clrPTT command mentioned in the Winkeyer2 (v23) datasheet. Do
you mean "PTT Off", which is <18><0> ?

73,

Dave, AA6YQ


Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Monday, August 06, 2012 6:32 PM
To: dxlab@...
Subject: [dxlab] Re: Winkey and <stop>


Hi Dave,
I have monitored Winkey2 application and the message starts with 18 01
and finishes with 18 00

18 01 20 44 45 20 46 36 47 43 50 20 54 55 20 1C .. DE F6GCP TU .
23 35 4E 4E 20 35 4E 4E 1C 14 20 54 55 18 00 #5NN 5NN.. TU..

The "clrPTT" is a command in the software (Winkey2.exe) only.

in WW, the "18 00" (as well as 18 01) does not exist
00 04 57 00 04 57 00 02 0A 15 05 05 1B 7F 03 32 ..W..W........2
04 03 32 10 14 11 00 17 32 12 32 0D 00 0E 45 01 ..2.....2.2...E.
05 02 1A 09 05 15 15 15 15 15 15 15 15 09 05 02 ................
1A 15 20 54 55 20 46 36 47 43 50 20 35 4E 4E 54 .. TU F6GCP 5NNT
55 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 U...............

In the PTT panel on the CW tab of WinWarbler's Configuration window,
1. check the "assert PTT during CW" box

2. set the "lead time" to the desired PTT lead time

3. set the "lag time" to 0

73,

Dave, AA6YQ


f6gcp
 

Hi,
1. check the "assert PTT during CW" box
Already check
2. set the "lead time" to the desired PTT lead time
3. set the "lag time" to 0
In that case, running by Macro is OK, however, by using the keyer the Trcv goes to receive too quicky (if any delay on sending characters), which is bad for the amplifier (or anyother devices such as pre-amplifier)...

According to WinKey2 manual (Page 9), and the trace "09 05" shows a Hang time (bit 5 WK2 PinCFG) of 0.
How to set the "hang" time in WW ?

73 - Pat




--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Monday, August 06, 2012 6:32 PM
To: dxlab@...
Subject: [dxlab] Re: Winkey and <stop>


Hi Dave,
I have monitored Winkey2 application and the message starts with 18 01
and finishes with 18 00

18 01 20 44 45 20 46 36 47 43 50 20 54 55 20 1C .. DE F6GCP TU .
23 35 4E 4E 20 35 4E 4E 1C 14 20 54 55 18 00 #5NN 5NN.. TU..

The "clrPTT" is a command in the software (Winkey2.exe) only.

in WW, the "18 00" (as well as 18 01) does not exist
00 04 57 00 04 57 00 02 0A 15 05 05 1B 7F 03 32 ..W..W........2
04 03 32 10 14 11 00 17 32 12 32 0D 00 0E 45 01 ..2.....2.2...E.
05 02 1A 09 05 15 15 15 15 15 15 15 15 09 05 02 ................
1A 15 20 54 55 20 46 36 47 43 50 20 35 4E 4E 54 .. TU F6GCP 5NNT
55 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 U...............

In the PTT panel on the CW tab of WinWarbler's Configuration window,
1. check the "assert PTT during CW" box

2. set the "lead time" to the desired PTT lead time

3. set the "lag time" to 0

73,

Dave, AA6YQ


Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
iain macdonnell - N6ML
Sent: Sunday, August 05, 2012 1:54 PM
To: dxlab@...
Subject: Re: [dxlab] Winkey and <stop>


On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@...> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive
(of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a �PTT off� buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

"Hang time" is controlled by bits in the WinKey's PINCFG register. Other
bits in this register control PTT, Sidetone, and Port selection; thus
WinWarbler's manipulation of the PINCFG register would override the effect
of any WinKey command to control "Hang time" issued by a <winkeycmd: ...>
macro command, were such a macro command provided.

73,

Dave, AA6YQ


Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
f6gcp
Sent: Tuesday, August 07, 2012 5:11 AM
To: dxlab@...
Subject: [dxlab] Re: Winkey and <stop>


Hi,
1. check the "assert PTT during CW" box
Already check
2. set the "lead time" to the desired PTT lead time
3. set the "lag time" to 0
In that case, running by Macro is OK, however, by using the keyer the Trcv
goes to receive too quicky (if any delay on sending characters), which is
bad for the amplifier (or anyother devices such as pre-amplifier)...

According to WinKey2 manual (Page 9), and the trace "09 05" shows a Hang
time (bit 5 WK2 PinCFG) of 0.
How to set the "hang" time in WW ?

The current version of WinWarbler provides no control over a WinKey
paddle's hang time. I've sent you a new version of WinWarbler that provides
this capability. Please let me know how it goes.

73,

Dave, AA6YQ


iain macdonnell - N6ML
 

On Wed, Aug 8, 2012 at 9:05 PM, Dave AA6YQ <aa6yq@...> wrote:
AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
iain macdonnell - N6ML
Sent: Sunday, August 05, 2012 1:54 PM
To: dxlab@...
Subject: Re: [dxlab] Winkey and <stop>


On Sun, Aug 5, 2012 at 2:45 AM, f6gcp <f6gcp@...> wrote:



Hi,
Winkey is set with a "tail" time of 500ms and PTT asserted, which is quite
ok for CW operation using the keyer, and to avoid trcv to go to receive
(of
course, I should say the amplifier!)
Using macro command is nice to run in a pile up, however, the tail, as set
to 500ms is a too long (the pile_up "TU" to confirm qso could be missed!).
Hi Pat,

What version of WinKeyer do you have? There was a change between v2.2
and v2.3 that significantly helps with this situation. From
http://k1el.tripod.com/files/Winkey23changes.pdf :

"Hang mode is now independent of tail delay: Hang Time applies only to
CW sent by paddle. Tail
delay applies only to CW sent by the host or by standalone message. It
is no longer necessary to
disable Hang Time setting controls in the GUI when Tail is set to a
non-zero value. This is because
the settings are independent now. (Side note: A long Tail time can be
truncated early by appending
a ‘PTT off’ buffered command /U0 to the message stream)"

It's worth upgrading (requires chip replacement) if you are
experiencing this problem, IMO.


Using the opcode "stop" (while running the winkey test software), the PTT
is immediatly released whatever the tail set time.
In a macro, is is possible, while <stop> command is used, to immedialty
return to RX (assuming VOX is not used!) or to create a command
<stop_immediat> (or similar) for such purpose?
That may be possible to implement (using the "/U0" command mentioned
above). Only Dave can say. Actually, it may be better to implement a
"<winkeycmd: ...>" so arbitrary commands could be sent.....

"Hang time" is controlled by bits in the WinKey's PINCFG register. Other
bits in this register control PTT, Sidetone, and Port selection; thus
WinWarbler's manipulation of the PINCFG register would override the effect
of any WinKey command to control "Hang time" issued by a <winkeycmd: ...>
macro command, were such a macro command provided.
I was suggesting the possibility using a <winkeycmd: ...> feature to
send a "stop immediately" command, in this case ... and thinking that
there may be other arbitrary commands that one may sometimes want to
send....

73,

~iain / N6ML