Repeater echolink
From MMAE
This is a checklist and idea resource for setting up echolink on the ARCatUCF 146.64 repeater.
Contents |
[edit] Work left
See also Repeater modifications
-
program repeater to add macros to bring link up and down - program echolink to activate repeater, and add remote controls
-
finish wiring and test... -
set up wired control operator remote controls for legal satisfaction - (optional) set up controls to call internet users from RF
- (optional) set up weather alert features via internet and other voice stuff
[edit] Set up methods
[edit] Direct method
Wire a server node directly into the repeater.
[edit] Set up tasks
-
Aquire a computer to use for the server. -
Study repeater schematics and set up correct wiring. Resolve issues with audio level, PTT control. -
Install echolink on computer. -
Open hole in firewall for echolink on that server. - Set up control macros and schedules on repeater.
- Set up control macros, schedules, permissions, etc., in echolink software.
[edit] Advantages
- Sound quality may be greatly improved over link method.
- Repeater will be MUCH more controllable, especially with respect to
- courtesy tones,
- voice messages
- squelch tail
- noise and other repeater signals inappropriate for echolink
- dual source mixing instead of double between echolink/RF
- This is the expected method for IRLP use if we decide to do that.
[edit] Disadvantages
- If repeater moves to an inaccessable location
- servicing the computer will be difficult
- computer must have network connection in remote location (but we need a remote access method to the repeater anyway)
- More hardware will have to be added to the repeater rack and wiring changed on the repeater.
[edit] Link method
Connect echolink to the repeater via a remote link radio and computer. Remote link computer/radio act almost the same as any other normal repeater user.
[edit] Set up tasks
- Aquire
computerAND link radio - Set up link computer on echolink
- Resolve repeater / link radio issues including squelch level, tone squelch,
PTT control. - Set up repeater control macros for "echolink mode" to
- turn off extra voice ID messages
- shorten or eliminate squelch tail hang
- reduce or eliminate courtesy tones
- Program echolink software macros to activate repeater/normal mode on connect/disconnect
- Program repeater macros to correctly pass DTMF to echolink and other control signals
- Set up schedules on repeater and echolink software
[edit] Advantages
- No physicial modification of the repeater is needed.
- Computer portion of link remains accessable even if the repeater is moved.
- This method is already half done.
[edit] Disadvantages
- Link method precludes full IRLP use. (Conferences ban remote linked repeaters due to extra non-voice noise introduced by the repeater.)
- Repeater noise is more difficult to control, and some repeater safety measures (such as squelch tail) will have to be disabled.
- Doubles between echolink and RF produce unusable results.
- Noise and users who key up too fast may completely prevent an echolink operator from participating in a conversation.
- Set up might be trickier.
- An extra link radio must be bought (or borrowed) that would not be needed with the direct method.
[edit] Tasks common to both methods
- Obtain echolink -R or -L designation on any call sign.
- Fine tune repeater behavior to optimize echolink response and reduce repeater noise.
- Set up macros and schedules
[edit] Decisions to make
- Should RF access to echolink be open and codes advertised?
-
Should the echolink station use the club callsign or a member's callsign on the echolink side? - Should the echolink access to RF be open or restricted to specific users?
- by country?
- by user type? (PC vs. repeater)
- to specific known (remote) users?
- Can echolink be on always or only on a schedule when members will be listening? (Or perhaps more restrictive rather than completely disabled.)
- If echolink control channel qualifies as primary control, always open is OK, if desired.
- If echolink control channel is not the primary control, a member on a primary control channel must be present.
[edit] Legal issues
[edit] rules
- Voice over IP mechanisms do not qualfiy under FCC rules for automatic control, as does a repeater.
- Since the VoIP is not a repeater, it falls under the rules for a remote controlled station.
- A remote controlled station must have its primary control as either a hard wired line, or a frequency above 220 mhz.
[edit] options
Under these conditions, the following are legal options:
- Echolink via 2m on repeater input
- If the echolink station links to the repeater via 2m frequencies, incoming calls do not qualify as remote control. Therefore, a control operator must be present (monitoring) at all times that echolink is active, and able to control the repeater via alternate means.
- Likewise, outgoing calls do not qualify as remote control, so a control operator must be present to monitor on a primary control channel.
- Echolink via 70cm repeater input
- If the echolink station links to the repeater via 70cm, incoming and outgoing calls qualify as remote control.
- Echolink hardwired directly to the repeater
- Incoming calls qualify as remote control.
- Outgoing calls via 2m do not qualify as remote control, so the repeater must be monitored by a control operator with access to a control channel, or outgoing echolink must be disabled.
[edit] legal control channels
- Under normal automatic repeater operations (i.e., not remote control), primary control may be via physical access, if physical access can be obtained within a reasonable time period.
- A link radio above 220mhz can provide primary control.
- A direct wired link (via standard phoneline, or secure internet link) can be primary control.
