The transmit panel is used to send Morse or data by typing it into the text window or by using macros containing pre-prepared texts. Macros are similar in purpose to a Morse memory keyer, but they may contain special symbols that are replaced with information such as the other station's call or name in real time. They may control the logging of information.
KComm provides sixteen macros for use at any one time. These may be loaded and saved using the icon buttons on the right, so it is easy to have different macro sets for different modes, or for contesting, DXing and ragchewing. KComm remembers the macro set last used for each mode, so you don't have to manually switch macros when changing from CW to data and back.
Each macro button has a caption which tells you what it does. To provide further confirmation a tool-tip pops up when you hover the mouse over the button. You specify what to put in the caption and tool-tip.
The button caption is shown in bold if the macro starts sending whatever is in the text buffer immediately, which it does by including the command ^t in the macro. Other macros simply copy their contents to the text buffer, shown in the large window, and are not sent until you click Start sending.
You can type text directly into the window as well, either to prepare a reply while the other side is sending (hence it is called the typeahead window) or in real time, during the transmission. You cannot edit the text to be sent by typing into the middle of it. You can usually backspace to correct mistakes on a line, but not always during sending, because the software grabs the text out of the buffer and sends it to the radio in big chunks, after which it is difficult to do anything about it.
The best way to find out how the text panel and macros work is to put the K2 or K3 into test mode and make some imaginary contacts. This is especially important when developing your own macros because the syntax of the commands is quite specific and if you make a mistake you may end up sending gibberish!
You can choose to have typed Morse text appear in upper case, if you prefer. The Clear button clears the contents of the text buffer. The Load button lets you load the contents of a text file into the text buffer, should you have a reason to do that.
Once sending has started, the Start sending button caption changes to Stop sending. Click this when you have entered all you want to send. It will take effect only once all the sending has been completed. If you wish to abort a transmission, click Stop sending a second time, or click in the transmit window to ensure it is the focus of your typing and then hit Esc.
Shortcut keys and CW prosigns
In CW mode you can send Morse prosigns either by typing them as text, with spaces on either side - e.g. ' AR ', ' BT ', ' KN ', ' SK ' - or by typing the ASCII characters that the K2/K3 associates with the prosigns: ( for KN, + for AR, = for BT, % for AS, * for SK and ! for VE.
You can also use Ctrl key codes to insert prosigns and some other information (such as name and callsign) into the text you are typing.
|Ctrl+A||CW prosign 'AR'|
|Ctrl+B||CW prosign 'BT'|
|Ctrl+C||Other station's callsign (from log field)
|Ctrl+G||Greeting (e.g. GA, 'good afternoon')|
|Ctrl+K||CW prosign 'KN'
|Ctrl+M||Your callsign (MYCALL)
|Ctrl+N||Other station's name (from log field)
|Ctrl+R||Report (RST) sent
|Ctrl+S||CW prosign 'SK'|
|Ctrl+X||Contest exchange sent|
1. The K3 can be set up to use the @ character in CW mode either as an abort signal, or to send the CW prosign for '@'. The former option must be selected (from the CONFIG menu) otherwise you will not be able to abort CW text that has been sent to the K3 by hitting the Esc key.
2. In the current version of the K3 firmware, all text in PSK31 is transmitted as lower case regardless of how it is sent by KComm.
In data modes that can transmit the full 256 ASCII characters the difficulty arises that the topmost 128 character values stand for different characters depending on the character set being used. KComm needs to know the character set being used on your computer in order to convert the characters correctly. Under Windows this can be detected automatically but under Linux it isn't, so this needs to be set using one of the Miscellaneous Settings options.
If you use the Language Bar or equivalent Linux feature to switch languages then KComm cannot detect this so you should use the setting mentioned above to select the character set you habitually use. This setting affects any macros you create as well, so if for example you have some stored greetings in Cyrillic text to send to Russian hams when you work them on PSK31, you must have one of the Cyrillic character encodings selected when you transmit those macros.