Directed net - Revision history

Carlb: intro

2009-09-14T19:45:10Z

intro

← Older revision		Revision as of 12:45, 14 September 2009
Line 5:		Line 5:
	The ''directed net'' structure reduces the number of message collisions, where multiple stations attempting to transmit simultaneously could otherwise cause unwanted interference to communication within the group.		The ''directed net'' structure reduces the number of message collisions, where multiple stations attempting to transmit simultaneously could otherwise cause unwanted interference to communication within the group.

	Directed nets are commonly used for scheduled on-air meetings of individual radio-amateur groups. They are also activated to co-ordinate disaster and [[emergency communication]] between volunteers during local events and to co-ordinate collection of [[weather spotting]] activity ~~in response to~~ a regional storm watch or warning.		Directed nets are commonly used for scheduled on-air meetings of individual radio-amateur groups. They are also activated to co-ordinate disaster and [[emergency communication]] between volunteers during local events and to co-ordinate data collection and [[weather spotting]] activity during a regional storm watch or warning.

	== Net scripts ==		== Net scripts ==

Carlb: /* Tactical callsigns */

2009-09-14T04:20:56Z

Tactical callsigns

← Older revision		Revision as of 21:20, 13 September 2009
Line 57:		Line 57:
	== Tactical callsigns ==		== Tactical callsigns ==

	Stations deployed to provide communication service during public events, or as part of [[emergency communication]]s operation, will often bear an additional identifier meaningful within the individual net. While these do not fully replace the station's globally-unique government-issued callsigns, they are employed to address traffic within an net based on the rôle a station at a specific location plays in the larger operation. Each deployed [[ARES]] net at an event will typically contain one ''control'', various fixed stations designated by place name (a town or location) and/or individual mobile units labelled by purpose (''admin-one'', ''repair 2''...) depending on the incident and the needed response.		Stations deployed to provide communication service during public events, or as part of [[emergency communication]]s operation, will often bear an additional identifier meaningful within the individual net. While these do not fully replace the station's globally-unique government-issued callsigns, they are employed to address traffic within an net based on the rôle a station at a specific location plays in the larger operation. Each deployed [[ARES]] or [[emergency communication\|emergency service]] net at an event will typically contain one ''control'', various fixed stations designated by place name (a town or location) and/or individual mobile units labelled by purpose (''admin-one'', ''repair 2''...) depending on the incident and the needed response.

	While there is normally only one ''control'' node on-frequency in the same net at any time, procedure should provide for another station to seamlessly take over the ''control-one'' identity and position if the existing ''control-one'' station loses backup power or has to abruptly leave the air for any reason. The use of tactical calls ensures that inbound enquiries to the net can continue to be addressed to ''control'' without regard for which individual licensed station on the net is currently occupying the rôle.		While there is normally only one ''control'' node on-frequency in the same net at any time, procedure should provide for another station to seamlessly take over the ''control-one'' identity and position if the existing ''control-one'' station loses backup power or has to abruptly leave the air for any reason. The use of tactical calls ensures that inbound enquiries to the net can continue to be addressed to ''control'' without regard for which individual licensed station on the net is currently occupying the rôle.

	{{operation}}		{{operation}}

Carlb: /* Net scripts */

2009-09-14T03:41:39Z

Net scripts

← Older revision		Revision as of 20:41, 13 September 2009
Line 35:		Line 35:
	Individual stations seeking to address the net send their callsigns, usually in groups of no more than two or three. The net co-ordinator acknowledges each station by callsign, then invites the first station to send its traffic. Once all identified stations in turn have sent any messages, the control operator will ask for the next series of check-in requests.		Individual stations seeking to address the net send their callsigns, usually in groups of no more than two or three. The net co-ordinator acknowledges each station by callsign, then invites the first station to send its traffic. Once all identified stations in turn have sent any messages, the control operator will ask for the next series of check-in requests.

	If traffic is received from station which is not audible to everyone on the net, but which is receivable at the ''net control'' station, the net co-ordinator may repeat the message manually or ask to verify that the intended recipient station copied the traffic. This is not commonly an issue on nets conducted using a local [[VHF]]/[[UHF]] [[repeater]], but will arise on [[HF]] or other [[simplex]] nets.		If traffic is received from a station which is not audible to everyone on the net, but which is receivable at the ''net control'' station, the net co-ordinator may repeat the message manually or ask to verify that the intended recipient station copied the traffic. This is not commonly an issue on nets conducted using a local [[VHF]]/[[UHF]] [[repeater]], but will arise on [[HF]] or other [[simplex]] nets.

	Once all stations in a group (such as mobiles) have finished, the next group is invited to check in to the net. Once all stations wishing to send traffic have done so, time may be allocated for announcements or other specific items before ending the directed net.		Once all stations in a group (such as mobiles) have finished, the next group is invited to check in to the net. Once all stations wishing to send traffic have done so, time may be allocated for announcements or other specific items before ending the directed net.

