Prosigns for Morse code

From AviationSafetyX Wiki
Jump to navigation Jump to search
Diagram of a telegraph key used to send messages in Morse code

Procedural signs or prosigns are shorthand signals used in Morse code telegraphy, for the purpose of simplifying and standardizing procedural protocols for landline and radio communication. The procedural signs are distinct from conventional Morse code abbreviations, which consist mainly of brevity codes that convey messages to other parties with greater speed and accuracy. However, some codes are used both as prosigns and as single letters or punctuation marks, and for those, the distinction between a prosign and abbreviation is ambiguous, even in context.

Overview

In the broader sense prosigns are just standardised parts of short form radio protocol, and can include any abbreviation. Examples would be K for "okay, heard you, continue" or R for "message, received".[1][2] In a more restricted sense, "prosign" refers to something analogous to the nonprinting control characters in teleprinter and computer character sets, such as Baudot and ASCII. Different from abbreviations, those are universally recognizable across language barriers as distinct and well-defined symbols.

At the coding level, prosigns admit any form the Morse code can take, unlike abbreviations which have to be sent as a sequence of individual letters, like ordinary text. On the other hand, most prosigns codes are much longer than typical codes for letters and numbers. They are individual and indivisible code points within the broader Morse code, fully at par with basic letters and numbers.

The development of prosigns began in the 1860s for wired telegraphy. Since telegraphy preceded voice communications by several decades, many of the much older Morse prosigns have acquired precisely equivalent prowords for use in more recent voice protocols.

Not all prosigns used by telegraphers are standard: There are regional and community-specific variations of the coding convention used in certain radio networks to manage transmission and formatting of messages, and many unofficial prosign conventions exist; some of which might be redundant or ambiguous. One typical example of something which is not an officially recognized prosign, but is yet fairly often used in Europe, is one or two freely timed dits at the end of a message, Template:Nobr or <templatestyles src="Morse/styles.css"/> ▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄ ; it is equivalent to the proword OUT, meaning "I'm done; go ahead". However the official prosign with the same meaning is AR, or <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄▄▄ ▄ , which takes a little longer to send.[3][2]

Representation in printed material

Even though represented as strings of letters, prosigns are rendered without the intercharacter commas or pauses that would occur between the letters shown, if the representation were (mistakenly) sent as a sequence of letters: In printed material describing their meaning and use, prosigns are shown either as a sequence of dots and dashes for the sound of a telegraph, or by an overlined sequence of letters from the International Morse Code, which when sent without the usual spacing, sounds like the prosign symbol.

The best-known example of the convention is the standard distress call preamble: SOS. As a prosign it is not really composed of the three separate letters S, O, and S, (in International Morse: <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄ ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ) but is run together as a single symbol <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄ ▄ ▄ , which is a sign in its own right.

History

In the early decades of telegraphy, many efficiency improvements were incorporated into operations. Each of the early versions of Morse code was an example of that: With only one glaring exception (Intl. Morse O), they all encoded more common characters into shorter keying sequences, and the rare ones into longer, thus effecting online data compression. The introduction of Morse symbols called procedural signs or prosigns was then just a logical progression. They were not defined by the developers of Morse code, but were gradually introduced by telegraph operators to improve the speed and accuracy of high-volume message handling, especially those sent over that era's problematic long distance communication channels, such as transoceanic cables and later longwave wireless telegraphy.

Among other prosign uses, improvement in the legibility of written messages sent by telegraph (telegrams) using white space formatting was supported by the procedural symbols. To become an efficient telegraph operator it was important to master the Morse code prosigns, as well as the many standard abbreviations used to facilitate checking and re-sending sections of text.

Notation and representations

There are at least three methods used to represent Morse prosign symbols:

  1. Unique dot/dash sequences, e.g. <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄ ▄▄▄ 
  2. Unique audible sounds, e.g. dah di di di dah
  3. Non-unique printed or written overlined character groups,[lower-alpha 1] e.g. BT

Although some of the prosigns as-written appear to be simply two adjacent letters, most prosigns are transmitted as digraphs that have no pauses between the patterns that represent the "combined" letters, and are most commonly written with a single bar over the merged letters (if more than one single character) to indicate this.[4] The only difference between what is transmitted for the Morse code prosign vs. the separate letter signs is the presence or absence of an inter-letter space between the two "dit" / "dah" sequences. Although the difference in the transmission is subtle, the difference in meaning is gross:

