Chester Clinic

 

Microsoft word - ares-4.doc

Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 District
District
District
District
Four
District
Five
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 1- INTRODUCTION .5
2- CHANGE LOG .7
3- ARES/RACES PACKET SKILL SET.9
4- FAQ ABOUT THE SKILL SET .10
5- IDEAS TO IMPROVE YOUR PACKET SYSTEM.13
6- OREGON PACKET OPERATORS CERTIFICATE PROGRAM .14
Introduction: .15 Method: .15 The Skills:.15 Demonstrating the Skills .16 Earning the Certificate .18 Comments?.18 7- REGULAR PACKET TRAFFIC TO BE GENERATED BY EACH ECC.24
8- ECC TO ECC COMMUNICATIONS STANDARD .25
Basic Information: .25 Message Format: .25 Traffic Form:.26 Traffic Order: .27 Communication Systems: .27 9- REQUIREMENTS FOR ALL TRAINING/DRILL TRAFFIC .28
10- REQUIREMENTS FOR ALL DISASTER TRAFFIC .29
11- OUTGOING MESSAGE FORMAT .30
12- ACKNOWLEDGING RECEIPT OF PACKET MESSAGE FORMAT .31
13- I T U PHONETIC ALPHABET .32
14- ARES/RACES STATE AND COUNTY ECC PACKET HEIRARCHICAL ADDRESSES .34
Changes to Report to [email protected] 15- IDEAS FOR YOUR "READY KIT".42
Basic Kit .42 Radio Equipment.43 The Human Side .44 The Human Side (continued) .45 16- FREQUENCY CHART - VOICE.46
17- FREQUENCY CHART - PACKET .47
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 18- ASSIGNMENT CHART .48
19- ARES/RACES - MESSAGE FORM .50
ARES/RACES - Message Form (continued) .51 20- SIGN SECTION.52
21- STATE AMATEUR RADIO CONTACT INFORMATION.61
22- FEDERAL RADIO CONTACT INFORMATION.64
23- LOCAL AND DISTRICT INFORMATION .65
Local Communications Plan .67 District Communications Plan .69 Local HF, VHF, UHF Frequency Plan.71 District HF, VHF, UHF Frequency Plan .73 Local Net Schedule .75 District Net Schedule .77 Local Packet Frequency Plan .79 District Packet Frequency Plan.81 Local EC, AEC, LEM and OEM Contact Information.83 District DEC, EC, AEC, LEM and OEM Contact Information.85 Local Miscellaneous Information.87 District Miscellaneous Information .89 24- ABBREVIATION TRANSLATION .91
25- NOTES .92
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 1- Introduction
This manual is for ARES/RACES use only.
There is confidential information in this manual that should not be
compromised.
Welcome to the first edition of the ARES/RACES Oregon Packet Radio Operators Manual.
Because of the dynamic nature of our mission… this manual is also dynamic. The intent
of the manual is to have one resource for basic information that is needed for emergency
communications with a focus on packet radio.
The local and district information must be supplied by the user of the manual. Sections
have been provided for inserting those pages into this manual.
Most of the information in this manual is available on the ARES/RACES Oregon Packet
is based, in part, on one
produced by David Hunt, KB6JAW, in 1993 for Alameda County in the San Francisco bay
area. The efforts of many folks have made this manual possible. Tami, W7TMK, and Lew,
WB7NML, have supplied much of the information and they help to keep the details up to
date.
Check the web site for a more detailed list of folks that have contributed to this manual

