NOTE- The TC ARES PACKET EMERGENCY RALLY FREQUENCY for PACKET is 145.050
CHECK- wb6fzh-1 PACKET MAILBOX, or watch for beacon with information.

TCARC/ARES Unproto Packet Activity

DRAFT----------DRAFT----------DRAFT

Procedures for UNPROTO Net Operations
I- Net Schedule

THIS IS A DRAFT PROPOSAL...NOT AN ACTUAL NETWORK YET!
Proposed Date: 1st and 3rd Wednesday (Following TCARC 2 Meter Voice Net)
Proposed Time: 2000 to 2030 Hours Local Time
Frequency (2 meter Primary and Secondary to be selected)
INTERIM NET FREQUENCY- 144.910 primary, XXX.XXX secondary
Note: This is not actual proposed time,etc.just for draft purposes, however, the frequency of 144.910 is the default for TCARC ARES EMERGENCY NET.

II- Net Guidelines

Reminder: This is a DIRECTED NET.
General format: Unproto net, roundtable via NCS
All stations will set Unproto to "via (NCS CALL)" ; or the appropriate path for digipeating so as to hit the designated digipeater or station.
At 2000 Local Time NCS will request all participating stations turn off beacons.
At 2005 Local Time NCS will begin packet net by transmitting the preamble.
Check-ins will then be taken by geographic area .
Stations checking-ins should include location and status for comments or announcements.

III- Sample Transmissions

Sample PreAmble: "Calling the Sunday Night packet net"
Sample for Check-In Call: "Now taking check-ins for (geographic area)…ga"
Sample Check-In: "W6ABC, Hayfork, announcement…ga"
Invitation to join ARES packet net, or assistance help with packet set-up.
Other Status/Announcements ( Check-in Modifiers Of Interest)- Besides Location or if you have an announcement,etc

Battery Power
ARES Portable Station Test
APRS able
New Antenna
New Location
Demonstration in Progress
New TNC
New Computer
New Radio (power level increase/decrease)

IV- General Net Protocol Notes

The NCS will keep a NET LOG

Callsigns
Save TXT file dump from TNC (name TCP0823.TXT, August 23 net)
The NCS is the ONLY "packet traffic cop" during the net. The Assistant NCS if on frequency may take over if the NCS does not respond to transmissions during the net, or does not start the net by 2010 HRS
If the NCS or the Assistant NCS is not present, any station may take over the net, and e-mail a network activity report to the NCS, or leave a message in the NCS's packet mail box or both.
Each transmission requiring a response should be followed by "…ga" where "ga" stands for "go ahead.".
Due to time delays of packet transmissions and reception, NCS will acknowledge check-ins for individual geographic areas after packet transmissions for that area have ceased.
NCS will then move on to the next geographic area.

V- Sample Acknowledgement

Sample Acknowledgement: "Acknowledging W5HOR/K6ABC/N6TKY/WD6FHX/WB6FZH…."

VI- Net Agenda

Once all geographic areas have checked-in, NCS will make announcements then proceed down the check-in list by area to take comments and announcements.

After all traffic, comments and announcements have been handled, NCS will allow stations to go direct to other stations or to make other general comments. To avoid confusion, NCS will acknowledge requests to go direct one station at a time.

VII- Sample NCS Transmission

Sample Direct Request: "KM6ZW request direct to AC6WW…ga"
Sample NCS Response to Direct: "KM6ZW go direct…ga"

VIII- Net Notes

Stations should keep directs SHORT and CONCISE to allow other stations to participate.

After all business is handled, NCS will close the net.

IX- Closing Procedure

The net will close at 2030 Local Time, or as the NCS decides. Note: Member Stations will notify the NCS if they have to close station early. (procedure being developed)
Sample Closing: "WB6FZH now closing the TCARC/ARES packet net, 73s and Thanks!

NOTE: This Packet Net Protocol was stolen from various pages on the internet, and will be updated and modified to reflect our needs continiously.
First Draft: August 20, 2001
Last Updated: November 27, 2003
Your constructive suggestions are always welcome- E- Mail Webmaster or Greg, WB6FZH
PACKET LINKS