[WriteLog] SO2V with K3

[Ed Muns]

Hi, John!

I have been using the WriteLog SO2V feature with the K3 since it appeared in
the code and there have been no issues.  I'm very pleased with the way it
works.  For the 10-Meter Contest this weekend, I used the WinKey built in to
a microHAM u2R and WriteLog 11.01e, but nothing to do with this changed from
10.90.  In the 10-Meter RTTY Contest the previous weekend, I used the
WriteLog SO2V K3 feature with two homemade FSK/PTT interfaces on separate
Com ports, one for each Rttyrite window for its respective VFO.  The two
interfaces connect together with a Y-adapter cable at the K3 ACC jack.

When you're setup for SO2V in WriteLog, do you still have keying if you
simply put the K3 into SPLIT mode without changing focus in WriteLog?
Which exact WinKey model do you have and which keyer menu choice did you
select in WriteLog?  Send me a screen capture of your WriteLog Ports window
... maybe I'm overlooking something obvious in the setup.


73,
Ed - W0YK
-------------------------
Ed Muns
www.w0yk.com 

 

John, WA6L, wrote:
> The more recent versions of Writelog offer an SO2V option 
> with the K3.  I decided to give it a try this weekend during 
> the ARRL 10M contest.
> 
> Setup was straightforward.  You enter the K3 twice in the 
> Ports setup, both with the same comm port.  Then you select 
> "number of radios" as two.  
> 
> I did encounter one problem.  When focus is shifted to the 
> second receiver, none of the CW messages would send.  After 
> shifting back to the main receiver, the CW messages came back.
> 
> I am using a K1EL Winkeyer (WKUSB).  When focus is on the 
> second receiver, the Winkeyer is basically inoperative.  Even 
> the buttons no longer send CW (which would have been a 
> work-around).  Once I shut down Writelog, I could manually go 
> to the second receiver using the Split controls, and the 
> Winkeyer worked fine.  So the problem is definitely something 
> that Writelog is doing.
> 
> This is either a bug in 10.90 or a user error.  I am hoping 
> for the latter.  Anyone seen this or similar problems?  Any 
> suggestions?