No subject

> keyer (SO2R scenarios) message. Note that the correct variable is
> "$MK2R=" without quotes, of course.


Thanks.  It makes sense to me now.  I just made few minor updates to the
Wiki pages to try to clarify this.

73,
Bob, N6TV

------=_Part_4907_12794490.1211318247669
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Tue, May 20, 2008 at 12:33 PM, Laurent HAAS - F6FVY &lt;<a href="mailto:f6fvy at free.fr">f6fvy at free.fr</a>&gt; wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
AFAIK, the microHam router monitors the serial stream and dumps all WK<br>
commands that can be set by using the router.</blockquote><div><br>According to the release notes &quot;The WinKey and PTT/CW events of the Win-Test integrated keyers are not handled by the protocol.&quot;&nbsp; In other words, you have to send commands to the WinKey virtual serial port, rather than the MK2R control port, and there&#39;s no way to do that with the $MK2R=<i>cmd</i> macro.<br>
<br>So, other than the limited Options, WinKey dialog, there&#39;s no way to send commands to a WinKey.&nbsp; So a $WINKEY=<i>cmd</i> macro would be a really nice addition.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">