For example, the unofficial prosign AA (<templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄▄▄ ) indicates that the receiving Morse operator should begin a new line,[lower-alpha 2] but the two separate letter sign or abbreviation AA (<templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ) indicates either the voice procedure words ALL AFTER, used to indicate what part of the previously transmitted message needs to be re-transmitted.[lower-alpha 3]

Because no letter boundaries are transmitted with the codes counted as prosigns, their representation by two letters is usually arbitrary, and may be done in multiple equivalent ways. Normally, one particular form is used by convention, but some prosigns have multiple forms in common use:

For example, AA (<templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ +<templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ) is exactly equivalent to EK (<templatestyles src="Morse/styles.css"/> ▄ +<templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ) and RT (<templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ +<templatestyles src="Morse/styles.css"/> ▄▄▄ ).
Although the well-known calling prosign for emergency messages SOS is always represented by the three letters "SOS", it could just as well be written VZE (<templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ +<templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄ ▄ ▄ +<templatestyles src="Morse/styles.css"/> ▄ ), VGI (<templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ +<templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄ ▄ +<templatestyles src="Morse/styles.css"/> ▄ ▄ ), or even 3B (<templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ ▄▄▄ +<templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄ ); all of these render the same single code <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄ ▄ ▄ .

Many Morse code prosigns do not have written or printed textual character representations in the original source information, even if they do represent characters in other contexts. For example, when embedded in text the Morse code sequence <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄ ▄▄▄  represents the "double hyphen" character (normally "=", but also Template:Nobr).[1] When the same code appears alone it indicates the action of spacing down two lines on a page in order to create the white space indicating the start of a new paragraph[2] or new section in a message heading.[1] When used as a prosign, there is no actual written or printed character representation or symbol for a new paragraph (i.e. no symbol corresponding to ""), other than the two-line white space itself.

Some prosigns are in unofficial use for special characters in languages other than English, for example AA is used unofficially for both the "next line" prosign[lower-alpha 2] and for "Ä",[6][7] neither of which is in the international standard.[1] Other prosigns are officially designated for both characters and prosigns, such as AR equiv. "+", which marks the end of a message.[lower-alpha 4][1] Some genuinely have only one use, such as CT or the equivalent KA (<templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄ ▄▄▄ ), the International Morse prosign that marks the start of a new transmission[1] or new message.[2]

International Morse code

The procedure signs below are compiled from the official specification for Morse Code, ITU-R M.1677, International Morse Code,[1] while others are defined the International Radio Regulations for Mobile Maritime Service, including ITU-R M.1170,[8] ITU-R M.1172,[4] and the Maritime International Code of Signals,[5] with a few details of their use appearing in ACP 131,[9] which otherwise defines operating signals, not procedure signals.

Prosigns

The following table of prosigns includes K and R, which could be considered either abbreviations (for "okay, go ahead", and for "received") or prosigns that are also letters. All of the rest of the symbols are not letters, but in some cases are also used as punctuation.

General-use procedure signs
Prosign Matching voice procedure word Code symbol Reference Explanation
AA UNKNOWN STATION <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄▄▄  [5] This meaning is only used for directional signal lights.[5] It has no official use in radio telegraphy,[1] where it is unofficially used to represent an accented letter Ä or Á,[6][7] or the prosign for "next line", and then only when it is embedded inside a heading section in amateur traffic.[2]
R ROGER <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄  [4][2] Means the last transmission has been received, but does not necessarily indicate the message was understood or will be complied with.
Template:Listen
K OVER <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄  [1][2] Invitation to transmit after terminating the call signal. (e.g. <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄▄▄ ▄ <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ).
Template:Listen
AR OUT <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄▄▄ ▄  [4][1][2] End of transmission / End of message / End of telegram.[lower-alpha 4]
(Same as EC "end copy", and character +.)[lower-alpha 5]
Template:Listen
AS WAIT <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄ ▄  [8][4][1][2] "I must pause for a few minutes."[lower-alpha 6]

Also means "I am engaged in a contact with another station [that you may not hear]; please wait quietly."
Template:Listen

AS AR WAIT OUT <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄ ▄ 
<templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄▄▄ ▄ 
[11] I must pause for more than a few minutes.
VE VERIFIED <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ ▄  [1][2] Message is verified.
Template:Listen
? SAY AGAIN? <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄  [1][11] When standing alone, a note of interrogation or request for repetition of the immediate prior transmission that was not understood.

