Logikey K-3 KEYER
7
Morse text and embedded functions can then be entered via the paddles. When each word is complete, sim-
ply stop sending. The keyer will detect and insert a word space, then prompt you for the next word by send-
ing "I". There is no limit to the elapsed time between words, so there is no need to hurry your sending.
The keyer includes an edit feature for immediate correction of errors during message loading. If a mistake
occurs, simply send an error indication of 7 or more dots. The keyer will erase the last word sent. It will then
play the 'new' last word (if any) so that the position in the message is known exactly. As many words as
needed can be erased this way. When the desired position is achieved, continue to enter the remainder of
the message.
After the keyer responds with "I" following the final word, the message is closed by a momentary press of
the button. To completely erase a message from memory, initiate the start of a message, but rather than
keying in text, simply press the message button again immediately after the "C" is sent. In the event that
message capacity is exhausted during the load, the keyer will send the raspy "error" message and the mes-
sage will terminate at that point. The operator might wish to then delete the last word with the error string,
then have the balance of the message continue in new message channel, and use the embedded command
number command (i.e. "/2") to tie the messages together.
LOADING REAL-TIME MESSAGES
Some operators prefer messages containing stretched or compressed spacing rather than perfect timing.
Real-time mode stores and replays messages exactly as entered. Along with somewhat reduced message ca-
pacity, the primary disadvantage of real-time messages is that they cannot contain embedded functions. Use
the Function Mode "L" command to switch to the real-time load mode, then press and hold the desired mes-
sage button. After 2 seconds, a continuous tone will emit, at which time loading mode is enabled and the
button may be released. The keyer then responds by sending "R" to confirm real-time mode and waits for
paddle input.
Since the keyer waits until the first paddle closure, there is no need to rush the first entry. Once entry be-
gins, however, the keyer loads continuously - any pauses are stored as spaces in the message. All interchar-
acter and interword spacing is strictly up to the operator. To end the message, simply press the message
button momentarily. Note that the elapsed time from the end of the last character to message termination is
stored as space at the end of the message. If room is exhausted during the load, the message is terminated
automatically, and the raspy error signal is sent by the keyer, indicating that the loading has terminated. The
operator will also notice that messages are not as easy to enter in this mode, since the keyer clock is free-
running and thus not resynched with paddle closures. However the stored message will play back cleanly.
PLAYING MESSAGES
It couldn't be simpler: just tap the desired message button. Both character-mode and real-time messages
can be played regardless of the current load mode.
If the input queue is enabled, multiple message button closures will be remembered. Each message will be
played in succession as the previous completes. As a simple example, suppose that message 1 contains
"CQ" and message 4 contains "DE WB8ZRL". Then pressing button 1 three times and button 4 once, in quick
succession, will cause "CQ CQ CQ DE WB8ZRL" to be played. As many as 8 button activations will be remem-
bered in this mode. With the input queue disabled, however, a button closure immediately cancels any cur-
rent message and starts the commanded one.
When a paddle closure is detected, messages are immediately aborted and the input queue flushed. The
only exception is during execution of an embedded /B break or a /R resume instruction, when paddle input
is expected. Otherwise, the paddles always take priority over message playback.
