Networked DMR communications is a shared resource, with imposed latencies (delays) that require a high level of ETIQUETTE applied to radio operation. Operators must visualize that their communications may not only be heard by hundreds, or thousands of DMR users, but that resources are being tied up by communications and may deny other users access. Users should invoke a higher level of operational courtesy, and a stronger adherence to structured protocols to avoid denying access to other operators.

Because of latency that is introduced by digitally encoding of digitized voice communications with Forward Error Correction codes at the transmitter, the application of Forward Error Correction to decoded data at the receiver, and the delay inherent in internet traffic, significant and noticeable latency (delay) is inherent in DMR communications. An analogy can be drawn to analog FM repeater communications, where protocol demands delaying until the repeater squelch tail drops, and voice must be delayed after keying to accommodate tone decoder delays. Similarly, DMR requires that you wait after a transmission stops, and before you start a transmission, to accommodate breaking traffic. It should be noted that there is no repeater squelch tail with DMR. Operators should wait for a minimum of 2-seconds after hearing the end of a transmission before initiating a transmission, and then wait an additional 1-second after keying the transmitter before speaking. Remember, users of any DMR repeater, or any DMR hot-spot device, on a world-wide basis, may wish to break in. Failure to adhere to delaying transmission may result in denying other operators access.

Nowhere is the importance of listening first more applicable to radio operation as it is with DMR, and especially networked DMR. When you arrive on channel, listen for a minimum of 30-seconds to get a sense as to whether the repeater, or the talk-group is in use. If the repeater or talk-group is in use, listen for a while to acquire conversational context, and then intelligently decide whether you can or should interject in the conversation. Do not interject to mislead or take-over a conversation. Rather, wait until the conversation is completed before interjecting if you mean to change topics or focus.

Announcements should be used sparingly. Many operators on DMR are in the habit of announcing their presence on DMR. Many of these announcements occur without applying the Listen First technique described above. There is a time when such announcements are sensible, but far more often than not, such announcements are disruptive and annoying. An announcement may be necessary to notify other repeater users that the repeater is now on a specific talk-group. But for most other purposes, such announcements are unnecessary. If an announcement is made, for the sake of notifying other repeater users that a specific talk-group is in use, the announcement should be made only once, and should not be periodically repeated. Operators should not make themselves a nuisance by periodically and repeatedly announcing their call sign and that they are listening to a specific talk-group as doing so literally drives other operators, who may be waiting for a call, to move to another talk-group. Remember: A talk-group is a wide-area resource, used far beyond the scope of your local repeater or hot-spot, and requires being courteous to other operators by using the resource sparingly. Over use of announcements tends to deter station operators from monitoring or communicating on a talk-group.

The Last Heard resource that is available on the BrandMeister Network web-site is a powerful resource to determine when a specific operator is available or when a specific talk-group is in use. However, operators should take care to apply the Listen First procedure when switching to a talk-group observed on Last Heard before interjecting into a conversation.

The DMR-ID of a station appearing on the talk-group may be displayed momentarily on your radio. This can be a consequence of the other station moving a dynamic talk-group on a repeater, or a hot-spot (such as a SharkRF OpenSpot), to the ARES-ID talk-group, and occurs when the station momentarily keys their transmitter to move the repeater or hotspot to the target talk-group. Such display of DMR-ID, or additional identifying information that may be programmed into the radio contact list, is not an indication that the station wishes to be called. The station may only wish to monitor the talk-group. Stations switching between repeater channels and/or hot-spot devices also will key to inform the network servers how to route a private call.  It is difficult to determine what the station intends.

In summary, do not force a QSO, but allow a station to move to the talk-group with the purpose of monitoring. Do not give the impression to other operators that you are waiting to pounce every time they appear on the talk-group.

DMR latencies can make it difficult to complete a call if another station responds to a call that is not directed toward them. Unlike other operating modes, such as analog FM simplex or analog FM repeater operations, a station that is not targeted in a call and that responds, even with a simple query to ask if they were called, can cause the targeted station to not be heard. There may be no indication that doubling has occurred. If you think that your station may have been called but are not certain because you did not actually hear the call, it is important that your first response is to wait in order to allow for the targeted station to respond. It is far better to wait 10 or 15 seconds, and then, if the channel is clear, make a query to ask if your station was called than to respond when uncertain and deny the calling station and called station the opportunity to establish contact. This operating principle employs the primary Amateur Radio operating skill of always listening first.

Talk-group Hopping, is a process where a station makes a call on a talk-group, waits a very short period of time, and then moves to the next talk-group before repeating this same process. Talk-group hopping is both disruptive to communications and an abuse of a shared network resource. Talk-group Hopping should be strongly discouraged. If talk-group hopping is a normal operating procedure for you, please do not include the ARES-ID 31016 talk-group in your talk-group hopping sequence.

If all parties in a QSO are operating on the same repeater, and networked resources are not required to support the QSO, move off of the Brandmeister Network talk-group and carry on the QSO on the LOCAL talk-group as configured for the repeater that you are operating on. Do not unnecessarily consume networked bandwidth. If all parties to a QSO are not on the same repeater, then this is a situation where network utilization, and the act of occupying a talk-group is justified

Talk-groups that cover an extremely large area should not be used for conversation. Rather, these talk-groups should be used to make a call, and then move off to a less used talk-group to conduct your conversation. For example, use USA 3100 to make a call and then move off to a state-wide talk-group, such as IDAHO 3116, to conduct your conversation. Do not deprive others from making a call by using such large area resources for conversation.

Networked DMR should not be visualized as a peer-to-peer resource that is limited in scope to the sphere of local repeater coverage foot-print. Networked DMR operation is a wide-area resource and demands a higher level of awareness of its wider scope, along with an extra dose of operational courtesy, to ensure that all users are accommodated and that a operations on the talk-group do not repel the very operations for which the talk-group was established.

With no receive signal present, the squelch control on an FM receiver should be adjusted just to the point where the audio becomes muted. Man-made noise sources may cause the squelch to pass audio and it may be necessary to adjust the squelch control with a dependency on other equipment that may be operating in proximity to the FM receiver. For example, a computer or a cash register may present a weak signal that opens the FM receiver squelch, and you may need to temporarily increase the squelch threshold setting when in proximity with such devices.

Signal reports are never to be interpreted as a personal attack. Nor does a signal report imply that improper station performance is an intentional act. Signal reports are always intended to to be an aid to station operation. Most amateur radio operators place high value on receiving a signal report, and especially so when the report is accompanied by a technical description that explains how anomalous operation affects station performance and suggests possible root causes. In fact, most amateur operators desire to have any anomalous operation reported to them.

Most radio communication occurs in half-duplex mode. Before explaining half-duplex, let's talk about the mode of communications that we all use in our conversations that are not conducted over radio, that is full-duplex.