Carlb: /* Net scripts */

2009-09-14T03:16:23Z

Net scripts

← Older revision		Revision as of 20:16, 13 September 2009
Line 34:		Line 34:

	Individual stations seeking to address the net send their callsigns, usually in groups of no more than two or three. The net co-ordinator acknowledges each station by callsign, then invites the first station to send its traffic. Once all identified stations in turn have sent any messages, the control operator will ask for the next series of check-in requests.		Individual stations seeking to address the net send their callsigns, usually in groups of no more than two or three. The net co-ordinator acknowledges each station by callsign, then invites the first station to send its traffic. Once all identified stations in turn have sent any messages, the control operator will ask for the next series of check-in requests.

			If traffic is received from station which is not audible to everyone on the net, but which is receivable at the ''net control'' station, the net co-ordinator may repeat the message manually or ask to verify that the intended recipient station copied the traffic. This is not commonly an issue on nets conducted using a local [[VHF]]/[[UHF]] [[repeater]], but will arise on [[HF]] or other [[simplex]] nets.

	Once all stations in a group (such as mobiles) have finished, the next group is invited to check in to the net. Once all stations wishing to send traffic have done so, time may be allocated for announcements or other specific items before ending the directed net.		Once all stations in a group (such as mobiles) have finished, the next group is invited to check in to the net. Once all stations wishing to send traffic have done so, time may be allocated for announcements or other specific items before ending the directed net.

Carlb: /* Tactical callsigns */

2009-09-14T03:04:36Z

Tactical callsigns

← Older revision		Revision as of 20:04, 13 September 2009
Line 55:		Line 55:
	== Tactical callsigns ==		== Tactical callsigns ==

	Stations deployed to provide communication service during public events, or as part of [[emergency communication]]s operation, will often bear an additional identifier meaningful within the individual net. While these do not fully replace the station's globally-unique government-issued callsigns, they are employed to address traffic within an net based on the rôle a station at a specific location plays in the larger operation. Each deployed [[ARES]] net at an event will typically contain one ''control'', various fixed stations designated by place name and/or individual mobile units labelled by purpose (''admin-one'', ''repair 2''...) depending on the incident and the needed response.		Stations deployed to provide communication service during public events, or as part of [[emergency communication]]s operation, will often bear an additional identifier meaningful within the individual net. While these do not fully replace the station's globally-unique government-issued callsigns, they are employed to address traffic within an net based on the rôle a station at a specific location plays in the larger operation. Each deployed [[ARES]] net at an event will typically contain one ''control'', various fixed stations designated by place name (a town or location) and/or individual mobile units labelled by purpose (''admin-one'', ''repair 2''...) depending on the incident and the needed response.

	While there is normally only one ''control'' node on-frequency in the same net at any time, procedure should provide for another station to seamlessly take over the ''control-one'' identity and position if the existing ''control-one'' station loses backup power or has to abruptly leave the air for any reason. The use of tactical calls ensures that inbound enquiries to the net can continue to be addressed to ''control'' without regard for which individual licensed station on the net is currently occupying the rôle.		While there is normally only one ''control'' node on-frequency in the same net at any time, procedure should provide for another station to seamlessly take over the ''control-one'' identity and position if the existing ''control-one'' station loses backup power or has to abruptly leave the air for any reason. The use of tactical calls ensures that inbound enquiries to the net can continue to be addressed to ''control'' without regard for which individual licensed station on the net is currently occupying the rôle.

	{{operation}}		{{operation}}

Carlb: /* Net scripts */

2009-09-14T03:02:38Z

Net scripts

