+1 for winkeyer support. 73 de AI6KG On Mon, Jul 20, 2020, 7:03 AM Joe DeVincentis <j...@ko8v.net> wrote:
> Personally, I'd like to see the K4 support something like the TinyFSK > protocol for doing RTTY. > > It could present multiple serial ports. one for CAT, one for FSK and one > for Keying. The FSK could emulate tinyFSK and the keyer could emulate the > K1EL keyers. That way programs don't need to fight over who gets the > serial ports. > > While I despise the following phrase as a SW guy (specifically embedded > real time operating systems): Hey, it's just S/W. I can see this as very > doable in the K4 given what I know about the architecture to date.. Much > harder in the K3s. > > Joe, KO8V > > > On Jul 19, 2020, at 18:50, Bob Wilson, N6TV <n...@arrl.net> wrote: > > > > Bill, > > > > Before it can be "fixed" in the K4, the logging software has to be fixed > to > > send the proper KY command. If it is sending KY<blank>*somes-string*;, > > then the messages are not going to be chained. If it is sending KYW > > *some-string*;, then the messages should be properly chained, perhaps > with > > a very brief pause in between if 0x04 (Ctrl-D, ^D or EOT -- ASCII End of > > Transmission character) is appended at the very end of a each chained > > message, before the terminating semicolon. The "W" means "wait for > message > > completion," as documented in the K3 Programming Manual. > > > > However, once a message sent via KYW starts, you will not be able to > > interrupt the transmission by pressing "Escape" or sending an "RX;" > > command. The RX; won't be processed until the message completes, which > > isn't very helpful. > > > > Maybe *that* will be addressed (somehow) in the K4. > > > > In sum, if you need chaining more than you need message interrupt > > capability, use KYW in your macros. If you need message interrupt > > capability more than you need chaining, use KY<blank>. If you need both, > > maybe you'll have to "wait" (sorry) to see if the K4 team comes up with > > some way to interrupt chained messages already in progress via a special > > "high priority" software command or key tap. > > > > 73, > > Bob, N6TV > > > > On Sat, Jul 18, 2020 at 7:39 AM Bill Frantz <fra...@pwpconsult.com > <mailto:fra...@pwpconsult.com>> wrote: > > > >> I'm getting ready for NAQP RTTY today, and I am reminded of an > >> old bug using the KY CAT command to send RTTY text. I am using > >> RUMlogNG on my MacBook Pro in contest mode which uses the CAT > >> interface to send and receive RTTY. (It also uses CAT with CW.) > >> > >> If I try to chain output, e.g. press the function key to send my > >> callsign several times, frequently the first parts of the > >> chained output are dropped, as shown by the text shown in the > >> VFO-B display. > >> > >> This does not occur on CW, so I think the CW to Data conversion > >> may be involved. The command is defined in the programmer's > >> Reference as: > >> > >> KY (CW or CW-to-DATA Keying from Text; > >> > >> If I chain by using a K3 memory and pressing the M1-4 button > >> several times, the VFO-B display shows "CHAIN" and things appear > >> to work correctly. > >> > >> I will admit, that while I can check what is being sent by > >> listening to the monitor tones with CW, but I can't quite be > >> sure about the RTTY. > >> > >> Will this problem be fixed on the K4? > >> > >> 73 Bill AE6JV > >> > >> ----------------------------------------------------------------------- > >> Bill Frantz | When an old person dies, a | Periwinkle > >> (408)348-7900 | library burns. - Joe McGawon | 150 > >> Rivermead Rd #235 > >> www.pwpconsult.com | Irish Ethnographer | > >> Peterborough, NH 03458 > >> > >> ______________________________________________________________ > >> Elecraft mailing list > >> Home: http://mailman.qth.net/mailman/listinfo/elecraft > >> Help: http://mailman.qth.net/mmfaq.htm > >> Post: mailto:Elecraft@mailman.qth.net > >> > >> This list hosted by: http://www.qsl.net > >> Please help support this email list: http://www.qsl.net/donate.html > >> Message delivered to n...@arrl.net <mailto:n...@arrl.net> > >> > > ______________________________________________________________ > > Elecraft mailing list > > Home: http://mailman.qth.net/mailman/listinfo/elecraft < > http://mailman.qth.net/mailman/listinfo/elecraft> > > Help: http://mailman.qth.net/mmfaq.htm <http://mailman.qth.net/mmfaq.htm > > > > Post: mailto:Elecraft@mailman.qth.net <mailto:Elecraft@mailman.qth.net> > > > > This list hosted by: http://www.qsl.net <http://www.qsl.net/> > > Please help support this email list: http://www.qsl.net/donate.html < > http://www.qsl.net/donate.html> > > Message delivered to j...@ko8v.net <mailto:j...@ko8v.net> > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Elecraft@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to c...@murgatroid.com > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