The margins have been set to allow for hole to be punched for insertion in a binder. It is
designed to be printer back-to-back.
A copy of this document is available for down loading from the website. It will be
updated as necessary.
The web site is updated at least weekly with new items and updating the current
information.
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Check packet bulletins posted to ares@or and races@or for updates.
The Change Log will be updated with each change so that a record may be kept of the
updates.
Please send any changes or corrections to [email protected].
Thank you for your efforts to make ARES/RACES Oregon one of the best groups in the
nation.
Ken Wilhelmi – N7QQU
Packet - [email protected]
Internet - [email protected]
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 2- Change Log
Pages to Replace
Initial Version
Oregon Packet Operators Certificate Program - Plus Minor changes and Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Blank Page
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 3- ARES/RACES Packet Skill Set
The following is a list of skills that are necessary for an operator to have in order to process ARES/RACES packet traffic. 1. Start TNC and configure 2. Start computer 3. Start radio, select frequency and adjust 4. Start software and configure 5. Check connection to node 6. Check connection to BBS 7. Compose message using ARES/RACES Packet Standard 8. Determine correct address of receiving station 9. Verify that receiving station is staffed by ARES/RACES personnel 10. Post message to BBS 11. Post bulletin to BBS 12. Retrieve message from BBS 13. Retrieve bulletin from BBS 14. Retrieve file from BBS 15. Check forwarding status of messages and bulletins on BBS or TNC 16. Send and receive messages from TNC mailbox 17. Print messages, bulletins and files 18. Log sent and received messages 19. Reply to received messages 20. Find alternate nodes and BBS Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 4- FAQ About The Skill Set
Question- I have been looking at the List of Skills' dated 3/1/98. I was going to submit
my name but have some questions. On determining the correct address of receiving station, do
you mean for example, KC7KFI@KC7KFI.#SALEM.OR.USA.NOAM or something else?
Answer- That is correct. There is a list posted about twice a month listing
the addresses of various ARES/RACES groups around the state; ECCs, ECs, SYSOPs and
other addresses of interest. On the IQI BBS check the ARES/RACES files for down load. Type
"we" (what is in "e" category). Check out the files named ECOMADDR.###. The most current
will be the largest number. Check the date on the file also. ECOMADDR.007 dated
2/28/98 is the newest as of today. To down load the file type de ECOMADDR.007. The "de" is
for download from category e the file named ECOMADDR.007.
Question- Verify the receiving station is staffed. I have no idea how to find out.
Answer- There are many ways of checking. voice on VHF, UHF, HF, telephone. Even a
packet message may work. The point here is, if there is an expectation of a reply, make sure
that there is someone to receive the message. There have been some problems with this in the
past.
Question- Checking forwarding status - I suppose you mean using RH #### to get
route and times?
Answer- You can "Check forwarding status of messages and bulletins on BBS or TNC"
by looking at the "status" of the message or bulletin. The means of doing this varies from one
BBS to another and one TNC to another. After posting a message on a BBS it is good practice
to list messages sent by you.
On RLI software for example: l< N7QQU On RLI software the results would look like: Msg# Stat Size To From Where Date/Time Subject 23817 P 1443 N7ICS N7QQU N7ICS 0306/2205 Basic Packet Skill Set 23813 P 1443 N7YAF N7QQU 0306/2204 Basic Packet Skill Set 23812 PY 1443 K7SUQ N7QQU 0306/2204 Basic Packet Skill Set 22627 B 1443 RACES N7QQU OR 0228/1114 Basic Packet Skill Set 22626 BF 1443 ARES N7QQU OR 0228/1111 Basic Packet Skill Set On RLI software the some examples are: Message 22626 is a bulletin and has been forwarded; BF Message 22627 is a bulletin and has NOT been forwarded; B Message 23812 is a private message to a station that uses this as their home BBS. Notice no listing in the "Where" column. This message has been read; PY Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Message 23813 is a private message to a station that uses this as their home BBS. Notice no listing in the "Where" column. This message has NOT been read; P Message 23817 is a private message to a station that uses N7ICS as their home BBS. Notice the N7ICS listing in the "Where" column. This message has NOT been forwarded. It still resides on this BBS. Since it has not been forwarded it cannot have been read; P. It is good practice to check the status of messages to see if they have been forwarded or read (if local). That was the intent of "Check forwarding status of messages and bulletins on BBS or TNC" Check with the TNC manual and see how they mark messages that have been read or forwarded. Check with your local BBS SYSOP to see how their system lists the status of messages and bulletins. Another helpful command in RLI BBS software is "s". It will list the status of the BBS. Example: s 640 Messages, 0 Held, 20 Killed. Up since Fri Mar 06 07:35:16 1998 WP: 6298 Callsigns, 326 New, 13951 Accesses Idle Ports: F G H I J Task Win Type Port Fri Mar 06 07:35:22 1998 Fri Mar 06 07:35:22 1998 Fri Mar 06 07:35:22 1998 Sat Mar 07 10:36:24 1998 5 D Forward < Sat Mar 07 10:36:47 1998 6 C Forward > Sat Mar 07 10:39:40 1998 This example shows that there is forwarding to and from K7IQI BBS. At the NODE level another command that may come in handy is "r r". It will list the routes that the Node has used recently and the retry rate and the volume of traffic. Example: PARETA:W0RLI-1} Routes: > 4 W0RLI-3 228 146 3479 0 0% 0 0 10:37 0 > 1 KC7KCQ-10 224 97 2343 35 1% 0 0 10:09 0 4 K7IQI-1 228 124 0 0 * 0 0 10:32 4 KA7AGH-8 228 109 0 0 * 0 0 10:06 The ">" denotes that that path has been used recently. The 228 and 224 numbers are the quality of the path that the SYSOP has set. The larger the number represents higher quality. The next number lists the number of nodes on the node list. The next number is the number of bytes sent. The next number is the number of retries followed by a percentage of retries. This will help you check on the connectivity of the Nodes and the quality of the connections. As before, check with your local NODE OP to see how their system lists the routes and connectivity. The idea here is to see if the message has at least started on its path and not stuck on the local BBS. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Question- On finding alternate nodes and BBS's, I'm not sure I understand.
We send things through K7IQI (Cedar), but if Ken didn't have power, we can go directly to
KC7KFE (SRA) and he has emergency power so we can get to KC7KFI. I'm not sure what I
would do if Ken and Evan were down.
Answer- It is a good idea to come up with a plan for that. IQI does not have Emergency
power so going to KFE would be a great plan. The idea here is to make plans and test them for
the node or BBS that you usually use to be down. There is a list, posted about once a month
that shows the nodes and BBSs with emergency power. Check for it by typing "l> ares" and "l>
races".
Question- I have only been active on packet since last fall, but have been checking the
ARES and RACES bulletins almost daily since then. I can run my station fairly well but the setup
at the Washington County EC (WCCCA) is a different matter. I run my station frequently from
our van and it works well.
Answer- It is always a good idea to use the station at the ECC to get used to it. You
may need to use it during an emergency. The portable packet in the van is a great idea. That
will come in very handy.
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 5- Ideas to improve your packet system
Setup a frequency plan for:
2 meter 1200 baud1: 2: 3: 70 cm 9600 baud 1: 2: 3: Setup a voice Packet Operations frequency.
For assisting packet operators off regular net control frequency
Try 70 cm. band first
Station status reports sent every two hours to all packet stations in
County
Call sign, location, packet frequency, etc. Set beacon to every 10 minutes.
Set beacon text to read Call sign including SSIDs and location. Make a copy of the configuration file for your Packet software on a
floppy and on your hard drive. If it crashes you will be able to get things
going again much faster.
Make a copy of the configuration file for your TNC settings on a floppy
and on your hard drive. If it crashes you will be able to get things going
again much faster.
Set your software to capture the text on the screen and enter DISPLAY and all the perameters will go streaming by. Different TNCs do this slightly different. Check your documentation. Create a floppy disk with the files commonly used. Message formats,
node and BBS frequencies, configuration files, TNC and software
commands, etc.
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 6- Oregon Packet Operators Certificate Program
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Release Notes
This document describes a certificate award program for amateur radio operators who demonstrate proficiency in packet radio operation, as it pertains to emergency communications. The goal of this program is to encourage training, participation in packet radio operations and developing proficient operators. The certificate is awarded by the Oregon Section of the ARRL's Amateur Radio Emergency Service. The certificate can be earned by demonstrating the skills necessary for successful packet radio operation in emergency communications. The set of Packet Radio Skills are defined on the ARES/RACES Oregon Packet Information web site ), and are shown below: The Skills:
The following list is the set of skills that must be demonstrated in order to earn the Packet Operator's certificate. 1. Start TNC and configure 2. Start computer 3. Start radio, select frequency and adjustments 4. Start software and configure 5. Check communication to Node. 6. Check communication to BBS 7. Compose message using ARES/RACES Packet Standard 8. Determine correct address of receiving station 9. Verify if receiving station is staffed by ARES/RACES personnel 10. Post message to BBS 11. Post bulletin to BBS 12. Retrieve message from BBS 13. Retrieve bulleting from BBS 14. Retrieve file from BBS 15. Check forwarding status of messages and bulletins on BBS or TNC 16. Send and receive messages from the TNC mailbox 17. Print messages, bulletins and files 18. Log sent and received messages 19. Reply to received messages 20. Find alternate nodes and BBS Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Demonstrating the Skills
Mastery of the Skills can be demonstrated in a number of ways. The method detailed in this section is one that has been approved by the certificate issuers (Oregon ARES). Other methods that are approved by the certificate issuers can be used to demonstrate the Skills and qualify for the certificate. This method is based on the "Packet Challenge" activity sponsored by the Marion County ARES group during the first half of 2001. The Packet Challenge was organized to cover many of the necessary packet skills. The following list of exercises (see Table 1) duplicates many of the Packet Challenge activities, with a few new ones created as necessary to cover all of the Skills. Where applicable, the equivalent Packet Challenge activity is noted, as "PC #?". Note that in some cases, a given activity can be performed in a way that will demonstrate either more or fewer skills than are listed in Table 1. A Note on Word Counts: Packet radio uses AX.25 which has a very good error correction scheme that makes the need for "word count" unnecessary. All packet traffic starts out in written form. Packet traffic may at times be converted into NTS phone traffic. At that time a word count should be added. The ability to accurately compute the Word Count remains an important aspect of formal traffic handling. Table 1 - Packet Activities
Activity
Skills Demonstrated
1. Create and maintain a log of all Packet Certificate 2. Send a packet radio message to the coordinator containing the bulletin number of the Packet #1, 2, 3, 4, 6, 10, 12, 13 Certificate announcement (PC #1) 3. Read message from and place a message into a TNC "personal" mailbox (PC #4) 4. Connect to a Node and retrieve information on it's 5. Report the full hierarchical address of an ARES EOC facility (PC #6) 6. Retrieve a file from a BBS directory (PC #8) and convert ARL radiogram to plain text. 7. Compose and send an Training/Drill Traffic 8. Compose and post a Bulletin to a BBS, verify when Skill 11, 15 it is forwarded. 9. Create hard-copy printed records 10. Connect to a Node or BBS by more than one route 11. Reply to a received message 12. Verify if a station is actively staffed Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Notes for each Activity
Activity 1: Maintaining a log of station activity is an important emergency skill. This provides a
written record of message traffic and station activity, which can be very helpful when giving way
to a relief operator.
For the Packet Certificate program, use the Log as your summary of your Skills demonstration. Note in your Log each activity for which Skills are being claimed. A sample Log file can be found in Addendum B. You must submit your Log to the Certificate coordinator as proof of skills. The Log may be kept either in paper or electronic form. Some Activities require only that information be entered in the Log, while other Activities require a message be sent to the Certificate coordinator as well. Activity 2: The Certificate coordinator shall post an announcement of the Packet Certificate program on all BBS systems in Oregon (sb ares@or and races@or). (The information will also ). The announcement should then appear on all local BBS systems, ideally including those designated in the local communication plan as a primary communication resource. This will encourage operators to be familiar with the same BBS that they would use during an activation. The announcement will appear with a BBS bulletin or message number, and will include the name and packet address of the current Certificate coordinator. If the Packet Certificate announcement is not available on your local BBS, contact the Certificate Coordinator or an ARES official in your area and ask that Announcement Bulletin be re-posted. This is often necessary due to the limited lifetime of bulletins in many BBS systems. For the Packet Certificate program, the operator should send a packet message containing the bulletin or message number of the announcement to the Certificate coordinator. The coordinator will return a confirmation message, which the operator should note in their Log. Activity 3: One method to demonstrate the skill of using a TNC mailbox is to connect via node hopping to the TNC of the Certificate coordinator, read a message, and leave a message there. This would also demonstrate Skill #5. Alternatively, one could exchange messages on the TNC of another operator in your local area. List in your Log any Nodes used to make a remote connection. Activity 4: If not already demonstrated in Activity 3, the operator could access a remote Node and retrieve information about its Port configuration. Record the information in your Log. Activity 5: Using Packet Radio means, determine the full hierarchical address of any ARES EOC facility, and record the address and method used in your Log. Activity 6: For this activity, find and retrieve a file from a BBS file directory that contains a message in ARL radiogram format. Convert the radiogram into plain text and add the correct word count. Enter the plain text message in your Log. The original message file will be distributed by the Certificate Coordinator. Activity 7: Using the information in Addendum A, send a "Training/Drill" traffic message to your local EOC facility. Receive a confirmation from the EOC that your message was received, and record the date and time in your Log. Note that this could be combined with Activity 6 to demonstrate Skills 7 and 8 in one step. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Activity 8: Post a Bulletin to the "PACKET" category with statewide distribution. Verify that it has been forwarded to other BBSes by connecting to a remote BBS. Enter a description of your bulletin and the approximate time required for the forwarding to take place in your Log. Activity 9: Practice creating hard copy of packet traffic, and make an entry in your Log. Take the opportunity to check for any spare resources needed (paper, ink cartridges, etc.) Activity 10: Enter in your log at least two routes you can use to access a remote BBS. Activity 11: Using the "sr" command, send a reply to a packet message you have received. There should be plenty of opportunity to demonstrate this skill during normal packet activity. Activity 12: It may be necessary to perform this activity during a training exercise. Finally, the operator should feel free to use any combination of their own activities to demonstrate the Skills. Please record in your Log whatever means you are using to demonstrate each Skill, and submit the Log for verification of earning the Packet Certificate. Earning the Certificate
One goal of the Certificate program is to keep the administrative burden to the minimum, so that the activity can be easily self-sustaining. During the startup period of the Packet Operators Certificate program, the Packet Challenge coordinator (Tom Mosher, AB7NV) will serve as the Certificate coordinator. After completing all of the Activities or equivalent, the applicant should send in their completed Log, and any other necessary proofs. The log can be sent as a packet message if desired. The coordinator will verify that the activities listed in the Log match up with the coordinator's records, and to verify any Skills demonstrated by alternate means. Once the Log has been verified, the operator's name will be forwarded to the ARES/RACES Packet coordinator, who will issue the certificate directly to the operator. Contact the author with your comments or questions via packet, or email at [email protected].
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Addendum A
ARES/RACES PACKET ECC TO ECC COMMUNICATIONS STANDARD =========================================================== ver 10/30/99 DISTRICT #[X]: ARES/RACES Packet Operational Detail The Amateur Radio callsign used at the [name of ECC] Emergency Coordination Center (ECC) is [call of ECC]. =========================================================== NOTE: Once a month all stations should send a message about local ARES/RACES activities; meetings, drills, nets, training, meeting minutes or anything that may be of interest to the ARES/RACES groups in the state. Post messages in the following way: sb ares@or sb races@or ============================================================ PACKET RADIO should be the primary means of communication with other ECCs where the traffic is written data. It may be critical to determine if the receiving ARES/RACES unit has been activated. There may not be any ARES/RACES personnel at the receiving station. Packet will provide automatic, written copy of all communications with an emphasis on data (example: names and addresses and for lists of supplies and equipment). Stations with traffic for other ECCs should place the traffic on the closest full service BBS system in their area for automatic forwarding. Because bulletin forwarding may be reduced during some phases of a drill, exercise or emergency, it is necessary to send all traffic as personal. All packet traffic received should be acknowledged. Your message or traffic should include routing information within the destination ECC in the form of a name and/or job function (this saves time and confusion in delivering your message or traffic). Also include date/time, who the message was originated by and a signature at the end of the message. Because bulletin forwarding may be reduced during some phases of a drill or emergency, it is necessary to send all traffic as personal. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 An example message follows: SP KC7KKK@KC7KKK.#ABCD.OR.USA.NOAM +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ MESSAGE: 14 TURKEYFOOT COUNTY EOC PRECEDENCE: E PLACE: Turkeyfoot County ECC DATE: April 15 TIME: 14:23 TO: Bill Jones Logistics Section Turkeyfoot county has suffered an earthquake. Disaster declaration in progress. Will transmit via packet radio when available with further information. Signed: Millie Bowhunt, Emergency Manager Turkeyfoot County +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The acknowledgment from the receiving ECC will appear on the BBS system on which you posted the message. Logon to your BBS and check for messages on a periodic basis (every 15 minutes). An acknowledgment of the receipt of the traffic should be returned quickly. An example follows: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ DATE: April 15 TIME: 14:23 TO: KB7XXX@K7ABC.#ZXYU.OR.USA.NOAM RE: MESSAGE 14 TURKEYFOOT COUNTY EOC YOUR MESSAGE NUMBER 14 RECEIVED 14:45 (LOCAL) APR 15 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ NOTE: The receiving station cannot predict when an official response to your traffic will be sent from the ECC or by which mode the response will come (telephone, public safety radio, amateur radio). Traffic sent to the State ECC should be addressed to the "Duty Officer". ALL OFFICIAL TRAFFIC to and from ECCs must be in the Official ARRL Traffic Format minus the word count and handling instructions. This includes traffic related to Amateur Radio Communications, but does not include the information required for maintenance of communications links and networks. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 When traffic flow is heavy, operators at ECCs should handle Emergency traffic first, then call for Priority traffic, and finally call for Routine traffic. Low priority traffic will wait for high priority traffic. COMMUNICATION SYSTEMS: The appropriate use of a particular communication system or frequency is a complex issue related to current propagation, conditions, frequency usage, type of message, length of message, operator skill and transmission distance. The choice of a communication system or frequency should be left to the ARES/RACES personnel whenever possible. ***** REQUIREMENTS FOR ALL *TRAINING/DRILL* TRAFFIC 1. Messages must be numbered 2. Precedence will be TRAINING Emergency (TE), TRAINING Priority (TP), or TRAINING Routine (TR). The ECC generally does not handle Health and Welfare traffic. 3. Handling instructions are not used. 4. Station of origin. 5. Check is not required. 6. Place of origin will generally be COUNTY ECC or other official agencies. 7. Date in Month, Day form. NO YEAR! Example: APR 14. 8. Time filed recorded in the 24 hour system using LOCAL TIME. For example: 3:06 PM is given as 1506. 9. Address of person in ECC to whom the message is directed or the job function of such an individual. 10. ALL messages must include the following line: *** THIS IS A TRAINING/DRILL MESSAGE ***. 11. The message must have a signature. 12. All packet traffic received should be acknowledged. 13. All messages will be in plain ASCII text. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 *** REQUIREMENTS FOR ALL *REAL-TIME DISASTER* TRAFFIC *** 1. Messages must be numbered. 2. Precedence will be Emergency (E), Priority (P), or Routine (R). 3. Handling instructions are not used. 4. Station of origin. 5. Check is not required. 6. Place of origin will generally be COUNTY ECC or other official agency. 7. Time filed recorded in the 24 hour system using LOCAL TIME. For example: 3:06 PM is given at 1506. 8. Date in Month, Day form. NO YEAR! Example: APR 14. 9. Address of person in ECC to whom the message is directed or the job function of such an individual. 10. Messages must have a signature. 11. All packet traffic received should be acknowledged. 12. All messages will be in plain ASCII text. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Addendum B
Sample Activity Log
Name:
Call:
Address:
City:
State:
ZIP:
Op: AB7NV
Activity
12 Oct 2001
1830Z 14, 18 BBS file and Hardcopy Printed "cookie.txt" recipe file from
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 7- Regular Packet Traffic To Be Generated By Each ECC
Set up monthly practice sessions within districts and counties
At a minimum - send monthly update of packet addresses of ECC, Sysop,
EC, AEC, etc.
Post to: ares@or and races@or
Use the ARES/RACES Packet ECC TO ECC Communications Standard
form
Address list updates – some addresses are not active
Send monthly update of packet addresses of ECC, Sysop, EC, AEC, etc.
Post to: ares@or and races@or
Use the ARES/RACES Packet ECC TO ECC Communications Standard
form
Document Nodes and BBSs with emergency power
Post to: ares@or and races@or
Use the ARES/RACES Packet ECC TO ECC Communications Standard
form
Document Packet Operators that can accomplish the Packet Skill
Set
Post to: ares@or and races@or
Use the ARES/RACES Packet ECC TO ECC Communications Standard
form
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 8- ECC TO ECC COMMUNICATIONS STANDARD
ver 10/30/99 DISTRICT #[X]: ARES/RACES Packet Operational Detail The Amateur Radio callsign used at the [name of ECC] Emergency Coordination Center (ECC) is [call of ECC]. NOTE: Once a month all stations should send a message about local ARES/RACES activities; meetings, drills, nets, training, meeting minutes or anything that may be of interest to the ARES/RACES groups in the state. Post messages in the following way: sb ares@or sb races@or Basic Information:
PACKET RADIO should be the primary means of communication with other ECCs where the traffic is written data. It may be critical to determine if the receiving ARES/RACES unit has been activated. There may not be any ARES/RACES personnel at the receiving station. Packet will provide automatic, written copy of all communications with an emphasis on data (example: names and addresses and for lists of supplies and equipment). Stations with traffic for other ECCs should place the traffic on the closest full service BBS system in their area for automatic forwarding. Because bulletin forwarding may be reduced during some phases of a drill, exercise or emergency, it is necessary to send all traffic as personal. All packet traffic received should be acknowledged. Message Format:
Your message or traffic should include routing information within the destination ECC in the form of a name and/or job function (this saves time and confusion in delivering your message or traffic). Also include date/time, who the message was originated by and a signature at the end of the message. Because bulletin forwarding may be reduced during some phases of a drill or emergency, it is necessary to send all traffic as personal. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 An example message follows: SP KC7KKK@KC7KKK.#ABCD.OR.USA.NOAM +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ MESSAGE: 14 TURKEYFOOT COUNTY EOC PRECEDENCE: E PLACE: Turkeyfoot County ECC DATE: April 15 TIME: 14:23 TO: Bill Jones Logistics Section Turkeyfoot County has suffered an earthquake. Disaster declaration is in progress. Will transmit via packet radio when available with further information. Signed: Millie Bowhunt, Emergency Manager Turkeyfoot County +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The acknowledgment from the receiving ECC will appear on the BBS system on which you posted the message. Logon to your BBS and check for messages on a periodic basis (every 15 minutes). An acknowledgment of the receipt of the traffic should be returned quickly. An example follows: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ DATE: April 15 TIME: 14:23 TO: KB7XXX@K7ABC.#ZXYU.OR.USA.NOAM RE: MESSAGE 14 TURKEYFOOT COUNTY EOC YOUR MESSAGE NUMBER 14 RECEIVED 14:45 (LOCAL) APR 15 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ NOTE: The receiving station cannot predict when an official response to your traffic will be sent from the ECC or by which mode the response will come (telephone, public safety radio, amateur radio). Traffic sent to the State ECC should be addressed to the "Duty Officer". Traffic Form:
ALL OFFICIAL TRAFFIC to and from ECCs must be in the Official ARRL Traffic Format minus the word count and handling instructions. This includes traffic related to Amateur Radio Communications, but does not include the information required for maintenance of communications links and networks. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Traffic Order:
When traffic flow is heavy, operators at ECCs should handle Emergency traffic first, then call for Priority traffic, and finally call for Routine traffic. Low priority traffic will wait for high priority traffic. Communication Systems:
The appropriate use of a particular communication system or frequency is a complex issue related to current propagation, conditions, frequency usage, type of message, length of message, operator skill and transmission distance. The choice of a communication system or frequency should be left to the ARES/RACES personnel whenever possible. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 9- REQUIREMENTS FOR ALL TRAINING/DRILL TRAFFIC
1. Messages must be numbered 2. Precedence will be TRAINING Emergency (TE), TRAINING Priority (TP), or TRAINING Routine (TR). The ECC generally does not handle Health and Welfare traffic. 3. Handling instructions are not used. 4. Station of origin. 5. Check is not required. 6. Place of origin will generally be COUNTY ECC or other official agencies. 7. Date in Month, Day form. NO YEAR! Example: APR 14. 8. Time filed recorded in the 24-hour system using LOCAL TIME. For example: 3:06 PM is 9. Address of person in ECC to whom the message is directed or the job function of such an 10. ALL messages must include the following line: *** THIS IS A TRAINING/DRILL MESSAGE ***. 11. The message must have a signature. 12. All packet traffic received should be acknowledged. 13. All messages will be in plain ASCII text. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 10- REQUIREMENTS FOR ALL DISASTER TRAFFIC
1. Messages must be numbered. 2. Precedence will be Emergency (E), Priority (P), or Routine (R). 3. Handling instructions are not used. 4. Station of origin. 5. Check is not required. 6. Place of origin will generally be COUNTY ECC or other official agency. 7. Time filed recorded in the 24-hour system using LOCAL TIME. For example: 3:06 PM is 8. Date in Month, Day form. NO YEAR! Example: APR 14. 9. Address of person in ECC to whom the message is directed or the job function of such an 10. Messages must have a signature. 11. All packet traffic received should be acknowledged. 12. All messages will be in plain ASCII text. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 11- Outgoing Message Format
MESSAGE: [Insert your message number and location] PRECEDENCE: [Training Emergency (TE)] [Training Priority (TP)] [Training Routine (TR)] [Emergency (E)] ORIGIN: [Your packet address.OR.USA.NOAM] PLACE: [Physical location] TO: [Person, Department] [IF THIS IS A TRAINING MESSAGE ADD THE FOLLOWING TO THE TOP OF THE ***** THIS IS A TRAINING MESSAGE - THERE IS NO EMERGENCY *****] [Insert message in any format] Signed: [Person, Title, Location] Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 12- Acknowledging Receipt of Packet Message Format
TO: [Origin packet address.OR.USA.NOAM] RE: [Insert message your number and location] YOUR MESSAGE NUMBER xxx RECEIVED xx:xx (LOCAL) MMMM DD Signed: [Call, Location] Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 13- I T U Phonetic Alphabet
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 14- ARES/RACES STATE AND COUNTY ECC PACKET
HEIRARCHICAL ADDRESSES
VERSION 3/16/2002 Hi All ARES/RACES Folks-
.
Please review this list and make corrections and additions.
********* Please include addresses for:
********* EC, SYSOP, ECC, ARC, hospitals
********* and other important packet addresses.
.
This information will be shared state wide in an effort to
improve communication between ARES/RACES groups on a regular
basis and during emergencies.
Please send responses to:
[email protected]
.
.
* ===========================================================
* NOTE:
* Once a month all listed stations should send a message
* about local ARES/RACES activities; meetings, drills, nets,
* training, meeting minutes or anything that may be of interest
* to the ARES/RACES groups in the state.
* Post messages in the following way:
* sb ares@or
* sb races@or
* ============================================================
.
OREGON ARES/RACES STATE AND COUNTY ECC PACKET HEIRARCHICAL ADDRESSES
.
VERSION 3/17/2002
.
* are changes from last posting
NOTE: Date represents last change
.
STATE WIDE
.
3/17/02
Oregon State Navy-Marine Corps MARS Director - Pete - NNN0JBG - WA7JBG
Oregon State Navy-Marine Corps MARS Assistant Director - Pat - NNN0PAT - KG7HT -
[email protected]
8/16/01 W6HNC - John , (AAR0MI/AAA0OR) Oregon State Army MARS Director Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 .
DISTRICT ONE
.
3/16/02
DEC - Craig - KC7YOC - [email protected]
3/16/02
Assistant DEC, Pat - KG7HT - National Weather Service
.
6/20/01
Net Manager - Bonnie - AB7ZQ - [email protected]
.
Clackamas.
ECC - [email protected]
EC - Dave - [email protected]
SYSOP - Mike - KB7VNS@W7SRA.#SALEM.OR.USA.NOAM
Ass. SYSOP - Allen - N7YAF
.
Clatsop.
9/15/01
EOC - Clatsop County Emergency Services - [email protected]
EC - Scott - [email protected]
SYSOP - Mike - [email protected]
ARES NET: Every Monday at 1900 local on 146.660 MHz repeater (tone 118.8 Hz)
.
Columbia.
6/20/01
EC - Martin - [email protected]
AEC - Norman - [email protected]
AEC - Robert - KC7PD@WA7SJN.#WWA.WA.USA.NOAM
EOC - [email protected] (sysop - Martin KC7ILK)
Vernonia FIre - [email protected] (sysop Norman -
KB7CD)
ARES Net - Every Tuesday at 19:00 hours on 146.880 mhz (minus
60 khz, pl tone 114.8 hz [off for net operations]) Alternate simplex
frequency of 147.470 mhz.
.
Tillamook.
ECC - N7UQW-6 Connect / N7UQW-7 Mailbox
EC - John - N7UQW@W7SRA.#SALEM.OR.USA.NOAM
.
Washington.
7/18/01
EC - Ben - [email protected]
Packet Contact - Ernie - [email protected]
ECC - [email protected]
Banks Fire District - [email protected]
AEC for Banks Fire District - Ray - [email protected]
.
Multnomah.
3/17/2002
EC - Eric - KK7UE - [email protected]
AEC for East Multnomah County - Pat - KG7HT - [email protected]
Multnomah County ECC - [email protected]
PORTLAND ECC - [email protected]
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Net is every Wednesdays night at 7PM on the 146.84 with a - off set.
SKYWARN - NWS Portland - WX7PDX-1 mail box on 145.07 off PDX7
[email protected]
.
Yamhill.
ECC - [email protected]
EC - Jim - KB7VLC@W7SRA.#SALEM.OR.USA.NOAM
Net at 7:00 p.m. on Monday nights on the 146.64 repeater.
.
City of Tualatin.KB7MYV@WA7EES.#NWOR.OR.USA.NOAM
.
Portland Red Cross.
6-20-01
Oregon Trail ARC - [email protected]
Communications Coordinator - Keith - K7KEV
Disaster Svcs. Splst. - Scott - KC7ZUH
.
Clark County.
6/22/01
ECC - W7AIA@N7YSS.#WWA.WA.USA.NOAM
EC - Bob - K7YFJ
SYSOP - John - KB7FND@N7YSS.#WWA.WA.USA.NOAM
.
DISTRICT TWO
6/20/01
DEC - Dale - KI7PH
.
Hood River.
AEC - Terry - KB7DRX@N7QDN.#PDX.OR.USA.NOAM
.
Wasco.
EC - Jeff - KC5KVT@N7QDN.#PDX.OR.USA.NOAM
ECC - [email protected]
AEC - Packet - Lou - [email protected]
.
Sherman.
.
Gilliam.
.
Jefferson.
.
Wheeler.
.
Crook.
.
Deschutes.
10/02/01
State Police - ECC - KC7SNY@W7SRA.#SALEM.OR.USA.NOAM
EC - Matthew - KD7EQK
AEC - Bill Miller - KJ7GQ@W7SRA.#SALEM.OR.USA.NOAM
AEC-OSP - John - W7BND@W7SRA.#SALEM.OR.USA.NOAM
The Deschutes County ARES Meeting is the third Tuesday evening at Round Table Pizza . the
Central Oregon Radio Amateurs (CORA) Board meeting is the second Tuesday.
.
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 DISTRICT THREE
08/17/01
*DEC – Gary – N7ZHG@WA7V.#SEWA.WA.USA.NOAM
.
Morrow.
*08/17/01
*EC - Gary – N7ZHG@WA7V.#SEWA.WA.USA.NOAM
*ECC – KC7SOY@WA7V.#SEWA.WA.USA.NOAM
*Morrow County ARC D.A.T Captain – KD7LXU@WA7V.#SEWA.WA.USA.NOAM
.
Umatilla.
08/17/01
*EC - Gary – N7ZHG@WA7V.#SEWA.WA.USA.NOAM
*ECC – KC7RWC@WA7V.#SEWA.WA.USA.NOAM
*AEC - UMESRO Packet Sysop - Whitley – KD7VX@WA7V.#SEWA.WA.USA.NOAM
*AEC - Al – KC7DNT@WA7V.#SEWA.WA.USA.NOAM
*Pendleton Chapter American Red Cross – KC7URD@WA7V.#SEWA.WA.USA.NOAM
*Pendleton National Weather Service Office – KC7ZNF@WA7V.#SEWA.WA.USA.NOAM
.
Benton and Franklin Counties in Wsashington
6/20/01
EC - Dick - N7WLD
.
REPEATERS:
*146.780 minus offset, pl=67.0Hz – Located in Morrow County on Black Mountain at 6000 ft.
Lat = 45 12 48N Long = -119 17 38W
*145.480 minus offset, pl=67.0 = Located in Benton County in Washington State just north of
McNary Dam
Lat = 45 56 54N Long = -119 18 56W
These two repeaters are linked together.
.
Wallowa.
.
Union.
.
Baker.
.
Grant.
.
Malheur.
.
Harney.
.
Lake.
.
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 DISTRICT FOUR
.
DEC - Al - WB7RAB
.
1/1/2002
State OEM
ECC - KC7KFI@KC7KFI.#SALEM.OR.USA.NOAM
SYSOP - Shane - W0SPK@W7SRA.#SALEM.OR.USA.NOAM
ASYSOP - Andy - W7ATR
RACES - Tami - W7TMK@KC7KFI.#SALEM.OR.USA.NOAM
APRS DIGI: N7IFJ-10
.
Marion.
7/17/01
ECC - No Packet
EC - Eric - KD7CSY
APRS Stations - KD6FIB, KK7HI, KD7LA, AB7NV
AEC - Digital - Christopher - KD6FIB@W7SRA.#SALEM.OR.USA.NOAM
APRS ECC- K7MAR
.
Polk.
7/17/01
ECC - Polk County S.O. - W7PLK@W7PLK.#DALLAS.OR.USA.NOAM
EC - N7BUD - Bud
SYSOP -AEC - Zale - KC7FYD@KC7FYD.#DALLAS.OR.USA.NOAM
.
Lincoln.
7/11/01
EC - AB7QN - Hugh
AEC KK7EM - James
Lincoln Co. Upses APRS for packet communications
.
Benton.
ECC - K7CVO@W7SRA.#SALEM.OR.USA.NOAM
EC - Steve - KB7WND@W7SRA.#SALEM.OR.USA.NOAM
.
Linn.
EC - Paul - WB9HZT
Linn County ARES meets 3rd Thursday of each month at the Linn County Sherrif's office near
the Linn County Jail at 7:00pm.
Net every Monday evening at 7pm on 147.200
.
Lane.
6/20/01
Local BBS is off the air.
SYSOP - Bob - W7BH
EC - Carl - W7EXH
AEC - Ralph - W7WTQ
ECC - Lane Co. S.O. - W7EUG
ECC - Lane Co. S.O. - W7EUG-2 off W7EUG-1 (CBRG) 145.06 - Keyboard
Sacret Heart Hospital - N7FGF-8 off W7EUG-1 (CBRG) 145.06
.
Western Lane.
2/1/02
ECC - W7FLO @ W7FLO.#FLO.OR.USA.NOAM
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 AEC FIELD OPERATIONS - Rob
AEC TRAINING OPERATIONS - BRUCE, K7BHB
AEC ECC OPERATIONS + SYSOP - Hal - N7HL@W7FLO.#FLO.OR.USA.NOAM
Peace Harbor Hospital - PHMC Maildrop
West Lane ARES / RACES meets on the fourth Saturday of each
month at the Siuslaw Valley Fire and Rescue, 26th & Hwy 101.
.
DISTRICT FIVE
.
12/11/01
DEC - Albert L. (Al) Pion, KK7XO
.
Coos.
EC - Liz - KA7MYM@W7FLO.#FLO.OR.USA.NOAM
Bay Area Hospital - KC7PQT@W7FLO.#FLO.OR.USA.NOAM
.
Douglas.
ECC - KC7NFY@KC7TLY#SWOR.OR.USA.NOAM
EC - TOM - KB7YLY@KC7TLY.#SWOR.OR.USA.NOAM
SYSOP - DICK - AA7GC@KC7TLY.#SWOR.OR.USA.NOAM
.
Klamath.
EC - Richard - K7DDI@WB7AWL.#SWOR.OR.USA.NOAM
ECC - W7VW-4 Maildrop / W7VW-1 connect
ARC - W7VW connect only
.
Curry.
.
Josephine.
6/20/01
EC - Brian Fritsen - KK7BF@N7ZWU.#SWOR.OR.USA.NOAM
AEC - Will Calvert - N7KS@N7ZWU.#SWOR.OR.USA.NOAM
AEC - Bill Leiken - N7IXX@N7ZWU.#SWOR.OR.USA.NOAM
SYSOP Sean Smithers - N7ZWU@N7ZWU.#SWOR.OR.USA.NOAM
.
Jackson.
ECC-NWS KC7PJX@WB7AWL.#swor.or.usa.noam
EC -Randy K7RPM@WB7AWL.#swor.or.usa.noam
AEC - Bill KC7REK@WB7AWL.#swor.or.usa.noam
AEC - Gary WA7MUY@WB7AWL.#swor.or.usa.noam
Jackson County ARES Net Tuesday@1930 on 145.49(136.5)/147.16
OR-CA ARES Net Wednesday@1930 on 145.49(136.5)/147.16 (8 counties)
SYSOP - Cal - KA0DFN@WB7AWL.#SWOR.OR.USA.NOAM
.
Thanks for the help. * This list will be posted to ares@or, races@or. Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Changes to Report to [email protected]
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 15- Ideas for Your "Ready Kit"
This is not a complete list. Just a list to build from
Basic Kit
Canteen with water (2 quarts) Snacks: four Power Bars Fanny pack with earphone, sun screen, chap stick, small pocket knife, pen, small pad First-aid kit (Motrin, Imodium, Dramamine, Tylenol, Benadryl, insect repellent, Toilet paper, Kleenex, cups Pocket knife (multifunction) Flashlights (Maglites, large and small) Camera with film Pens, pencils, markers, note pad, small calculator, miniature office set Net preamble and check-in sheet ECC message forms (50 min.) ECC activity log Clipboard night light Clipboard note pad Emergency / ARES/RACES placards Repeater directory (local and national) Maps (AAA area or Thomas Guides) and compass (in car) Ski hat and gloves, leather gloves with liners, rain poncho, collapsible umbrella, ball Waterproof matches, butane lighters Parachute cord (two 50-foot lengths) Power extension cord (50 foot, 110 VAC) 110-Vac outlet strip Portable reflector lamp (110 VAC) Roll of black electrical tape Garbage bags (two 55 gallon, four large ziplock) AM/FM radio and batteries Four Cyalume light sticks (12-hour, green) Strobe-marker light Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Ideas for Your "Ready Kit"
This is not a complete list. Just a list to build from
(continued)
Radio Equipment
All the Radios and accessories you can find Coax: (25 ft RG-58/U, 100 ft RG-8X, 10 ft RG-58/U, 6 ft RG-58/U) Connectors and adapters: PL-259 TO BNC, N, SO-239, barrel connectors, etc. HT accessories, speaker mic, earphone, earphone with tie-clip mic, dc power plug, dc Magnetic-mount antenna for HT Extended gain antenna for HT Electrical tape and duct tape Small tools; larger tool case in car Spare D cell and AA batteries (MANY FRESH ONES) Fire extinguisher Gel cells battery packs J-pole or quad antennas Butane torch and butane, wire cutters, and spare connectors for repairs 12 Volt battery charger Good head phones (It gets very noisy with all the radio traffic and the QRM) Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Ideas for Your "Ready Kit"
This is not a complete list. Just a list to build from
(continued)
The Human Side
Cooking stove (dual fuel), unleaded gas and camping fuel Quart fuel bottle (camping fuel) Cooking kit: small pot, dish, eating utensils, 2-qt plastic measuring cup Water: 3 gallons (depending on duration of event) Plan on at least 1 gallon per day. Lantern (dual fuel) Extra matches, lighters, fire-starter stick Plastic trash bags Grooming kit: shaver, soap, etc. Extra clothing, socks, warm clothing, parkas 50-ft rope (5/16-inch diameter) Food: three-day supply; MRE, freeze-dried, etc. Hiking boots, work boots Small folding shovel Two-Person tent Sleeping bag with foam pad Personal medication (seven-day supply) Small folding chair Antacid (Mylanta) Antiseptic wipes Bandaids: 12 various sizes Dressings: eight 2-inch × 2-inch Dressings: eight 4-inch × 4-inch Gauze rolls (Kerlix) Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000
Ideas for Your "Ready Kit"
This is not a complete list. Just a list to build from
(continued)
The Human Side (continued)
Hydrogen peroxide Instant cold pack Magnifying glass Motrin or aspirin Polysporin ointment Pressure dressings Splinter-removal kit Triangular bandage Small Fanny Pack Extra eye glasses Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 16- Frequency Chart - Voice
Call
Note
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 17- Frequency Chart - Packet
Call
Note
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 18- Assignment Chart
Call
Note
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Assignment Chart(continued) Call
Note
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 19- ARES/RACES - Message Form
MESSAGE:[ message number and location] PRECEDENCE: [Circle ONE]
[TRAINING Emergency (TE)] [TRAINING Priority (TP)] [TRAINING Routine (TR)]
[Emergency (E)] [Priority (P)] [Routine (R)]
ORIGIN:[Your packet address.OR.USA.NOAM] PLACE:[Physical location] DATE: [Now]
TIME: [Now]
TO: [Person, Title, Department]
***** This is a TRAINING/DRILL Message *****
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 ARES/RACES - Message Form (continued)
Additional message text – Staple to above message form Sender: PRINT [Person, Title, Location]
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 20- Sign Section
Add Arrows and Post as Necessary Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 21- STATE AMATEUR RADIO CONTACT INFORMATION
TACTICAL
PACKET ADDRESS
E-MAIL (WEB)
AND/OR AGENCY
CALL SIGN
FREQUENCIES
VHF (P) = 147.02 OERS 1-800-452-0311 VHF (Alt) = 146.86 #salem.or.usa.noam or 503-378-6377. Dist #1 = 147.32 Reception at 503-378- Dist #4 = 146.78 HF (P) = 3.993.5 ARES console phone: HF (Alt) = 7.228 503-378-2911 ext. 257 HF (Res) = 1.928 Mike Potter KB7VNS /
Oregon ‘statewide' area coordinator for Navy-Marine Corps MARS. HF PACTOR (3.624 State Duty Officer 1- netnow.micron.net/ dscweb/index.html Northern California
ARES HF Net
Frequencies:
Daytime: 7232 LSB
(up) Nighttime: 3.987
LSB (down) /
Alternate: 1.982
LSB
(down)
CW: 7045 (up) 3545
(up)
ARES SIMPLEX:
146.55
ARES / Red Cross 2
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 meter SIMPLEX
147.42
NATIONAL CALLING
AND WILDERNESS
PROTOCOL 146.52
ARES REGIONAL
AND STATE NETS:
OR-NorCal-NV "5-1-
2" ARES Leadership
Net
W @ 1930L 3.987
Sonoma and
Mendocino Coast OA
Tu @1930L 3.915
Butte County
Th @ 2000L 146.85-
(110.9)
Lassen County
(146.565)
Th @ 1830L 3.987
QSY to: 146.88-
(after HF net)
Modoc County
(147.48)
Tu @ 1900L 146.97-
Mono County
(147.42)
Th @ 2000L 146.88-
(151.4)
Shasta County
(146.595)
M @ 1945L 3.987
2M Net - via
repeaters.
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 1st M @ 2000L
145.45 -
2nd M @ 2000L
146.64 - (88.5)
3rd M @ 2000L
146.76 - (107.2)
4th M @ 2000L
145.15 - (107.2)
5th M @ 2000L
146.925 - (85.4)
(When there are 5
Mondays in a month)
Siskiyou County
ARES (146.55)
Th @ 1930L 3987 and
146.55
Tehama County
ARES (146.55)
M @ 2030L 145.45-
Last updated: 3/15/2002 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 22- FEDERAL RADIO CONTACT INFORMATION
TACTICAL
E-MAIL (WEB) ADDRESS
CALL SIGN
FREQUENCIES
"Net Control" Assistance Center Last updated: 3/3/2002 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 23- Local and District Information
Insert the following local and district information Insert Local Communication Plan
Insert District Communication Plan
Insert Local HF, VHF, UHF Frequency Plan
Insert District HF, VHF, UHF Frequency Plan
Insert Local Net Schedule
Insert District Net Schedule
Insert Local Packet Frequency Plan
Insert District Packet Frequency Plan
Insert Local EC, AEC, LEM and OEM Contact Information
Insert District DEC, EC, AEC, LEM and OEM Contact Information
Insert Local Miscellaneous Information
Insert District Miscellaneous Information
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Local Communications Plan
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 District Communications Plan
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Local HF, VHF, UHF Frequency Plan
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 District HF, VHF, UHF Frequency Plan
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Local Net Schedule
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 District Net Schedule
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Local Packet Frequency Plan
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 District Packet Frequency Plan
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Local EC, AEC, LEM and OEM Contact Information
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 District DEC, EC, AEC, LEM and OEM Contact Information
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Local Miscellaneous Information
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 District Miscellaneous Information
Insert on following page(s)
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 24- Abbreviation Translation
American Red Cross Amateur Radio Emergency Service Amateur Radio Relay League Bulletin Board Service – Packet radio Civil Air Patrol ARES/RACES District Emergency Coordinator Emergency Alert System ARES/RACES Emergency Coordinator Emergency Communications Center – also know as EOC Emergency Locator Transmitter (usually on aircraft) Emergency Operations Center – also know as ECC Federal Communications Commission Federal Emergency Management Agency Hospital Emergency Administrative Radio Net High Frequency (less than 30 mhz) Incident Command System Local Emergency Manager National Traffic System National Weather Service Office of Emergency Management OR Oregon Emergency Management
Oregon Emergency System Oregon Emergency Response System Oregon State Police Private Bulletin Board Service (resides on local TNC) – Packet radio Radio Amateur Civil Emergency Service Radio Officer OR RACES Officer
Search and Rescue ARES/RACES Section Emergency Coordinator Sheriff's Office Terminal Node Controller – Packet Radio Ultra High Frequency (more 400mhz) Very High Frequency (30mhz to 400 mhz) Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000 25- Notes
Prepared by Ken Wilhelmi N7QQU Version 1 – 2/2000

Source: http://ares.ucem.us/d3web/ARES-4.pdf