In full duplex operation, you can hear the person that you are talking to at the same time that you are talking. In this mode of communication, you can interrupt or interject into the conversation through the simple act of speaking. With the exception of Repeaters use of full duplex operation in Amateur Radio is extremely rare.

In half-duplex operation, you cannot hear the station that your are conversing with while you are talking. This is equivalent to placing your fingers in your ear whenever you are speaking with another individual, and they would do the same.

In half-duplex operation, you cannot interrupt or interject while another station is transmitting. Nor can the station that your are conversing with interrupt or interject while you are transmitting. We cannot talk and listen at the same time in a half-duplex system

When using FM, the stronger of two stations will be heard over the weaker station. This phenomenon is referred to as capturing the receiver. Even in these cases, there may be a low level tone or growling in the receiver, accompanied by some level of interference to the station that has captured the receiver. The low-level tone, growling or interference is evidence that another station wants to break-in, or, perhaps, the station breaking in captured the receiver and the station you were conversing was not heard.

Early repeaters used relays to key the transmitter in response to the receiver detecting that a signal is present. Some propagation effects, such as mobile flutter, or picket fencing, would cause the repeater transmitter to cycle on and off as the receive signal experiences fading and restoration of received signal. This cyclic operation would result in premature failure of the transmit relay. Further, the delay in keying the transmitter may itself be responsible for rendering a signal unintelligible when compared to leaving the transmitter keyed during periodic momentary signal fading conditions.

These problems were mitigated by implementing a squelch tail timer. As soon as the receiver detects a valid signal, the transmitter is keyed immediately. When the received signal drops out, a timer is started and the transmitter remains keyed until that timer times out. The squelch tail timer duration is longer than most periodic signal fading conditions, and is able to avoid un-keying the transmitter in instances of periodic fading conditions.

Secondary to this function, the squelch tail serves a second purpose in providing a queuing signal to indicate when a user station may begin transmission. Stations may begin transmitting after the repeater squelch transmitter drops. This can be identified by the sound of the repeater squelch decaying being retransmitted by the repeater transmitter when the receive signal drops out of the repeater receiver, followed by a delay that is equal to the duration of the squelch tail timer, and then the sound of the squelch decay heard directly on your radio when the repeater transmitter drops. Although the squelch tail timer duration typically is approximately 1.5 seconds long, shorter and longer squelch tail delays may be present on a given repeater system.

This double decay of squelch circuits, resulting in short noise bursts that are separated by a 1.5 second delay, is often referred to as a ker-chunk sound, or simply the squelch tail (it is not a come-back).

The squelch tail is used in repeater operating protocol to indicate first, that the transmitting station has ceased transmission as evident by the first squelch decay noise burst, and second, that the repeater transmitter has stopped transmitting as evident by the second squelch decay noise burst. Conversing stations should not start transmitting until the second squelch decay noise burst occurs. Breaking stations should transmit in the interval between noise bursts, as conversing stations will be standing by to wait for the repeater transmitter to drop, in order to make their presence known.

The sequence to hear is a CH sound, followed by silence for a count of one, one thousand, two, and then a CH sound.

If the audio queue from the squelch circuit decay is difficult for you, watch your signal strength meter or receiver active Light Emitting Diode for an indication that the repeater transmitter has dropped before keying your transmitter.

Individual repeater transmissions are limited to a maximum duration (by FCC regulations, there is a 10-minute maximum). This is enforced by a timer in the repeater control circuitry. If a transmission exceeds the maximum allowable duration, the repeater transmitter will drop at or before the maximum duration is reached. The repeater transmitter will stay un-keyed until the signal at the repeater receiver drops.

To avoid the timer invoking a drop out of the repeater transmitter, be sure to let the repeater transmitter drop at the end of the squelch tail.

All DMR repeaters require compliance with DMR Tier II.  A DMR Tier I radio will not provide repeater access.  DMR Tier III supports Trunking operation (rarely used on Amateur Radio).  When shopping for a DMR radio, make sure that you purchase a DMR Tier II capable radio.

Because of Amateur Radio's close relationship to Emergency Communications, and to a lesser degree, Public Service communications, it is vital that we, as Amateur Radio operators, are understood by those agencies and organizations that we serve. The day to day operating habits that we establish will prevail in NET operations, or in an Emergency Communications or Public Service role. Further, since many Amateur Radio communications are international in nature, the use of anything other than standard english serves only to cause the break-down in communications.

This is why it is critical that we use Plain English. Further, training from the Federal Emergency Management Administration (FEMA) mandates that Plain English be used.

Of the utmost importance is to listen to the frequency prior to making a call. If you observe that the frequency is already in use, wait until the frequency is no longer in use before making a call. If someone else made a call, allow time for the station that they called to respond before making your call (note that the calling station will likely repeat the call). If the call is an emergency, you may break in at any time to make an emergency call. If the call is not an emergency, but is urgent or time critical, you may break in and, when acknowledged, explain that you would like to make a quick call and will vacate the frequency shortly if allowed to make a quick contact (most Amateur Radio operators will accommodate such a request). If the frequency is not in use, you are free to make a call.

Do not use the proword BREAK to break into a conversation.  The proword BREAK is used to indicate a separation of text from other portions of the message.  To break into a conversation, simply key and say your call sign.

In an emergency, use the phrase BREAK BREAK.  The number of instances of the use of the BREAK proword (i.e. a single BREAK or BREAK BREAK) provides the context or intent in the use of the proword.

Avoid using a double BREAK if you are not declaring an emergency.

If you wish to make another call, you may do so. If you do not wish to make another call, you may simply cease operation. Clearing off the frequency is optional, but usually not necessary.

If you choose to clear off the frequency, just pronounce your call sign, followed by the procedural word OUT.

When your transmitter is active, your station must be identified once every ten minutes. Identification, while in conversation, usually occurs When establishing initial contact, once every 10 minutes while in conversation, or when terminating contact.

The use of the ITU/ICAO Phonetic Alphabet is the standard phonetic alphabet for Amateur Radio operations. Although some Amateur Radio operators make up phonetics, there is no proof that these achieve better results in achieving clarity. Further, making a habit of using non-standard phonetics can create the habit of using non-standard phonetics, and may carry over to emergency communications and public service communications.

The Federal Information Processing Standard (FIPS) county code is composed from a 2-digit state code and a 3-digit county code. The state code for Idaho is 16. County codes are usually assigned in numerical sequence, using odd numbers to accomodate changes or additions without upsetting the existing order, derived from an alphabetical ordering of counties that starts at number 1.

FIPS Codes for Idaho Counties are as follows:

A directed NET enables the NET Control Station to prioritize requests for resources, to efficiently handle traffic from multiple stations, and to keep a centralized log of requests and responses.