When ? is placed after a coded signal, modifies the code to be a question or request.
Template:Listen

INT INTERROGATIVE <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄▄▄ ▄ ▄▄▄  [11][9][12] Military replacement for the ? prosign; equivalent to Spanish ¿ punctuation mark. When placed before a signal, modifies the signal to be a question/request.[13][lower-alpha 7]
HH ... CORRECTION
(kor-rek-shun)
<templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄ ▄ ▄ ▄ ▄  [1][2] Preceding text was in error. The following is the corrected text. (Same as IIII or EEEEEEEE.)
Template:Listen
HH AR DISREGARD THIS TRANSMISSION OUT <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄ ▄ ▄ ▄ ▄ 
<templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄▄▄ ▄ 
The entire message just sent is in error, disregard it. (Same as EEEEEEEE AR.)[lower-alpha 8]
BT BREAK <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄ ▄▄▄  [4][1][2] Start new section of message.
Same as character = or rarely – –.
KA ATTENTION <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄ ▄▄▄  [4][1][2] Message begins / Start of work / New message
(Starting signal that precedes every transmission session. Sometimes written as CT.)
Template:Listen
SK OUT <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ ▄ ▄▄▄  [4][1][2] End of contact / End of work / Line is now free / Template:Nobr
(Ending signal that follows every transmission session. Occasionally written VA.)

Abbreviations for message handling

The following table lists standard abbreviations used for organizing radiotelegraph traffic, however none of them are actual prosigns, despite their similar purpose. All are strictly used as normal strings of one to several letters, never as digraph symbols, and have standard meanings used for the management of sending and receiving messages. Dots following indicate that in use, the abbreviation is always followed by more information.

General-use abbreviations and letter-codes
Abbrev. Matching voice procedure word Code symbol Reference Explanation
DE ... Template:Grey FROM <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄  <templatestyles src="Morse/styles.css"/> ▄  [4][1][2] Used to precede the name or other identification of the station sending the transmission (Morse abbreviation).
NIL NOTHING HEARD <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄  General-purpose response to any request or inquiry for which the answer is "nothing" or "none" or "not available" (Morse abbr.). Also means "I have no messages for you."
CL CLOSING <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄  [4][2] Announcing station shutdown (Morse abbr.).
CQ CALLING <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄ ▄ ▄▄▄  [4][2] General call to any station (Morse abbr.).
CP ... ... CALLING FOR <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄▄▄ ▄  [4] Specific call to two or more named stations (Morse abbr.).
CS ... CALLING STATION <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄  [4] Specific call to exactly one named station (Morse abbr.).
CS ? WHO ? <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄  [4] What is the name or identity signal of your station? (Morse abbr.) In many contexts, the question mark is optional.
WA ... WORD AFTER <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄  [4][2] (Morse abbr.)
WB ... WORD BEFORE <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄  [4][2] (Morse abbr.)
AA ... ALL AFTER <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄  [4][2] The portion of the message to which I refer is all that follows the text ... (Morse abbr.)
AB ... ALL BEFORE <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄  [4][2] The portion of the message to which I refer is all that precedes the text ... (Morse abbr.)
Template:Nobr ALL BETWEEN <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄  [4][2] The portion of the message to which I refer is all that falls between ... and ... (Morse abbr.)
C CORRECT / YES / AFFIRMATIVE / CONFIRM <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄  [4][2] Answer to prior question is "yes". (Morse abbr.)
N NO / NEGATIVE <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄  [5][9] Answer to prior question is "no". (Morse abbr.)[lower-alpha 9]
ZWF ... WRONG <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄ ▄ ▄ <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄▄▄ <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄▄▄ ▄  [9] Your last transmission was wrong. The correct version is ...
QTR ? REQUEST TIME CHECK <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄ ▄ ▄▄▄ <templatestyles src="Morse/styles.css"/> ▄▄▄ <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ 
<templatestyles src="Morse/styles.css"/> ▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄ 
[9] Time-check request. / What is the correct time?
(Time is always UTC, unless explicitly requested otherwise, e.g. QTR HST ?)
QTR ... TIME IS <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄ ▄ ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄  [9] The following is the correct UTC in HHMM 24 hour format
BK BREAK-IN <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄  [4][2] Signal used to interrupt a transmission already in progress (Morse abbr.). NATO nets use AX.[9] Some military networks use <templatestyles src="Morse/styles.css"/> ▄▄▄▄▄▄▄▄▄▄▄  TTTT instead.
CFM CONFIRM / I ACKNOWLEDGE <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄  [4][2] Message received (Morse abbr.). (Same as R.)
WX ... WEATHER IS <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄▄▄  [4][2] Weather report follows (Morse abbr.).
INTERCO INTERCO

