Note: The Tab is displayed as a right arrow character and the Carriage Return is displayed as
a left arrow character on the LCD. Both are sent as a word space.
You may control the unit's features during message playback by using embedded commands.
These embedded commands can set sending speed, audio tone, and Farnsworth values, as well as
provide great flexibility by allowing functions such as message looping and one message calling
another. Embedded commands begin with a slash “/” and must enter as a separate word. Upper
or lowercase letters may be used; embedded commands are not case-sensitive.
When a parameter such as Overall Speed or Tone is specified by an embedded command, the
parameter will remain set during playback of that message. When playback of that message is
completed or stopped, the value of the parameter will revert to the value set prior to the message
playback.
Note: Adjusting the Speed control during message playback will undo the settings set by
embedded commands /S, /U and /W.
Embedded Commands
While in the message recording mode you may use embedded commands for special features.
To use an embedded command, simply store the multi-character embedded command code
within your message. To distinguish embedded commands from normal text, the embedded
commands must be entered as a separate word; that is, it must be preceded by a word space (this
leading space is ignored during playback). When encountered during message playback, the
commands are executed. Note that if “/” is part of a single word, as in K5MFJ/4, it is sent as
expected and is not executed as an embedded command. Embedded commands and their uses
are explained below:
Call – calls message #, where # is a single digit in the range of 1 to 4. This allows
one message to be called from another. When playback of the called message is
finished, playback continues with the rest of the calling message. This command has
a three-level deep stack; that is, a message can call another message, this message
then calls another message, which in turn calls another message. One message
should not call itself or any of its calling messages; otherwise, the stack will overflow
resulting in infinite loop.
Note: The message stack size increases to seven levels deep if the message queue
is disabled.
To Next Page
Loading...