Re: Winkey and <stop>


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:

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 :

"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.....


~iain / N6ML

Join to automatically receive all group messages.