The goal of any communication should be to accurately communicate a message with brevity and clarity while adhering to NET protocols. Successful attainment of these goals results in minimum bandwidth consumption, which leads to the ability of the NET to handle a higher number of traffic messages, the lossless communication of information, resulting in accurate conveying of information, and minimized latency for those stations needing to pass traffic after you.

Non-critical transmissions of a casual nature have no place in emergency NET operations. Although tolerated during scheduled directed NETs, such transmissions should be held until formal NET traffic has been completed.

Tactical call signs are used to indicate the function of a station or the location of a station. Tactical call signs are useful in that new stations can enter the NET and establish contact without knowing the station’s FCC issued call sign. Tactical call signs should be used for all emergency NETs and public service NETs whenever any participating station is not familiar with other stations or their assignments, or whenever communications can be made more efficient by use of tactical call signs.

A repeater is an automated relay station, used to extend line of sight communications.

Ground Wave HF propagation is generally limited to 60 miles or less. Terrain can significantly shorten the distance. For communications on the long end of HF ground wave capabilities, HF may be viable if VHF / UHF repeaters are not available. For communications on the short end of HF ground wave capabilities, VHF / UHF simplex or repeater operation will almost always provide more reliable communications.

HF signals with a low angle of radiation, refracted by the F-Layer of the ionosphere and bouncing off the ground, can result in very long distance communications, and under ideal conditions, world-wide communications capability.

Near Vertical Incidence Skywave (NVIS) propagation provides communications capabilities that overlap ground-wave coverage and extend up to 600 miles approximate. NVIS requires a high angle of radiation, usually achieved by installing a horizontal dipole antenna no higher than 1/8 wavelength above the ground.

Always seek to obtain a copy of the NET script that is used by the NET Control Station (NCS). This document is vital to performing the function of the NET Control Station and is very helpful to participating stations, especially when the participating station is inexperienced with the NET or NET operation.

If you are operating in a noise environment, or have poor signal strength to the station you are communicating with, do not talk louder to get through.  This only makes communications worse.  Further, you could generated clipped audio or exceed width of the receiver pass-band, which will make communications more difficult.  Instead, either talk in a normal voice, or even reduce the amplitude of your speech to avoid clipping and/or driving out of the pass-band.

Digital Mobile Radio, or DMR, is a technology that supports both digital voice and digital message operating modes, with a repeater channel having two time-slots.  Simultaneous but distinct conversations can occur on both time-slots (effectively two-repeaters in one).  When networked via the internet, local, regional, national and international communications are possible.

When participating in simplex net operations, be sure to adjust the squelch to accommodate weak signals.  Also be sure to have all strong stations periodically stand-by so that the NET control station and all participating stations can listen for weak stations.

Operating simplex mode on the input of a repeater will cause interference to a repeater.  In a dispute, the FCC will always favor the coordinated repeater user over the non-coordinated individual user.  Move to a simplex channel to conduct simplex operations.

If a band-plan is published by the frequency coordinating body, the simplex frequencies specified in the band-plan should be used for simplex operations.

If no published band-plan is available, this does not indicate that no band-plan exist.  We just need to reference a repeater directory to determine the band-plan model that is implemented in order to determine what simplex frequencies are available.  Looking at the spacing between channel allocations for coordinated repeaters to establish the channel spacing, and the repeater channel allocation to determine both a base frequency to establish the set of simplex frequencies and the frequencies that are available for simplex operation.  2-Meter simplex occupies the frequency segments between 146.400 to 146.599 MHz and from 147.400 to 147.599 MHz.  This range is left as unallocated for repeater use, in part, because of the 600 kHz split between repeater transmitters and repeater receivers.

With 2-meter repeater allocations occurring on 20 kHz channel spacing, and projecting that channel spacing into the simplex portion of the FM band-plan, this would seem to indicate the following as viable simplex channels on 2-meters:

The 20-kHz channel spacing is optimized to accommodate a standard FM deviation that does not encroach on an adjacent channel and cause interference.  Operation on frequencies between these channels will result in improper channel spacing and can cause interference.  For example, operation on 146.430 will cause interference to both 146.420 and 146.440.

Information in contained in this operating tip, regarding the Idaho 2-Meter band-plan, can be found under the Resources menu on the Idaho ARES web-site.

Note that 146.520 MHz has been established as the National 2-Meter Calling Frequency.  Stations use 146.520 to establish contact and then move to a working frequency.  Stations should avoid using 146.520 MHz for conversation or NET operations.

A talk-group is like a chat room, and usually is specified to cover a geographical area.  For example, talk-group 3116 covers all of Idaho.  Any operator on a DMR repeater or DMR hot-spot that is actively connected to a talk-group can establish communications with operators on any other DMR repeater or DMR hot-spot that is on the same talk-group.  Talk-groups are a shared resource, and require a higher level of operator etiquette.  See the DMR section under the RESOURCES menu for more details.  The ARES ID talk-group has been established on 31016 to support Idaho ARES operations.  It is essential that operators be familiar with the published article on this talk-group, which can be found under the RESOURCES menu.

A repeater can have a set of talk-groups that are always active, and these are referred to as static talk-groups.  A push-to-talk talk-group will temporarily apply the talk-group that is specified by the programming of your radio, and this is a dynamic talk-group.  In the absence of activity, dynamic talk-groups remain active for 15 minutes.  Traffic on a static talk-group can always be heard.  Traffic on a dynamic talk-group can only be heard while that talk-group is active.  The repeater administrator can also program TIMED STATIC TALK-GROUPS, where a talk-group is made to become static based on a schedule.  TIMED STATIC TALK-GROUPS are usually used for scheduled NETs, and allow the NET to be heard beyond the 15-minute period and without requiring activity that would be necessary to keep a dynamic talk-group active.

With time-slotted operation, and the ability to have simultaneous but distinct conversations on time-slot 1 vs time-slot 2, a DMR repeater is especially well suited to serving EMCOMM operations.  A NET can be held on one time-slot, and any traffic can be moved off to a channel on the opposing time-slot, ensuring that communications will not be lost (since the same repeater is being used).

Multi-path phase distortion occurs when a signal takes multiple paths to the receive point and where each of those signal paths are a different length.  The different signal paths arrive at the receive point out of phase, resulting in distortion.  Usually there is a direct path and multiple reflected paths, where the reflected paths may bounce off of buildings or terrain.  In some cases, there may not be a direct path.  It seems counter-intuitive, but REDUCING POWER may provide the best relief.  The goal of reducing power is to cause the weaker reflected paths to become so weak that they are no longer received at the receive point, and this can greatly reduce multi-path phase distortion.  If the station you are working reports multipath phase distortion on your signal, try reducing power.