← Older revision		Revision as of 20:02, 13 September 2009
Line 16:		Line 16:
	This is (name)_________ , (call sign)___________, Net Control Operator for the ______ Net.		This is (name)_________ , (call sign)___________, Net Control Operator for the ______ Net.
	This net meets at (time)_________ on (frequency)_____________ for the purpose of __________________.		This net meets at (time)_________ on (frequency)_____________ for the purpose of __________________.

	This net is open to anyone interested in (purpose)_____________ in (region served)______________.		This net is open to anyone interested in (purpose)_____________ in (region served)______________.

	If at any time during the Net, should an emergency arise, please notify Net Control. We will stand		If at any time during the Net, should an emergency arise, please notify Net Control. We will stand
	by and allow those in need access to this frequency.		by and allow those in need access to this frequency.

Carlb: /* Net scripts */

2009-09-14T03:02:00Z

Net scripts

← Older revision		Revision as of 20:02, 13 September 2009
Line 11:		Line 11:
	A scheduled net will often use a pre-defined script which identifies the purpose of the net, invites stations to "check in", allocates time for individual stations to send their traffic sequentially, delivers any announcements and then ends the directed net once all traffic is completed.		A scheduled net will often use a pre-defined script which identifies the purpose of the net, invites stations to "check in", allocates time for individual stations to send their traffic sequentially, delivers any announcements and then ends the directed net once all traffic is completed.

	This script is an example, based on a weekly on-air meeting of a local radio-amateur group.<sup>[http://fcares.net/?modules=2mnet]</sup> While elements of the basic structure are similar between different nets, individual organisations can and do adapt the general structure to suit their needs.		This script, as an example, is based on a weekly on-air meeting of a local radio-amateur group.<sup>[http://fcares.net/?modules=2mnet]</sup> While elements of the basic structure are similar between different nets, individual organisations can and do adapt the general structure to suit their needs.

	<pre>		<pre>
	This is (name)_________ , (call sign)___________, Net Control Operator for the ______ Net. This net meets at (time)_________ on (frequency)_____________ for the purpose of __________________. This net is open to anyone interested in (purpose)_____________ in (region served)______________. If at any time during the Net, should an emergency arise, please notify Net Control. We will stand by and allow those in need access to this ~~repeater~~.		This is (name)_________ , (call sign)___________, Net Control Operator for the ______ Net.
			This net meets at (time)_________ on (frequency)_____________ for the purpose of __________________.
			This net is open to anyone interested in (purpose)_____________ in (region served)______________.
			If at any time during the Net, should an emergency arise, please notify Net Control. We will stand
			by and allow those in need access to this frequency.

	Is there any priority or emergency traffic at this time?		Is there any priority or emergency traffic at this time?
Line 38:		Line 42:

	<pre>		<pre>
	Last call for any stations wishing to check-in to the __________ net, or any further comments or questions.		Last call for any stations wishing to check-in to the __________ net,
			or any further comments or questions.

	There being no further check-ins or comments, this is (call sign)__________ closing the _________ Net, Thanks to all for participating. This frequency is now returned to regular amateur use. 73 to all.		There being no further check-ins or comments, this is (call sign)__________
			closing the _________ Net, Thanks to all for participating.

			This frequency is now returned to regular amateur use. 73 to all.
	</pre>		</pre>

Carlb: /* Net scripts */

2009-09-14T03:00:36Z

Net scripts

← Older revision		Revision as of 20:00, 13 September 2009
Line 8:		Line 8:

	== Net scripts ==		== Net scripts ==

			A scheduled net will often use a pre-defined script which identifies the purpose of the net, invites stations to "check in", allocates time for individual stations to send their traffic sequentially, delivers any announcements and then ends the directed net once all traffic is completed.

			This script is an example, based on a weekly on-air meeting of a local radio-amateur group.<sup>[http://fcares.net/?modules=2mnet]</sup> While elements of the basic structure are similar between different nets, individual organisations can and do adapt the general structure to suit their needs.

			<pre>
			This is (name)_________ , (call sign)___________, Net Control Operator for the ______ Net. This net meets at (time)_________ on (frequency)_____________ for the purpose of __________________. This net is open to anyone interested in (purpose)_____________ in (region served)______________. If at any time during the Net, should an emergency arise, please notify Net Control. We will stand by and allow those in need access to this repeater.

			Is there any priority or emergency traffic at this time?
			</pre>

			This enquiry is fingers always crossed greeted with utter silence. So far, so good. Having received no emergency traffic, the net control operator is then free to ask for stations which have routine traffic to identify themselves.

			<pre>
			Are there any portable or mobile stations wishing to check in at this time?

			Are there any homebase/fixed stations wishing to check in at this time?
			</pre>

			Individual stations seeking to address the net send their callsigns, usually in groups of no more than two or three. The net co-ordinator acknowledges each station by callsign, then invites the first station to send its traffic. Once all identified stations in turn have sent any messages, the control operator will ask for the next series of check-in requests.

			Once all stations in a group (such as mobiles) have finished, the next group is invited to check in to the net. Once all stations wishing to send traffic have done so, time may be allocated for announcements or other specific items before ending the directed net.

			<pre>
			Do we have any stations with announcements, bulletins, or news of general interest to the net?
			</pre>

			Depending on the organisation operating the net and its purpose, a window may be allocated to receive announcements of upcoming events, radio-amateur equipment for trade, items of trivia or other matters of a general nature.

			<pre>
			Last call for any stations wishing to check-in to the __________ net, or any further comments or questions.

			There being no further check-ins or comments, this is (call sign)__________ closing the _________ Net, Thanks to all for participating. This frequency is now returned to regular amateur use. 73 to all.
			</pre>

	== Tactical callsigns ==		== Tactical callsigns ==

Carlb: /* Tactical callsigns */

2009-09-14T02:38:39Z

Tactical callsigns

← Older revision		Revision as of 19:38, 13 September 2009
Line 11:		Line 11:
	== Tactical callsigns ==		== Tactical callsigns ==

	Stations deployed to provide communication service during public events, or as part of [[emergency communication]]s operation, will often bear an additional identifier meaningful within the individual net. While these do not fully replace the station's globally-unique government-issued callsigns, they are employed to address traffic within an net based on the rôle a station at a specific location plays in the larger operation. Each deployed [[ARES]] net at an event will typically contain one ''control'', various fixed stations designated by place name and/or individual mobile units labelled by purpose (''admin 1'', ''repair 2''...) depending on the incident and the needed response.		Stations deployed to provide communication service during public events, or as part of [[emergency communication]]s operation, will often bear an additional identifier meaningful within the individual net. While these do not fully replace the station's globally-unique government-issued callsigns, they are employed to address traffic within an net based on the rôle a station at a specific location plays in the larger operation. Each deployed [[ARES]] net at an event will typically contain one ''control'', various fixed stations designated by place name and/or individual mobile units labelled by purpose (''admin-one'', ''repair 2''...) depending on the incident and the needed response.

			While there is normally only one ''control'' node on-frequency in the same net at any time, procedure should provide for another station to seamlessly take over the ''control-one'' identity and position if the existing ''control-one'' station loses backup power or has to abruptly leave the air for any reason. The use of tactical calls ensures that inbound enquiries to the net can continue to be addressed to ''control'' without regard for which individual licensed station on the net is currently occupying the rôle.

	{{operation}}		{{operation}}

Carlb: intro

2009-09-14T02:32:49Z

intro

New page

:''This is an introductory explanation of basic operating procedures for nets. For lists of individual local and regional [[nets]], see the [[nets table]].''

A ''net'' or ''directed net'', in radio-amateur operating procedure, is an organised meeting of multiple stations on a common frequency at a scheduled time. One station is designated to serve as ''net control''; all requests to deliver message traffic to the net are initiated by sending an identifier or callsign to the ''control'' station and waiting for that station to reply before continuing.

The ''directed net'' structure reduces the number of message collisions, where multiple stations attempting to transmit simultaneously could otherwise cause unwanted interference to communication within the group.

Directed nets are commonly used for scheduled on-air meetings of individual radio-amateur groups. They are also activated to co-ordinate disaster and [[emergency communication]] between volunteers during local events and to co-ordinate collection of [[weather spotting]] activity in response to a regional storm watch or warning.

== Net scripts ==

== Tactical callsigns ==

Stations deployed to provide communication service during public events, or as part of [[emergency communication]]s operation, will often bear an additional identifier meaningful within the individual net. While these do not fully replace the station's globally-unique government-issued callsigns, they are employed to address traffic within an net based on the rôle a station at a specific location plays in the larger operation. Each deployed [[ARES]] net at an event will typically contain one ''control'', various fixed stations designated by place name and/or individual mobile units labelled by purpose (''admin 1'', ''repair 2''...) depending on the incident and the needed response.

{{operation}}