Check-in and Check-out Procedures: Difference between revisions
From Portland NET Wiki
BruceSchafer (talk | contribs) Added more formatting |
BruceSchafer (talk | contribs) →Checking into a Regional Subnet: Clarified the relationship tactical call signs to team names. |
||
| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
=== | === Choosing Regional Subnets === | ||
Choose frequencies corresponding to two or more VHF simplex regions based on this map. Also make note of a backup UHF frequencies in case there is interference on the VHF frequencies. | Choose frequencies corresponding to two or more VHF simplex regions based on this map. Also make note of a backup UHF frequencies in case there is interference on the VHF frequencies. | ||
Propagation is more important than exact location so you may want to start by briefly listening on two frequencies and choosing the one that has the clearest signal. | Propagation is more important than exact location so you may want to start by briefly listening on two frequencies and choosing the one that has the clearest signal. There is a chance, however, that propagation won't be symmetric so that a subnet controller that you can hear clearly may not be able to hear you well and vice versa for the other subnet. In that case, you might have to try one and then the other. Don't give up if neither seems to be working well, however, because after the main check in, the controller will usually ask for one of the stations already checked in to ask for additional check ins from those who are having trouble hearing or reaching the controller. | ||
Things to worry about later: | Things to worry about later: The subnet controllers tend to vary from one exercise or deployment to another and sometimes their equipment will change. So, the best region to check into may vary from one exercise to another. It may also vary based on whether you’re checking in from home or from your team’s staging area. If you find two regions that work equally well, you could break the tie by choosing the one used by teams that adjoin your team geographically. | ||
=== Checking into a Regional Subnet === | === Checking into a Regional Subnet === | ||
| Line 9: | Line 9: | ||
During simplex exercises, your tactical call sign should be your NET team name followed by a number. If your net team name is long, choose an abbreviation. Example: “South Heights 1.” If you hear someone else check in with your chosen tactical call sign, change the number, e.g. “South Heights 2.” | During simplex exercises, your tactical call sign should be your NET team name followed by a number. If your net team name is long, choose an abbreviation. Example: “South Heights 1.” If you hear someone else check in with your chosen tactical call sign, change the number, e.g. “South Heights 2.” | ||
During citywide deployment exercises and actual deployments, your tactical call sign should be your team name or an abbreviation of it. You do not need to add a number as there should only be one ARO representing a team at a time. | During citywide deployment exercises and actual deployments, your tactical call sign* should be your team name or an abbreviation of it. You do not need to add a number as there should only be one ARO representing a team at a time. Your subnet controller will probably ask you for the full name* of the team or neighborhood where the team is deployed. Even if there are multiple teams participating at that location give only the name of the host team or neighborhood and then give your FCC call sign and say the word “Out” as it is the end of that communication. “Out” doesn’t mean you’re turning off your radio; it means you don’t expect a reply | ||
The subnet controller may have trouble hearing some operators. If you hear a station that the controller doesn’t acknowledge, wait for a pause, say the word “Relay” and wait to be told to go ahead. If the subnet controller has requested that relays be held until requested, follow the subnet controller’s instructions | The subnet controller may have trouble hearing some operators. If you hear a station that the controller doesn’t acknowledge, wait for a pause, say the word “Relay” and wait to be told to go ahead. If the subnet controller has requested that relays be held until requested, follow the subnet controller’s instructions | ||
<nowiki>*</nowiki> In some cases the team name will be short so your tactical call sign and the full team name will be the same. For longer names of teams or neighborhoods please choose a single word that represents the name of the team or neighborhood as your tactical call sign. | |||
=== What to do if you have trouble checking into a subnet === | === What to do if you have trouble checking into a subnet === | ||
| Line 25: | Line 26: | ||
=== Checking into the Resource Net === | === Checking into the Resource Net === | ||
During major exercises and actual deployments, we all start by checking into the Resource Net using the Hoodview Amateur Radio Club repeater at 147.280 MHz, 600KHz offset and 167.9 Hz tone. This repeater is also known as MC-2 as it is included as channel 2 in the [https://multnomahares.org/resources/frequency-lists-and-radio-programming-templates/ Multnomah County ARES (MCARES) frequency templates]. If the repeater does not appear to be working, you should switch to simplex using 147.280 MHz, which is channel 12 in the MCARES templates and known as MC-12. | |||
Subnet Controllers will sometimes be asked to check in first, so wait for the Resource Net operator to ask you to check in. The general check ins will probably be in alphabetical order by FCC call sign suffix. | |||
* Check in using your FCC call sign using the ITU spelling alphabet. | |||
* Listen for any announcements about which regional subnets are expected to be active and any changes to [[Frequency Tables|standard frequencies]]. | |||
* Once you have checked in and been released by the Resource Net Controller, you can transition to your regional subnet. | |||
Note: While you are waiting for your call sign suffix to be called, you may want to use the Reverse button on your radio occasionally to check to see if there are operators near you who are not reaching the repeater. If you hear someone trying to check in while you are on reverse but don’t hear them without reverse, they are not reaching the repeater. You have the option of offering a relay by using the proword “Relay”. ''Be sure and turn off the reverse feature before doing so.'' | Note: While you are waiting for your call sign suffix to be called, you may want to use the Reverse button on your radio occasionally to check to see if there are operators near you who are not reaching the repeater. If you hear someone trying to check in while you are on reverse but don’t hear them without reverse, they are not reaching the repeater. You have the option of offering a relay by using the proword “Relay”. ''Be sure and turn off the reverse feature before doing so.'' | ||
| Line 43: | Line 50: | ||
The protocol is to use MC-12 if the MC-2 repeater is down. Not only is MC-12 simplex but it uses the output frequency of the MC-2 repeater. This has a couple implications: | The protocol is to use MC-12 if the MC-2 repeater is down. Not only is MC-12 simplex but it uses the output frequency of the MC-2 repeater. This has a couple implications: | ||
# If the repeater is down and we don't remember that the alternate is MC-12 we can perhaps remember that it is the same frequency without an offset and turn off offset on our radios to access the Resource NET in simplex mode. | |||
# We can't practice on MC-12 because if we did so, we would be conducting simplex conversations on the output frequency of an active repeater and would conflict with anyone using the repeater (who may not be able to hear our simplex conversations). | |||
Details of MC-2 and MC-12 | |||
* MC-2 and MC-12 are references to Channels 2 and 12 in the [https://multnomahares.org/resources/frequency-lists-and-radio-programming-templates/ Multnomah County ARES frequency templates]. | |||
* MC-2 gives access to a repeater owned and operated by the [https://www.wb7qiw.org/ Hoodview Amateur Radio Club] | |||
** The repeater's output frequency is 147.280 MHz | |||
** The transmit offset is +600 KHz | |||
** The PL Tone is 167.9 Hz | |||
* MC-12 is a simplex channel to be used only when the MC-2 repeater is not operating | |||
** The frequency is 147.280 MHz. | |||
** Note that operating on MC-12 is operating the output frequency of the MC-12 repeater. | |||
=== Regions === | |||
Please choose a subnet according to your location. A map of regions can be found at www.tinyurl.com/pnet-simplex-map. If an exercise starts with a Resource Net the frequency for each region will be given by the Resource Net operator. If an exercise does not include a Resource Net, try the standard frequency for your region. If you don’t hear anything, try another region or check the backup UHF frequency for the region. Here are the names of the simplex regions: | |||
* Alameda North | |||
* Alameda South | |||
* Columbia | |||
* New Northeast | |||
* Outer East | |||
* River North | |||
* River South | |||
* Southeast | |||
* Westside | |||
=== Checking Into a Regional Subnet === | === Checking Into a Regional Subnet === | ||
Tune your radio to your regional frequency. Make sure that your radio is not using an offset because you will not be using a repeater. Once you’re satisfied you’re on the correct frequency, listen for the subnet controller. After some preliminary remarks, he or she will call for check-ins. Remember to check-in using your tactical call sign as described above. FCC call signs should only be used at the end of a communication. | Tune your radio to your regional frequency. Make sure that your radio is not using an offset because you will not be using a repeater. Once you’re satisfied you’re on the correct frequency, listen for the subnet controller. After some preliminary remarks, he or she will call for check-ins. Remember to check-in using your tactical call sign as described above. FCC call signs should only be used at the end of a communication. | ||
