Sysop (Link) Nodes

Home
Up
FAQ - General
FAQ - Installation
FAQ - Callsign Validation
FAQ - Nodes
FAQ - Servers
FAQ - Connecting
FAQ - Operating
FAQ - Advanced Operating
FAQ - Audio
FAQ - iPhone
FAQ - Android
FAQ - EchoLink Web
Firewall Solutions
Authentication
Validation Documents
Access Policies

Although you can run EchoLink directly from a PC or mobile device, the true power of EchoLink lies in its ability to bridge between the worlds of Internet and RF. This is accomplished through the thousands of nodes on the system that run in Sysop mode; that is, which function as links between EchoLink and a local repeater or simplex frequency.

If you want to set up your own link, there are many ways to do it, with different combinations of hardware and software. This page describes some of the most common approaches.

Hotspot

A “hotspot” is a low-power simplex link which serves only a very small area, such as the inside of your own home. With this arrangement, you can use an HT to communicate with any station on the EchoLink system, as long as your HT is in range of your hotspot. This type of node will have a -L callsign suffix.

Simplex Link

A simplex link is just like a hotspot, but it serves a wider area and might be intended for use by other hams who are in range of it. It will typically have higher power and a better antenna than a hotspot, and will be tuned to a carefully selected, clear frequency. This type of node will have a -L callsign suffix.

Repeater Link

A repeater link serves an existing repeater, adding EchoLink capability to it. With a repeater link, anyone who is in range the repeater can benefit from being able to connect to any node on the EchoLink system and carry on a QSO just as if it were a local station. Other nodes on the EchoLink system can also discover and connect to the repeater via this link. This type of node will have a -R callsign suffix and will typically use the same callsign as that of the repeater it serves.

There are two ways to set up a repeater link. One is to build it exactly like a simplex link — a PC connected through an interface to an FM transceiver, but with the transceiver tuned to the frequency pair of a local repeater. This is often the most convenient approach, since this equipment can be located anywhere in range of the repeater, such as at your own QTH. The second way is to co-locate the equipment at the repeater site, as long as the site has Internet access. Although often more complicated to set up, this can be more reliable and more operationally sound, since it is less susceptible to interference and can provide a cleaner experience on-air.

Choosing Equipment and Software

The most common way to set up an EchoLink link node is to dedicate a Windows-based PC to the task, running the EchoLink software for Windows. Configure the software for Sysop mode, and use a callsign ending in -L or -R. Using a special hardware interface, connect this PC to a dedicated FM transceiver, and tune the transceiver either to a clear simplex frequency, or to the frequency pair of a local repeater (with the repeater trustee’s permission).

The hardware interface forms the bridge between the PC and the transceiver, connected to the PC’s USB port. The EchoLink web site lists some common solutions. Depending on the type of interface, you would either use the PC’s built-in sound card, or a sound “card” built into the interface itself; some FM transceivers even have their own sound device built in.

There are some alternative approaches:

EchoIRLP lets your node operate on both the EchoLink and IRLP systems. With this approach, you purchase and install an IRLP node, and then add the EchoIRLP software to give it the additional EchoLink capability. In recent years, the most common hardware choice for EchoIRLP has been an imbedded IRLP node running on a Raspberry Pi. The Pi is a small, low-power, inexpensive single-board computer that eliminates the need to run a conventional PC 24/7. The IRLP node has a dedicated hardware interface which provides the appropriate signals to connect an FM transceiver.

SvxLink runs on Linux-based systems and provides much of the same functionality as the EchoLink application. See svxlink.org.

Asterisk is a software-based PBX which runs on Linux-based systems; you can add a module called app_rpt and the EchoLink “channel driver” to build a system that interacts with the EchoLink network, as well as the AllStarLink network. One of the common deployment packages is called HamVoIP. This platform is also available as ready-to-run, hardware/software packages; one such example is ClearNode.

More Information

To learn more about setting up a new node on EchoLink, please see the New Node FAQ.

 

 

Copyright © 2002- EchoLink.org — EchoLink is a registered trademark of Synergenics, LLC