(in-tur-ko)

<templatestyles src="Morse/styles.css"/> ▄ ▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ 
<templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄ ▄▄▄ 
[5][4] Groups of abbreviations from the International Code of Signals[5] follow (Morse abbr.).

Amateur radio National Traffic System

For the special purpose of exchanging ARRL Radiograms during National Traffic System nets, the following prosigns and signals can be used, most of which are an exact match with ITU-R and Combined Communications Electronics Board (military) standards; a few have no equivalent in any other definition of Morse code procedure signals or abbreviations.

Table of Morse code prosigns and useful Morse code abbreviations[3][1][2]
Prosign Code symbol Meaning Comments Verbalization As text
AA <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄▄▄  Start new line Space down one line; typewritten as Carriage Return, Line Feed (CR-LF). Only used instead of BT in ARRL batched messages, where BT would prematurely start a pending next section.[2] Also written RT. di dah di dah Ä, Á[lower-alpha 10]
AR <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄▄▄ ▄  Message separator, start new message / telegram.[1][3][2] New Page, space down several lines.[3] Decoder software may show "+".[1] Alternative for "Break" in conversational Morse.[2] Also written RN. di dah di dah dit +[1]
AS <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄ ▄  Wait[1][3] Respond with: SN, or characters "R" (Received) or "C" (Confirmed).[3][1] di dah di di dit &[lower-alpha 11]
BT <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄ ▄▄▄  Start new section[1] / paragraph[3][2] Space down two lines; typewritten CR-LF-LF. Decoder software may show "=".[1] dah di di di dah =, – – [1]
CT <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄ ▄▄▄  Start of
transmission[1]
Start of new
message[3][2]
Attention[3][2] commencing transmission. Also written KA. dah di dah di dah
HH ... <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄ ▄ ▄ ▄ ▄  Error /
correction[1][3]
Always followed by correct text.[3] Equivalent to both IIII and EEEEEEEE . Sometimes transcribed as "???". di di di di di di di dit
K <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄  Invitation for any station to transmit[1][3][2] Lone alphabetic character "K" at the end of a transmission.[3] dah di dah K[1]
X <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄▄▄  Full stop[3] Lone alphabetic character "X" surrounded by word spaces.[3][2]
Substitute for period AAA in ARRL batched messages.
dah di di dah X[1]
? <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄  Please say
again[1][3][2]
Lone question mark "?" from the receiving station in response to a transmission; possibly followed by Template:Nobr or Template:Nobr[3] di di dah dah di dit ?[1][3]
KN <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄▄▄ ▄  Invitation for
named station
to transmit[3]
Go ahead, specific named station.[3] Decoder software may show equivalent character "(".[1] dah di dah dah dit ( [1]
NJ <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄▄▄ ▄▄▄ ▄▄▄  Shift to Wabun code Shift from Morse code to Wabun code Kana characters. Also written XM. dah di di dah dah dah
SK <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ ▄ ▄▄▄  Template:Nobr[1] /
Template:Nobr[3][2]
/ Frequency Template:Nobr in use
Also written VA. di di di dah di dah
SN <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ ▄  Understood[3] / verify / verified[1] Message received and checks okay. Alternatively shift from Wabun to Morse code. "SN?" verification requested. Also written VE. di di di dah dit Š, Ś[lower-alpha 10]
SOS <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ ▄▄▄ ▄▄▄ ▄ ▄ ▄  Start of a distress signal[1][3] Only used by the original distressed station, and only for imminent danger to life or property.[1] (Template:Audio) di di di dah dah dah di di dit
DDD <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄▄▄ ▄ ▄ ▄▄▄ ▄ ▄  Start of a
distress signal relayed from another station
Used to forward a copy of a received "SOS". dah di di dah di di dah di dit
BK <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄ ▄ <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄  Break in
conversation[3]
Morse abbreviation for "back-to you" (Morse abbr.).[3] In conversational Morse some use any of AR, BT, KN, or "K" instead. Template:Nobr Template:Nobr BK
CL <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄ <templatestyles src="Morse/styles.css"/> ▄ ▄▄▄ ▄ ▄  Closing down[3][2] Abbreviation for "closing station" (Morse abbr.). Template:Nobr Template:Nobr CL

Obsolete prosigns

Historical Morse code prosigns
Prosign Matching voice procedure word Former code symbol Explanation Reference
CQD Distress call <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄▄▄ ▄ ▄▄▄  <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄  Obsolete code used to call all stations during distress (see CQ). Replaced by SOS in 1906 (see above).
VE General call <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄▄▄ ▄  Code re-used for "Message verified" or "Message understood" (see SN above).[1] Replaced by CQ (see above).[1] 1937 Royal Navy Signal Card[14][15]
NNNNN Answering sign <templatestyles src="Morse/styles.css"/> ▄▄▄ ▄ ▄▄▄ ▄ ▄▄▄ ▄ ▄▄▄ ▄ ▄▄▄ ▄  Dropped.
Template:Nobr Separative sign break <templatestyles src="Morse/styles.css"/> ▄ ▄  <templatestyles src="Morse/styles.css"/> ▄ ▄  Generally replaced by BT, although it is still used in MARS CW operations,[12] and other military standards.[11]
Later re-used for both a "ditto" mark and to represent the warning "I repeat" before a duplicated transmission.
EEEEE Error <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄ ▄ ▄  Exactly five dits (code for digit 5[1]). Replaced by HH[1] (exactly eight dits, EEEEEEEE[1]).
RRRRR Receipt sign ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Replaced by R.[1]
É (printed as e) Further message sign <templatestyles src="Morse/styles.css"/> ▄ ▄ ▄▄▄ ▄ ▄  Re-purposed original ITU symbol for É[1] not used in English.

See also

Template:Div col begin

Notes


References


  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 1.33 1.34 1.35 1.36 1.37 1.38 1.39 1.40 1.41 1.42 1.43 1.44 1.45 1.46 Cite error: Invalid <ref> tag; no text was provided for refs named ITU_MC_Rec
  2. 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 2.19 2.20 2.21 2.22 2.23 2.24 2.25 2.26 2.27 2.28 2.29 2.30 2.31 2.32 2.33 2.34 2.35 2.36 2.37 2.38 Cite error: Invalid <ref> tag; no text was provided for refs named ARRL_Send_CW
  3. 3.00 3.01 3.02 3.03 3.04 3.05 3.06 3.07 3.08 3.09 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 3.20 3.21 3.22 3.23 3.24 3.25 Cite error: Invalid <ref> tag; no text was provided for refs named ARRL_Oper_Man
  4. 4.00 4.01 4.02 4.03 4.04 4.05 4.06 4.07 4.08 4.09 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22 4.23 Cite error: Invalid <ref> tag; no text was provided for refs named ITU-R-M-1172
  5. 5.0 5.1 5.2 5.3 5.4 5.5 5.6 Cite error: Invalid <ref> tag; no text was provided for refs named ICS-102
  6. 6.0 6.1 Cite error: Invalid <ref> tag; no text was provided for refs named Deutsch-Österreich-Telegr-1851
  7. 7.0 7.1 Cite error: Invalid <ref> tag; no text was provided for refs named Smithsonian-Report-1879
  8. 8.0 8.1 Cite error: Invalid <ref> tag; no text was provided for refs named ITU-R-M-1170
  9. 9.0 9.1 9.2 9.3 9.4 9.5 9.6 Cite error: Invalid <ref> tag; no text was provided for refs named ACP131F
  10. Cite error: Invalid <ref> tag; no text was provided for refs named Benedktsn-Kjartnsn-2014-09-27
  11. 11.0 11.1 11.2 11.3 Cite error: Invalid <ref> tag; no text was provided for refs named ACP124
  12. 12.0 12.1 Cite error: Invalid <ref> tag; no text was provided for refs named Op-Guide-2009
  13. 13.0 13.1 Cite error: Invalid <ref> tag; no text was provided for refs named FM24-6


Cite error: <ref> tags exist for a group named "lower-alpha", but no corresponding <references group="lower-alpha"/> tag was found