Logikey K-3 KEYER
17
What is an embedded command? It is a special command inserted (through the paddle) into a message
being loaded into memory. Embedded commands can only be used in a message loaded in Character mode,
rather than Real-Time mode. Embedded commands always follow a word space "I", and start with a "/", fol-
lowed immediately by the command.
For purposes of this tutorial only, a "_" in the following text is to be considered a WORD SPACE - not a trans-
mitted character. The underline dash is easier to recognize than a simple space. OK? Good.
How do you program your portable call sign in if the "/" is used for entering an embedded command, you
ask? Simple. As long as the slash bar is NOT preceded by a word space, the keyer will recognize it as a slash
bar. So if you are signing WY9IE/KH7, no problem at all. Just key it into the memory. (On the other hand, if
you want to program in WY9IE_/KH7 with a word space pause, that can be done with the Gap command,
which we will learn shortly.)
Let's try out a message with an embedded command. First, let's call one message from inside another. To do
so, first load into memory #1 your call sign "DE WY9IE AR". Now, load the following into message #2:
"CQ_CQ_CQ_/1" (Don't forget that the "_" means a word space in your message load, indicated by the key-
er's high-pitched "I".) Got it stored? OK. Now, simply press the #2 button to play out its stored message.
Hah! See that? It called and played message #1, running it out with a perfect word space between the two
messages.
OK, now load a different message into message #1 "CQ_CQ_CQ_DE_WY9IE WY9IE_/1". OK, now play it
back. See how it keeps playing over and over again? You have created a closed loop, with the message con-
tinuously calling itself. Of course, to stop the message, all you have to do is touch your paddle, or press any
two buttons and release.
Load into message #2: "12345". Then, load this into message #1: "ABC_DEF_GHI_/2_JKL_MNO". Now play
message #1 back. See how message #1 picked up the embedded call to message #2, then, when message
#2 had run its course, message #1 continued?
Now, let's examine the embedded Pause command, called by "/Pdd", where dd stands for an operator se-
lected number between ØØ and 99, and where each digit stands for one tenth of a second. So, load this
message into memory #1: "CQ_CQ_CQ_DE_WY9IE_WY9IE_AR_/P5Ø_/1", then play it back. Now you
should have the CQ message play, sign your call, and then after a five second pause, repeat again. And
again. And again etc. The /P5Ø is your embedded command into the message to pause 5 seconds, then
continue, where continuation in this case calls for a repeat of message #1. And note that you embedded
two commands in a row, with each doing its thing. This closed loop message with a pause for listening is
great for beacons, contest CQing on a relatively dead band, Meteor Shower skeds etc. Try
"ABC_DEF_GHI_/P50_JKL _MNO". See how the pause allows internal breaks in message transmission? But
remember, if you touch the paddle during the pause, the message will be killed, and you are restored to nor-
mal keyer mode.
Let's make a beacon message out of it, with a key down tone of 5 seconds. Load this into message #3:
"TEST TEST DE WY9IE/B WY9IE/B /X /P5Ø E /3. The "/X" of course puts the keyer in the "key-down" mode,
and the "/P5Ø" command causes it to go for 5 seconds. You ask what the "E" is after the "/P5Ø" command
is for? It is silent - it "breaks" the key-down mode. Load it and try it. To escape the looped beacon message,
touch the paddle or press any two buttons.
Now, suppose you want a message that would include hand-sent text, like the other station's call in a con-
test exchange? For that, embed a "/B" command, "B" as in "Break". Load this message: "UR_RST_/B_DE
WY9IE" and play it. Notice that the message play back gives you the "UR_RST", then quits. Now, manually
enter the RST report -say "579", then release the paddle. Almost immediately after you release the paddle,
the "DE WY9IE" will play. The "/B" command opens a window for paddle entry. When the message reaches
the "/B" it stops and waits for your entry. While you are sending manually, the keyer monitors your sending,
and as soon as it detects a space greater than a word space it picks up where it left off and finishes the
message. Note that there is one possible problem in using this embedded command: you will find, especially
at high speeds, that any delay during your manual sending will cause the keyer to try to resume before you
are finished. Then, when it senses your continued paddle closures, the keyer will think you have terminated
the message and will stop, leaving you wondering what happened, and maybe feeling a little dumb.
To Next Page
Loading...