This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
guide:aerospace_communication_protocols [2014/04/16 16:01] – external edit | guide:aerospace_communication_protocols [2019/06/21 12:19] – Remove forced line breaks wes | ||
---|---|---|---|
Line 11: | Line 11: | ||
The standard message contains several key components. The first is the designation of the calling station and the intended receiving stations. This can be given in several formats, including: | The standard message contains several key components. The first is the designation of the calling station and the intended receiving stations. This can be given in several formats, including: | ||
- | “[receiving station], [calling station]”\\ | + | “[receiving station], [calling station]” |
- | “[receiving station], this is [calling station]”\\ | + | “[receiving station], this is [calling station]” |
- | “this is [calling station], calling [receiving station]”\\ | + | “this is [calling station], calling [receiving station]” |
Then follows the message traffic. The body of the message ought to be as short as possible. Leaving out unnecessary grammatical features is acceptable, even preferable, as long as the meaning of the message remains clear. Particularly long message out to include a pause, in the event that other critical traffic can be heard across the network. This pause is signaled by saying, “break, | Then follows the message traffic. The body of the message ought to be as short as possible. Leaving out unnecessary grammatical features is acceptable, even preferable, as long as the meaning of the message remains clear. Particularly long message out to include a pause, in the event that other critical traffic can be heard across the network. This pause is signaled by saying, “break, |