Differences
This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
|
Next revision
Both sides next revision
|
repeater_linking [2019/12/14 15:20]
KD6KPC [Link to Repeater] |
repeater_linking [2019/12/14 15:24]
KD6KPC [Link to System] |
| - Limit to this state/province. Select "Yes" if the entire system is contained within one state or province. This helps to declutter the drop-down box by omitting linked systems belonging to other states and reducing confusion when two systems have the same name, but are not related to each other but are in different states or provinces. If the system crosses over state or provincial boundaries, select "No." | - Limit to this state/province. Select "Yes" if the entire system is contained within one state or province. This helps to declutter the drop-down box by omitting linked systems belonging to other states and reducing confusion when two systems have the same name, but are not related to each other but are in different states or provinces. If the system crosses over state or provincial boundaries, select "No." |
| |
| === Simplex === | ==== Link to Simplex ==== |
| | A repeater may be linked to a simplex frequency and not another repeater at all. That link can be added by entering the following: |
| | |
| | - Persistence: This is the nature of the link. Is it full-time, part-time, linkable, or On-Demand? Choose "full-time" if the repeater is always linked to the frequency. Select full-time if it is only linked part of the time, such as for nets. Select linkable if there is a pre-configured link that a repeater sysop can activate to the frequency. Select On-Demand if the linking can be completed by someone other than a sysop via a DTMF code, for example. |
| | - Frequency: Enter the frequency the repeater is linked to. |
| | |
| | This should not be used for repeaters with a frequency-agile remote base to list more than a frequency or two. |
| |
| |