During simplex operations, it is extremely useful to dispatch a mobile station to a local hill top to act as a relay for NET operations.  If it is SAFE to do so, consider volunteering to drive to a higher location to act as a RELAY station to enable wider coverage by NET operations.

Although often absent from the radio specification, support for a large number of contacts on DMR radios is a necessity.  Group contacts are used to select a talk-group (similar to a chat-room, and often organized geographically and/or by function).  Private contacts are used to display an alias that shows the call sign and name of the operator currently being received.  Private contacts can also be used in channel programming so that traffic is routed to a specific operator (this is not encryption, simply routing, and can be received by a DMR capable scanner).  Because of these three use cases for contacts, support for a large number of contacts is necessary for DMR radios used in the Amateur Radio service, and often the Amateur Radio requirement exceeds the requirement of the LMR / FCC Part 90 service.  At minimum, the radio should have the capability to store as many contacts as channels.  Optimally, the number of contacts should far outnumber the number of channels.  Please consider this when comparing DMR radios.

Amateur Radio has a secondary allocation on the 60-meter band.  The primary allocation is to Federal stations, and through the National Telecommunications Information Administration (NTIA), not the FCC.  As such, the FCC rules for Amateur Radio use of 60-meters follow the NTIA regulations.  All digital emission modes must be centered on the channel bandwidth allocation.  Although not specifically mandated, the implication is that all digital communications occupy the exact same frequency, and therefore require sequential, and not simultaneous use, by all stations.  With Amateur Radio holding a secondary allocation, should a Federal station appear on frequency and issue an order to vacate, Amateur Radio stations must vacate.  This is a rare occurrence, and usually only temporary.  Should this occur, the Federal station is likely to indicate when the frequency is free.

Near Vertical Incidence Skywave (NVIS) provides propagation on HF, from ground-wave propagation distances out to 600-miles.  The highest frequency that NVIS communications can occur on is called the foF2 Critical Frequency, and is usually near 1/3 of the Maximum Usable Frequency.  NVIS communications are rarely possible above 11 MHz.  NVIS provides great potential for intra-state communications for Idaho ARES. NVIS is achieved by raising the angle of radiation, and is best achieved with a horizontal antenna by placing the antenna no higher than 1/8 wavelength above the ground.

Anytime a transmitter and receiver are operating on different frequencies and in close proximity to each other, the transmitter can cause a reduction in receiver sensitivity. This reduction in receiver sensitivity is called desensitization, or desense.

Desense can occur when two stations are operating very close to one another while using the same repeater. When this occurs, one station might not hear the transmissions of the other station because of the loss of receiver sensitivity.

Avoiding desense from other nearby operators requires increasing the physical separation between stations

