I think you need another program to make this work. It intercepts the serial 
port for the FSK/PTT and makes it all work together. 

I use 2-Tone instead of myth and seem to get by with just it and n1mm. 

For interface I use my WINKEYER-USB with the latest firmware. I use a “Y” 
adapter in the KEY line. The second line goes to K3/Acc2 FSK pin. “Diddles” go 
to FSK and “Dit-Dahs” go to CW.  works well. 

Sent from my iPhone
...nr4c. bill


> On May 24, 2020, at 1:14 AM, "[email protected]" <[email protected]> wrote:
> 
> I am fairly new to the K3 but have no problems setting up N1MM and other 
> software, getting things to work properly. My problem is I cannot get RTTY to 
> send/TX. I have made a homebrew interface with optoisolators for both the FSK 
> line and the PTT line. I'm going from a separate serial port, pins 3 and 7, 
> for FSK and PTT, to the Assy(15 pin) connector. To pins 1 for FSK, 4 for PTT 
> and 5 for ground.
> 
> When I run MMTTY I cannot get the rig to key. If I switch to SSB or CW and 
> use the CAT line to work the PTT, no problem. If I switch to RTTY and try to 
> use the CAT line it will not key the TX. I've tried a variety of setting in 
> MMTTY and get no TX. I have a 1000MP set up with a similar homebrew interface 
> and have no issues.
> 
> Can anyone shed some help on me?
> 
> 73 Bill K3SV
> 
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:[email protected]
> 
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
> Message delivered to [email protected]
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected] 

Reply via email to