[WT-support] Winkey problem

[Frank, IZ7AUH]

Thanks for a good reply I resolve to use 2 com one for cw on flex and one more for ic7400 no WK! 

Why no flexradio on radio setup? I don't like use omnirig

Francesco Giacoia
Inviato da iPhone

Il giorno 29/mag/2011, alle ore 19:49, "Bob Wilson, N6TV" <n6tv at arrl.net> ha scritto:

> On Sun, May 29, 2011 at 4:05 AM, Frank, IZ7AUH/AK1CQ <iz7auh at gmail.com> wrote:
> " The virtual serial port pins can be used for CW on/off keying and PTT, or for high speed SO2R active radio control of a microHAM, EZMaster (?) or DXDoubler box via "Classic Auto Control" (set device type to Other interface)."
> 
> I don't understand where available all information about, please give me a link.
> 
> There are many Win-Test sample configurations documented here:
> 
> http://www.microham-usa.com/support.html
> 
> But unfortunately, there is no example explaining how to use COM ports for SO2R switching.
> 
> About a year ago OM7ZZ documented the solution here:
> 
> http://lists.f5mzn.org/pipermail/support/2010-May/079591.html
> 
> At SO2R tab in Router set:
> - Classic auto control
> - TX Focus = DTR | COM x
> - RX Focus = Follow TX focus | COM x
> - Stereo headphones = RTS | COM x
> 
> At Win-Test Configure Interfaces set:
> - COM x = Other interface
> - COM x = Configure
> DTR = Active Radio
> RTS = Stereo RX Audio
> 
> Unfortunately, I believe you said you have a microHAM MKII (microKEYER II), which does not support SO2R switching for headphones and mic., just CW switching via the WinKey outputs.  So I made a mistake.  I thought you had a microHAM MK2R, MK2R+, or u2R, in, which case you could use virtual COM port pins or LPT pins to switch headphones and mic. for SO2R.  If you have a MKII, you cannot do this.
> 
> 73,
> Bob, N6TV
> 
> 
> _______________________________________________
> Support mailing list
> Support at f5mzn.org
> http://lists.f5mzn.org/cgi-bin/mailman/listinfo/support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.f5mzn.org/pipermail/support/attachments/20110529/884a414c/attachment-0001.html>