When desense is present in a repeater system, the repeater receiver is more sensitive when the repeater transmitter is not active. When the repeater transmitter becomes active, the repeater receiver may become less sensitive. If the received signal at the repeater receiver is not sufficiently strong to be heard when the repeater transmitter is active and desense is present in a repeater, the operator may bring up the repeater but cannot hold the repeater up. A repetitive cycle of (A) the repeater hears the operator signal when the repeater transmitter is inactive and then keys the repeater transmitter, and (B) when the repeater transmitter becomes active, the repeater no longer hears the operator, and the repeater un-keys the transmitter after the appropriate squelch tail timer expires, then (A), (B), (A), (B), etc. This cyclic keying and un-keying of the repeater transmitter (often referred to as cyclic ker-chunking, because of the sound that is heard in the receiver that is listening to the repeater, terminates only when the transmitted signal becomes to weak to be heard by the repeater when the repeater transmitter is inactive, the operator ceases transmission, or the transmitted signal becomes sufficiently strong to be heard when the repeater transmitter is active.

Desense in a repeater, and particularly on bands where the frequency separation between the repeater receiver frequency and repeater transmitter frequency is relatively small (such as occurs on 2-meters, where the split is only 600 kHz) is extremely difficult to avoid. Isolation between receiver and transmitter must be very large, on the order of -95 dB, to avoid desensitization in the repeater system. Common methods of addressing this issue is to increase isolation by installing better cavity duplexers, adding additional pass/reject cavity filters, and separating receive and transmit antennas along the axis of polarization.

When operating hand-held portable, a non-vertical antenna will become directional.  When supporting EMCOMM operations while portable, hold your hand-held radio so that the antenna is vertical to avoid directional effects that may attenuate a signal, or to avoid attenuation due to cross-polarization of antennas.  For best results, do not hold your hand-held so that the antenna is at an angle or horizontally.

When conducting mobile operations where multi-path is present (i.e. a transmitted signal takes multiple paths to the receive point), there may be cyclic fading of signals.  When this cyclic fading causes the signal to periodically fade into the noise, the signal is sometimes described as picket fencing, which is a comparison to the signal propagation to how a picket fence would block a signal for a moving station.

If you are operating mobile and this phenomenon results in an inability to communicate, pull-over and stop.  Try to stop in a position where the cyclic fading is at a minimum.  If no signal is present, move the vehicle one quarter wavelength (i.e. 19 inches on 2-meters) and try again.  If communications is not restored by moving one-quarter wavelength, repeat moving one-quarter wavelength and try again.

If you are operating portable, and the station receiving you is experiencing cyclic fading,  stop and check propagation.  Try to stop in a position where the cyclic fading is at a minimum.  If no signal is present, step one quarter wavelength (i.e. 19 inches on 2-meters) and try again.  If communications is not restored by stepping one-quarter wavelength, repeat stepping one-quarter wavelength and try again.

When handling GPS latitude and longitude coordinates, there are three different coordinate systems, and listening for the position of the decimal point is essential to understanding which coordinate system is being used so that position errors can be avoided.

Latitude and longitude can take one of the following formats:

When communicating a latitude / longitude position, a best practice would be to prefix the conveying of the position with a statement that indicates the format.  If you receive a latitude / longitude position that was not  preceded with an announcement of format, pay close attention to where the decimal place appears in the sequence of position figures (numbers).

If you need to convert between coordinate systems, a Coordinate Converter is available under the Resources menu on the Idaho ARES web-site.

Most GPS units can be set to one of any of the formats shown in this operating tip.  It is best if all operations can use the same format.  However, there is no standardization on format.  Each county may use a different format (check with your local SAR unit or Public Safety Dispatch [DO NOT USE 911, USE ONLY A NON-EMERGENCY NUMBER]).  FEMA promotes the use of the United States National Grid coordinate system, however, this system is not adopted by Public Safety and may present confusion when interoperating with served agencies.

During a Directed NET, stations only transmit at the direction of the NET control station (i.e. NCS or NECOS).  Under a Directed NET, the NET control station should call for relay traffic as part of running through the NET script.  Participating stations should not break in with a transmission that announces a relay for a station that was not heard by the NET control station, but should wait until the NET control station calls for relay traffic.  Only after the NET control station calls for relay traffic should stations make a transmission to offer a relay for the unheard station.

You can tune in and listen to HF SSB/CW/DIGITAL communications without a radio.  Visit WebSDR and select the receiver from the large (and growing) list of receivers located internationally.  You will need to have the Java runtime environment installed to use these.

Use of a Read Solomon ID can help identify a digital mode that is difficult to identify visually on the waterfall display.  But transmitting an RSID on all transmissions, or when the mode is easily identifiable (such as PSK31) can be very counter productive.  Use of RSID should be restricted to only difficult to identify modes and then, only when making a general call (i.e. CQ or CQ DX).  Use of RSID outside of this context will result in other stations having to dismiss modal windows, or could cause their digital station to switch frequencies automatically.  Wide use of RSID can actually degrade operations, not help.  Please consider the implications of over using this feature.

Use of RSID in the context of a Directed NET that combines both Voice and Digital traffic should be avoided altogether.  In a Directed NET that combines both Voice and Digital traffic, the NET Control Station should determine the digital mode for all communications, or the two stations passing traffic should agree upon the mode prior to conducing digital communications

Unlike Single Side Band (SSB) operation, where the receiver pass band might simultaneously handle 20 simultaneous PSK31 signals, FM only handles a single signal at any given time.  Because FM only supports a single signal at once, the best choice of digital mode for FM is not based on limiting bandwidth, but should be made based on speed.  The only way that FM can handle a high volume of traffic is if the traffic is passed by the fastest mode available.  PSK31 is an extremely poor choice for FM operations.  Modes like PSK500RC4, which are both fast and support Forward Error Correction (FEC), are much better choices for FM operations.

When a transmitter includes the transmission of a Continuous Tone-Coded Squelch System (CTCSS) tone, or Digital Coded Squelch (DCS), the transmitter is said to be operating in encode. When a receiver decodes the CTCSS or DCS, the receiver is said to be operating in decode.

Typically, your station will run in encode mode to access a repeater. The repeater typically operates in decode.

There are some cases where a repeater in both decode and encode. When a repeater operates in encode, it is possible for your station to run in decode. The advantage of being able to do this is that certain noise sources that are capable of opening the squelch, particularly when mobile, will not be heard when operating in decode.

It should be noted that radios that support DCS always run encode on the transmitter and decode on the receiver when DCS is used.  CTCSS can be turned on or off independently for the transmitter or receiver.  CTCSS decode should only be used on a repeater if the repeater is using CTCSS encode.  Virtually all repeaters use decode (either CTCSS or DCS), and this requires that stations wishing to access the repeater use an appropriate encode mode..

CTCSS and DCS decoders require a significant amount of time to decode the CTCSS or DCS (approximately 1/4 second).  If repeaters are linked (i.e. connected) together, these delays are accumulated through the repeater network.  For this reason, it may be necessary for stations to key their transmitter and then wait for the appropriate delays to pass before speaking in order to be heard.  Some repeaters implement audio delay lines to avoid having to have the operator delay speech relative to transmitter keying.

When operating on a Directed NET, and after receiving a General Call for stations to check in to the NET, where the General Call includes a description that includes your station, you can use an operating practice that will help reduce interference and help ensure that your call sign is heard.  The procedure has the station responding to a General Call:

1. Listen first to ensure no one else is transmitting.  If another station is transmitting, wait until they complete their transmission.

2. Key the transmitter.

3. Announce THIS IS

4. Un-key the transmitter and very briefly listen to see if someone else is making a call at the same time.  The delay should be only long enough to hear another station.  If using this procedure on a repeater, the delay should not allow the repeater squelch talk to drop.

5. If you hear another station in the above step, return to the first step in this procedure.

6. If no other station is heard, re-key the transmitter and announce your call sign.

This procedure reduces the chance of multiple stations making simultaneous transmissions, makes copy much easier for the NET Control Station, provides better assurance that your call sign will be heard by the NET Control Station, and allows NET operations to proceed more efficiently.

If you are using a Push-To-Talk Talk-Group (i.e. a dynamic talk-group on a repeater or any  talk-group on an OpenSpot), and cycle your push-to-talk switch to change talk-groups, DO  NOT issue a station identification until you have listened first to determine if your  identification will result in interference to a QSO that is already in progress.  FCC  regulations do require identification on a frequency, but you have up to 10-minutes to perform  that action.  A talk-group is not a frequency, and if, after listening and determining that the  talk-group is in use and not available for your use, you move to another talk-group, you can  identify (after listening first) on that talk-group and still meet the FCC requirements for  station identification.  Do not interrupt other users by announcing your call sign over an  existing QSO.

When programming radios, apply proper diligence in researching the frequencies that you plan to apply to the radio programming file.  Do not include repeater operating frequencies that represent restricted closed repeater systems or networks unless you have permission to operate on the closed system.  Observing a observing that a repeater is operating on a particular frequency is not sufficient justification to use a repeater.  Consult every resource available to you, including the ARRL Repeater Directory or repeaerbook.com, to ensure that you are not operating on a restricted resource without permission.  FCC Part 97.205(e) allows repeater operators to restrict who can use a repeater system, which provides the authorization to operate a closed repeater system.  These restrictions need to be respected.

During NET operations, there are circumstances where your station may not be able to hear all other stations.  Under these conditions, it is important that you, as a station operator, listen closely to activity on the NET so that you can determine when making a transmission may result in causing interference.  The following examples demonstrate contexts where making a transmission may result in interference.

• When your station has been requested to stand-by.

• When the NET control operator has requested a relay to a station that cannot be heard by your station.

• When the NET control station has indicated that NET control services are not to be available for a short period of time, due to a need to perform a task.

These are just a few examples where failure to maintain NET situational awareness will result in imposing a reduction in NET efficiency upon NET operations.  This all falls within the Amateur Radio operating principle of the importance of listening.

Station operators that are participating in a NET should always maintain a situational awareness of NET context, and should always have a good sense of when it is appropriate or inappropriate to make a transmission.  When it is not appropriate to make a transmission, you should delay your traffic until such a time that a transmission is appropriate.

A failure to maintain NET situational awareness, and then making a transmission at an inappropriate time, may result in interference, and may also require that traffic be repeated.  The impact of repeating traffic is a reduction in the amount of traffic that can be handled by the NET.

Your station operation procedures should never impose a reduction in NET traffic handling capability.  Always maintain NET situational awareness and think before you key your transmitter.

The following call signs are assigned for FEMA operations.  If these call signs appear on an EMCOM NET, they should be given higher priority entry into the NET than standard Amateur Radio stations.

Note that each of these call signs has the word FEMA contained within the call sign, with the call district numerical designator inserted after the letter F.

This block of 40 call signs are to be considered as Federal, and are used only for emergency use.  Use of these call signs is most likely to be encountered on the interoperability frequencies that comprise the 60-meter band.

This information originated from the FEMA SHARES National Teleconference of 5 September 2017.

The term x-ray x-ray is not normally encountered during Amateur Radio operations.  However, with the availability of the 60-Meters band, and the ability to interoperate with other services directly on that band, an Amateur Radio operator may encounter the term x-ray x-ray.

When a station or station operator has a prohibition to disclose Personally Identifiable Information (PII), the station operator will respond to a query for PII with x-ray x-ray.  Personally  Identifiable Information (PII) can include name, location, phone number, or any information that  may allow someone to locate and/or identify an individual.  Federal services that my interact directly with an Amateur Radio station on the 60-Meter band may include FEMA, Army MARS, Air Force MARS, United States Coast Guard Auxiliary, and others.  Some of these services have regulations that prohibit disclosure of PII.

This term may be heard on 60-M interoperability NETs, when a NET control operator makes a query to disclose operator name or location.  If you are operating such a NET and receive a response of x-ray x-ray, please note the response in the NET or radio log and do not query the station operator further.

If you recognize a station operator that is interoperating with Amateur Radio stations, but not operating under an Amateur Radio call sign, do not address that station operator by name, and take care not to disclose any PII associated with that station or station operator.

It is very important, and especially so when interoperating with other radio services on the 60-meter interoperability channels, that stations use the ICAO Phonetic Alphabet.  Do not use made-up DX-er phonetics.

Federal, State and Local agencies all use the Incident Command System, which relies upon Plain Language and the ICAO Phonetic Alphabet.  The purpose of the use of phonetics is to clarify the traffic being passed.  When non-standard phonetics are used to convey traffic to an agency, the result is to achieve the opposite of what is intended, and the operator using non-standard phonetics actually introduces confusion instead of clarity.  This results in requests to repeat traffic, which adversely impacts the network by reducing the amount of traffic that can be handled in a given period of time (i.e. excessive bandwidth consumption).

Note that exercise after action reports from FEMA, for exercises and EMCOMM activities that involve interaction with Amateur Radio operators, using the 60-meter interoperability channels, often cite improper use of phonetics as an issue that need to be addressed by Amateur Radio operators.

Use of the proword ROGER should not involve repeated use of the word.  To acknowledge a transmission, the proper use of the proword ROGER is to state your call-sign, followed by ROGER, OUT when no response is needed or ROGER, OVER when a response is needed.

The following is an example of the proper use of the proword ROGER, and requires no response:

N7QRS, ROGER, OUT

The following is an example of the proper use of the proword ROGER, and requires a response:

N7QRS, ROGER, OVER

The following is an example of improper use of the proword ROGER:

N7QRS, ROGER ROGER ROGER

Note that exercise after action reports from FEMA, for interoperability exercises and EMCOMM activities that involve interaction with Amateur Radio operators, using the 60-meter interoperability channels, often cite improper use of the prowords as an issue that need to be addressed by Amateur Radio operators.

All Amateur Radio operators are requested to set a higher standard by setting an example of proper use of this proword.  Such examples serve to promote proper radio operating procedure.

When participating in an Exercise or EMCOMM activity, keep your traffic germane to the activity and do not introduce unnecessary conversational language.  Exercise and EMCOMM activities often employ the use of a SITREP (i.e. Situational Report) or the conveyance of an ICS-213 Message Form.  Adding language that is not part of the requested message structure for NET activities results in consuming time, and a reduction in the amount of traffic that can be handled by the NET in a given period of time.

Note that exercise after action reports from FEMA, for exercises and EMCOMM activities that involve interaction with Amateur Radio operators, using the 60-meter interoperability channels, often cite excessive conversational language as an issue that need to be addressed by Amateur Radio operators.

All Amateur Radio operators are requested to set a higher standard by setting an example of proper use of bandwidth.  Such examples serve to promote proper radio operating procedure.

When operating in a Directed NET environment, whether a mixed mode NET that includes both voice and digital, or a single mode NET that contains only digital, participating stations should not make transmissions unless directed to do so.  Stations emitting unauthorized asynchronous transmissions can cause interference to NET operations, resulting in:

• Loss of data fidelity to stations that are copying an authorized transmission.

• A need to retransmit an authorized message, resulting in a loss of network bandwidth.

If your station has no copy on the NET Control Station (NECOS), do not make a transmission in the blind.  By attaining and maintaining NET situational awareness, you can determine when other stations are responding to general NET call, and respond at that time, or wait until an Alternate NET Control Station (ANECOS) relay station issues a NET call, and then respond to the ANECOS station.

NECOS and ANECOS stations should make it a point to call for relay services when making a NET call, or when issuing a procedural change to NET operations (e.g. changing NET mode, operating frequency, etc.).  Structured relay services are critical to helping stations that do not have copy on ANECOS to establish NET situational awareness.  Non-structured Relay Services can negatively impact NET operations.

At all times, station operators should attempt to maintain network situational awareness (what is going on right now, at this instance in time), and avoid any operations that introduce chaos and result in a negative impact network operations.  If your station cannot copy NECOS or ANECOS, or any other authorizing station, you should avoid transmission until such time that you can establish NET context, and then, only transmit when situational awareness indicates that making a transmission will not be detrimental to NET operations.  

Station operators should strive to achieve efficient operations.  Transmissions should be made with the goal of accurately conveying information with a minimal amount of time.  This goal serves to enable the NET to carry the maximum amount of traffic in the minimum amount of time.

Order is the basis of good circuit (i.e. NET) discipline.

All Amateur Radio operators are requested to set a higher standard by setting an example by properly establishing contact prior to passing traffic.  Such examples serve to promote proper radio operating procedure.

Many Exercises and EMCOMM activities utilize communications methodologies that an individual operator may not be familiar with, or may not have the capability to handle.  For example, interoperability exercises on the 60-meter interoperability channels, which often have Amateur Radio operators communicating directly with Federal stations (i.e. FEMA Idaho Office of Emergency Services, MARS, etc.), will use a mixture of voice communications and various digital communications to convey traffic.

The reason for this mixture is that, with Forward Error Correction and Automatic Repeat Request (ARQ) technology, digital modes can offer both guaranteed delivery of data and guaranteed fidelity of data, and this represents a capability that is not always possible via voice communications.  Further, digital modes can convey traffic at a much faster rate than voice transmission can, enabling the NET to handle a higher volume of traffic in a given time period that would be possible with voice communications..

Voice only stations, hearing digital transmissions, should never make an assumption that digital transmissions are not related to the exercise, and certainly should not make negative voice comments, which are often unidentified, that admonish the digital station after completion of a digital transmission.  Such comments may have the the good intention of keeping the frequency clear for traffic, but the operator, who lacks context from not being able to monitor the digital transmission, or because they are unaware that digital transmissions are part of the structured communications operation, are actually having the opposite effect to what was intended by the comment.

Comments never provide assistance to a NET activity, unless specifically made or requested by the NET control station.

If you need additional context as to what resources are being used in a NET activity that is supporting an exercise or EMCOMM situation, establish contact with the NET control station and ask.  Do not interfere with operations that you are not familiar with my making over the air comments.

The five 60-meter channels have a primary allocation to Federal stations, which include FEMA, SHARES, and MARS stations.  Amateur Radio has a secondary allocation on these channels, and must yield to Federal stations when directed by a Federal agency to do so.

Because of this shared dual allocation, the 60-meter band provides the only opportunity for the Amateur Radio operator to directly interact with Federal agencies.

FEMA Region X, which comprises Alaska, Idaho, Oregon and Washington, conducts a monthly NET to test interoperability between Federal stations and Amateur Radio stations.  This activity includes the use of both voice and digital communications.  For digital transmissions, Amateur Radio operators may encounter WINLINK being used for HF email, and MT63-2KL or MT63-1KL (supported by the free FLDIGI application)  used for general text communications.

Interoperability Exercises and COMMEXs (i.e. Communications Exercises) that are conducted on the 60-meter interoperability channels are often conducted under the authority of a MARS program, or under the authority of the SHARES IWG (i.e. Interoperability Working Group).  In almost all cases, an operational order is issued that contains the following information:

• Event Simulation Type

• Affected Area

• Operational Period

• Situation Description

• Operational Instructions

• SPOTREP (i.e. Spot Reporting) Instructions

The operational instructions may impose limitations upon participating stations.  For example, it is not unusual for the operational instructions to restrict participation of stations to those at specific locations (i.e. a station located at a Federal, State, County or Critical Infrastructure/Key Resource partner's facility).

The SPOTREP instructions will indicate the format and content of information to be conveyed over radio (i.e. what data and the order of that data).  Locations are usually indicated with a Federal Information Processing Standard (FIPS) code, which indicates both the State and County in a 5-digit number (see the Reference menu item found under the Resources menu on this page).  Deviation from the instructions will result in imposing additional work load upon the Federal liaison station.  Further, stations that generate reports, when the station is explicitly excluded from participation based on the operational instructions will result in unnecessary traffic, additional work-load for the liaison station, and the loss of network bandwidth capability (i.e. less real traffic can be handled due to the time taken handling excluded traffic).  In some cases, this imposes data processing tasks upon the FEMA Interoperability Working Group, using a very small paid staff.  The ripple effect is that tax dollars may be spent performing tasks that are neither scheduled or funded, resulting in delaying of completion of other scheduled and funded tasks.

It is commendable that so many Amateur Radio operators want to participate, but it is also vitally important that the operational instructions be adhered to.  Interoperability SPOTREP instructions often use FIPS codes to indicate the state and county of origin, as shown below:

If you hear an interoperability NET, COMMEX, Exercise or EMCOMM operation, please make an attempt to obtain the operational instructions.  If you cannot locate the operational instructions (under the Activities menu on this web-site), determine an idle period, where the NET control station is idle, and call the NET control station.  Upon establishing contact with the NET control station, ask the NET control station to summarize the operational instructions, including any exclusions and SPOTREP instructions.

If you need to know what the operational instructions are, chances are that other operators need this same information.  Triggering an on-NET announcement, if not done with excessive frequency, can have the positive effect of eliminating disqualified traffic, and can only serve to help participating stations in successfully completing the operation.

When engaged in providing radio communications for Public Service and / or Emergency Communications, and where more than one radio operator is manning a radio facility, maintain audio silence when receiving a message.

If one operator is not able to copy the message, another operator who is present at the same radio facility may be able to copy the message.

If a radio operator is not able to copy a message, and then makes comments while the message is still being received (i.e. midway through the message), this will almost certainly result in no operator copying the message, and increase the probability that a request for repeated transmission will be necessary.  Any request for retransmission degrades the bandwidth capabilities of communication by reducing the number of messages that can be handled in a given period of time.

Maintain local silence while receiving a message to increase the probability that at least one operator may copy the message successfully.

It is our natural response, when not being heard, to talk louder in an effort to be heard.  With a weak signal on FM communications, where the receiver is poorly quieted (i.e. the signal presents a very low signal to noise ratio), this natural tendency to speak louder is counter productive and can lead to the receiver squelch circuit closing and muting the audio.

The best practice, with analog FM communications, is to lower the voice level slightly.  It is far better to have low audio that maintains the receiver squelch gate in an open / un-muted condition than to have loud audio the results in a squelch gate operating in a closed / muted condition.

When operating as a NET control operator in a Public Service and / or Emergency Communications environment, it is common to receive requests that are either generated or forwarded from satellite stations that are participating in the NET.  It is also common for the NET control operator to defer responding to these requests due to work load or the need to refer the request to a third party.

In order to ensure that the request is addressed, and to avoid loss of network bandwidth from satellite stations repeating a request when no response is received, the NET control operator should keep a log of all outstanding requests.

The log should include:

• Description of request
• Date and time of initial request
• Description of request response
• Date and time of response to request
• Date and time of cancellation of request by the requestor

A request can only be cancelled with the approval of the requestor.

The NET control operator should periodically review the list of requests to determine if a request is outstanding, and follow up on any outstanding request as appropriate.

At the end of the communications event, there should be no outstanding requests remaining before demobilizing the communications NET.

During NET operations, the unstructured calling out of relays often occurs when a satellite station hears something that is not heard by NET control (NECOS).  These unstructured announcements by satellite stations often create interference to a call in process and can make operations more difficult for a NET control operator.

To mitigate this issue, the NET control operator should periodically issue requests for relay, and participating stations should refrain from calling out a relay until the NET control operator makes a request for relay.  This simple process avoids contributing to interference issues that arise from simultaneous transmission, and especially so when the relaying station is not hearing other traffic that the NET control operator is hearing.  It also supports the concept of a Controlled NET, where stations ONLY transmit at the direction of the NET control (the purpose of which is to maximize communications efficiency and the ability of the NET to handle the maximum possible amount of traffic in a fixed period of time).

NET scripts for a controlled NET should state that relays should be deferred until the NET control operator asks for relayed traffic.  Further, the NET control operator MUST periodically request relay traffic.

For example, a statewide HF network might include the following NET script steps:

• NECOS: Now calling for checkins from stations in District 1
• NECOS: Are there any relays?
• NECOS: Now calling for checkins from  stations in District 2
• NECOS: Are there any relays?
• NECOS: Now calling for checkins from  stations in District 3
• NECOS: Are there any relays?
• NECOS: Now calling for checkins from  stations in District 4
• NECOS: Are there any relays?
• NECOS: Now calling for checkins from  stations in District 5
• NECOS: Are there any relays?
• NECOS: Now calling for checkins from  stations in District 6
• NECOS: Are there any relays?
• NECOS: Now calling for checkins from any late or missed stations
• NECOS: Are there any relays?

The following definitions are offered to clarify NET operation terminology:

• NECOS: Net Control Station
• ANECOS: Alternate Net Control Station
• OVER: Used to terminate a transmission where a response is required.
• OUT: Used to terminate a transmission where no response is required.
• WAIT: All stations should wait, and avoid transmission, until NECOS / ANECOS resumes operations.
• ROGER: Used to acknowledge transmission.  Should only be used once (i.e. ROGER, not ROGER, ROGER, ROGER).
• SAY AGAIN: Request to repeat last transmission.
• ALL BEFORE: Repeat all before WORD or PHRASE.
• ALL AFTER: Repeat all after WORD or PHRASE.
• CLOSE DOWN: Issued by NECOS to indicate that the NET is terminated.
• CORRECT: What you have transmitted is correct
• FIGURES: Precedes numbers within phonetically transmitted text.
• I READ BACK: Used to verify the transmission to repeat back to the sender what was sent.
• I SPELL: Precedes phonetic word.
• DIRECTED NET: NECOS / ANECOS assumes NET control and stations only transmit at the direction of NET control.
• FREE NET: Stations are allowed to contact each other directly without the intervention of NECOS / ANEOCS.
• WILCO: I will comply with the request from NECOS / ANECOS.

The above is particularly appropriate for communications with FEMA (see interoperability exercise announcements / schedule).

Calling frequencies are established for the purpose of contacting a station, but are not intended to be used for holding a conversation or any type of NET operations.  Once contact has been established on a calling frequency, stations should then switch to a working frequency.  This leaves the calling frequency free for stations to monitor for contact and avoids interference to establishing such a contact.

Calling frequencies can be found in the ARRL Repeater Directory and in publications provided by local Frequency Coordinating organizations or individuals.

On the 2-meter band, 146.520 MHz has been established as the National Calling Frequency.  Once contact has been established on 146.520 MHz, stations should then move to one of the following non-calling 2-meter frequencies:

146.420	147.420
146.440	147.440
146.480	147.480
146.500	147.500
	147.520
146.540	147.540
146.560	147.560
146.580	147.580

The THIS-IS protocol is specifically designed to minimize the occurrence of simultaneous transmission from multiple stations when a NET is accepting check-ins of stations entering the NET. The purpose of the THIS-IS protocol is to reduce interference, improve the ability of the NET control operator to obtain clean copy of the call signs of stations entering the NET, and to reduce the number of NET calls required to solicit stations entering the NET. The result is a smoother and more efficient execution of the steps in the NET script with maximized time efficiency.

Listening to verify the channel is clear, and especially between speaking THIS-IS and speaking the station call-sign is critical to reducing the occurrence of simultaneous transmission by multiple stations.

For the NET control operator, who is accumulating the call signs after issuing a call to solicit stations to enter the NET, simultaneous transmission results a significant increase in work load that is imposed by difficulty in copy of any call sign, results in a subsequent need to make additional solicitations for stations to join the NET (including possible solicitations for clarification of one or more call signs), and contributes to unnecessary consumption of NET bandwidth (i.e. consumption of time that reduces the amount of traffic that can be handled in a given period of time).

An operator who uses a portion of the THIS-IS protocol, but does not un-key and listen between speaking THIS-IS and speaking the station call sign often creates a worse situation for the NET control operator in that the transmission is then excessively long, without contributing to NET efficiency, and results in an increase in simultaneous transmission among stations entering the NET.

One of the primary goals of NET operation is to collectively provide the ability to pass traffic with 100% data fidelity and with a minimum of time consumption. This goal is desired during a scripted NET protocol and when passing traffic through the network. Proper use of the THIS-IS protocol is an important tool that all operators can use to help the network achieve this goal and to reduce the work load of the network control operators.

When calling another station, the called station call sign is spoken first and is followed by the calling station call sign.  For example, if N7QRM is calling K7QRT, the following phrase is spoken to issue the call sign:  K7QRT N7QRM

Historically, a CW (ie. morse) calling sequence uses the PROSIGN of DE, which means FROM between the call signs.  In CW, the same calling task is accomplished by K7QRT DE N7QRM

Why is this important?  There are several reasons.  The calling sequence also serves to identify your station.  When the calling sequence is inverted (ie. N7QRM K7QRT) this makes it appear that K7QRT is transmitting when it is N7QRM that is transmitting, and this presents a misidentification of the calling station.  This can lead to someone who is familiar with N7QRM thinking that an unauthorized individual is using the N7QRM call sign.  This could also result in attributing N7QRM with station operation, including possible NET procedural violations or even potential FCC regulatory violations.

If an inverted sequence is used, you must use language to make it clear that the sequence is being inverted.  For example: This is N7QRM looking for K7QRT.

Prowords, or Procedural Words, serve to provide common terminology in performing the art of communications, and especially so in resolving communications difficulties.  They are a critical component of NET management, traffic handling and communications protocols.

The proper use and application of prowords is intended to provide both brevity and clarity.  When used incorrectly, brevity may be sacrificed by consuming available network bandwidth with unnecessary traffic.  Unnecessary consumption of network bandwidth reduces the traffic handling capacity of the network.

The WORDS TWICE proword is used to direct another station, under difficult communications conditions, to repeat the words twice.  This proword is as applicable to the use of other PROWORDS as to passing traffic.

The WORDS TWICE proword is usually requested in passing of traffic.  It is not typically applied to prowords that are used for communications protocols.  For example, it would be unusual to to apply WORDS TWICE to the following prowords: OVER, OUT, ROGER, NOTHING HEARD, WAIT or WAIT OUT.

WORDS TWICE is applicable to passing of traffic when circumstances dictate such a need.  As an example, assume that an operator passes traffic that states EVACUATION SHELTER REQUESTS FIGURES 2 CASES OF BOTTLED WATER, speaking at a speed that is no faster than the traffic can be written down.  If communications conditions are difficult, and the receiving station does not receive this traffic accurately, the receiving station operator may combine the prowords SAY AGAIN and WORDS TWICE.  The transmitting station operator would then retransmit the traffic as: EVACUATION EVACUATION SHELTER SHELTER REQUESTS REQUESTS FIGURES 2 FIGURES 2 CASES CASES OF OF BOTTLED BOTTLED WATER WATER, followed by the proword OVER to indicate that a response is desired.  Note that the proword OVER is stated only once.