|
I am trying to use the KY command with Writelog for RTTY contesting. I
have no problem setting up a Keyboard shortcut which then sends the data in the KY command, however I cannot find a way to stop the K3 from transmitting after the command sends the data in KY. I see there is an RX; command to end the TX. I also tried a SWT16 to create a press of the XMIT button. I cannot find a syntax that works for combining the RX or SWT16 command at the end of my KY command. I do not want to use another key press. I was hoping to do it with one line of data. The command string does not appear to work with the KY command Neither of these formats with return to radio to RX. KY "callsign";RX; or KY "callsign;SWT16; Any thoughts? Rich ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
Administrator
|
Use the "KYW" form of the command. Inserting a 'W' in place of the normal space causes any subsequent command (in this case "RX;") to wait for the text string to be sent.
73, Wayne N6KR On Jan 6, 2016, at 8:55 PM, Rich <[hidden email]> wrote: > I am trying to use the KY command with Writelog for RTTY contesting. I have no problem setting up a Keyboard shortcut which then sends the data in the KY command, however I cannot find a way to stop the K3 from transmitting after the command sends the data in KY. I see there is an RX; command to end the TX. I also tried a SWT16 to create a press of the XMIT button. I cannot find a syntax that works for combining the RX or SWT16 command at the end of my KY command. I do not want to use another key press. I was hoping to do it with one line of data. > > The command string does not appear to work with the KY command > > Neither of these formats with return to radio to RX. > > KY "callsign";RX; > or > KY "callsign;SWT16; > > Any thoughts? > > Rich > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
In reply to this post by Rich-4
Yes, I had the same issue last weekend. I rec’d help from several listers including Dick who showed me the proper syntax for n1mm. Below is the function key file I used with n1mm.
The "<04>;” is a ^D or ctrl-D which is an EOT (end of transmission) character from ‘days of olde’ i’m told. The brackets indicate HEX base. I realize these are for n1mm, your software may be totally different. Hope this helps, some. …bill nr4c > On Jan 6, 2016, at 11:55 PM, Rich <[hidden email]> wrote: > > I am trying to use the KY command with Writelog for RTTY contesting. I have no problem setting up a Keyboard shortcut which then sends the data in the KY command, however I cannot find a way to stop the K3 from transmitting after the command sends the data in KY. I see there is an RX; command to end the TX. I also tried a SWT16 to create a press of the XMIT button. I cannot find a syntax that works for combining the RX or SWT16 command at the end of my KY command. I do not want to use another key press. I was hoping to do it with one line of data. > > The command string does not appear to work with the KY command > > Neither of these formats with return to radio to RX. > > KY "callsign";RX; > or > KY "callsign;SWT16; > > Any thoughts? > > Rich > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
In reply to this post by wayne burdick
Thanks so much. It worked like a champ. I guess I should not have
"assumed" that the Prog Ref I googled was the most recent. The one on your site shows the KYW quite clearly. My bad. Thank you Rich On 1/6/2016 23:57 PM, Wayne Burdick wrote: > Use the "KYW" form of the command. Inserting a 'W' in place of the normal space causes any subsequent command (in this case "RX;") to wait for the text string to be sent. > > 73, > Wayne > N6KR > > On Jan 6, 2016, at 8:55 PM, Rich <[hidden email]> wrote: > >> I am trying to use the KY command with Writelog for RTTY contesting. I have no problem setting up a Keyboard shortcut which then sends the data in the KY command, however I cannot find a way to stop the K3 from transmitting after the command sends the data in KY. I see there is an RX; command to end the TX. I also tried a SWT16 to create a press of the XMIT button. I cannot find a syntax that works for combining the RX or SWT16 command at the end of my KY command. I do not want to use another key press. I was hoping to do it with one line of data. >> >> The command string does not appear to work with the KY command >> >> Neither of these formats with return to radio to RX. >> >> KY "callsign";RX; >> or >> KY "callsign;SWT16; >> >> Any thoughts? >> >> Rich >> ______________________________________________________________ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[hidden email] >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to [hidden email] > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
In reply to this post by Rich-4
On January 7, NR4C posted a function key message file for N1MM+ that
used KY commands to send FSK RTTY without requiring any FSK keying interface connected to the K3/K3S AUX port. While the basic idea (<04> used to terminate transmissions) is good, unfortunately there is an error in this file. Almost every message line in the file was terminated with a K30; command. These K30; commands should all be removed from the file. N1MM+ expects the K3/K3S to be in K31 mode, and switching it to K30 mode will cause some N1MM+ program features to stop working correctly. 73, Rich VE3KI ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
Is there a command for the RX ANT on the K3 ?
73 Dwight NS9I ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
Yes SWT25;
Rich On 1/9/2016 7:50 AM, DGB wrote: > Is there a command for the RX ANT on the K3 ? > > 73 Dwight NS9I > > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
Administrator
|
In reply to this post by Richard Ferch
Also note that a new field-test version of K3/K3S firmware is presently in test (rev. 5.46) that corrects a long-standing problem with the "RX;" command. This command is often used at the end of "KY<text>;" packets, or just for general use in returning the radio to receive mode. "RX;" now correctly terminates transmit in all cases, even when used in combination with PTT.
Anyone who uses N1MM (old or new versions) and would like to try the new firmware should contact me directly. 73, Wayne, N6KR (Who is aware that such requests often result in unintentional reflector postings, and yet asks for the group to be tolerant of this :) On Jan 9, 2016, at 4:41 AM, Richard Ferch <[hidden email]> wrote: > On January 7, NR4C posted a function key message file for N1MM+ that used KY commands to send FSK RTTY without requiring any FSK keying interface connected to the K3/K3S AUX port. While the basic idea (<04> used to terminate transmissions) is good, unfortunately there is an error in this file. > > Almost every message line in the file was terminated with a K30; command. These K30; commands should all be removed from the file. N1MM+ expects the K3/K3S to be in K31 mode, and switching it to K30 mode will cause some N1MM+ program features to stop working correctly. > > 73, > Rich VE3KI ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
| Free forum by Nabble | Edit this page |
