Re: WinWarbler


Joe Subich, W4TV
 

Why not? If he wants to emulate a WinKeyer, and the software that he
needs to interact with supports the latest version of the protocol,
being fully compliant with that protocol should be sufficient.
Because WK3 does not require the CMD MODE OFF command when starting.
WK3 fores command mode off whenever the serial port is closed - that
was not the case with WK1 (and perhaps WK2 - I'd have to go back to
the developers/programmers documentation). There are other subtle
differences in behavior (e.g. the behavior of PTT tail and a difference
PTT delay for paddle vs. ASCII data) among the three WK families (as
well as among firmware versions *within* families).

The "WK" protocol is not monolithic and can't be treated as such.

73,

... Joe, W4TV


On 2020-08-25 1:12 PM, iain macdonnell - N6ML wrote:
On Tue, Aug 25, 2020 at 5:05 AM Joe Subich, W4TV <lists@subich.com> wrote:


On 2020-08-25 3:14 AM, sm6fpg wrote:
I'm trying to understand the documentation for WK3 but obviously I'm
failing.
You can not limit yourself to WK3. There are significant issues in
maintaining backward compatibility with WK 1 and WK 2. Study the
documentation on *ALL THREE* versions to understand the full range
of requirements for "WinKey compatibility".
Why not? If he wants to emulate a WinKeyer, and the software that he
needs to interact with supports the latest version of the protocol,
being fully compliant with that protocol should be sufficient.
73,
~iain / N6ML

On 2020-08-25 3:14 AM, sm6fpg wrote:
I'm trying to understand the documentation for WK3 but obviously I'm failing.
I'll see if I can find any source code for some programs to try to understand it all better!
Thank you for your commitment!

73,
SM6FPG/Bo

Join DXLab@groups.io to automatically receive all group messages.