HomeContactsProductsSupportDownloadsRepeaterLinux SetupEI-2010NewsShoppingLinkWorld GlobeDisclaimer

What do I need to get a SVXLINK / Echolink Node setup

The SvxLink Server

I'll try to summarize what is needed to setup a Simplex node using the SVXLINK software. However, because of the large variety of hardware and software, it is almost impossible to cover each and every aspect. Also, please have a look at this PDF that describes a possible scenario on a Simplex Linking Frequency.

  • A reasonably fast Internet connection that should be permanent (DSL or ADSL provides enough Bandwidth for about 4-5 simultaneous connections) .Dialup can be used, however may be sluggish at times and should only provide one connection at a time. A static IP number would be desirable however is not really required. Make sure that the router is setup with PORT 5198, 5199 and 5200 open. Dynamic IP numbers (on your local area network) may change once the lease is expired or the computer is restarted and you may experience sudden port closures. Most router allow  you to reserve an IP Number within your local area network (mostly starting 192.168.1.xxx but can be different). If you chose a static IP Number on the private side, it will be assigned permanently to the SVXLINK / Echolink host computer by using the MAC Address of this computers Network Interface Card (NIC).
  • A word about the host computer. Since the Computer is mostly running 24/7 it is advisable to use a low power consumer. Those computer are usually called Single Board Computer (SBC) and cost between $60-$200 with all the devices needed on a single PCBA not included in this price is the enclosure, monitor, keyboard, hard-disk, power supply and mouse. The initial cost will well compensate for the electricity saved over time. There are many more ways to save energy but this is probably the highest power consumer in the entire link setup.
  • A Linux operating system installed onto the SBC or Host Computer of your choice. I personally prefer a UBUNTU installation. The SVXLINK software was developed on a RED HAT - Fedora Project as I believe Version 8 or earlier. In the meantime many bug fixes and other improvements have been implemented. Although, it was developed for the Fedora operating system, it will work with many other Debian based LINUX operating systems. Help on how to install the operating system is provided with the individual distribution package or visit the official SVXLINK site.
  • Some Interface between the computers sound board and the transceiver. Should be dedicated for 24/7 Internet VoIP setup. In general a Radio Transceiver can be connected directly to the computer but great care has to be taken when doing so. There are Voltage levels from the RS232 interface that might exceed the capability of the transceiver and destroy it or at least part of it. Also, there will be no or not much timeout timer control and if the transceiver was designed for mobile operation might overheat in some cases. It is advisable to use an interface that was designed to do the task of interfacing the TRX with the computer. Aleks (S54S) has designed an Interface that works with the SVXLINK software and has made the documentation available on his Website. There is however no ready to use PCBA and exists merely as documentation for the technically active HAM. I admit, I was lazy and have not been able to finish my design, a ready to use interface. One of the reasons is the lack of time. Another reason is that I would like to release a device that can automatically detect the Software in use. In other words is able to run on either Echo-Link system. My EI-160 design is in theory finished and most of the Firmware has been written, however a Proto Type will first have to be tested for some time before release. Once released the EI-160 will provide Automatic Audio Level Control, Audio processing circuitry, Timeout Timer and more.
  • After all of the above components have been connected you are almost ready to go. Before you can become active on the Echo-Link net, you will have to register with Echolink.org to get your node ID number. This will require a copy of your HAM radio license. This registration process was designed to minimize the possibility of boot legging your call sign. If you can't provide proof of your license there will be no node ID.
  • WB0RXX/Tim has designed and constructed an interface that also has a COR and timeout circuit built in. (Sorry, the Link does not exist anymore) to find out more. There are more web sites that offer Echo-Link interfaces and can be found here. Keep in mind that most of those were designed to work with Echo-Link (Windows® Application) and may not provide the RTS / DCD lines needed with SVXLINK.
  • The Ubuntu Linux Operating system Installs with X- Windows enabled at startup. This means that Memory resources are used to draw a fancy Windows Lookalike onto the screen. Logically, this does not make really a lot of sense for this type of application, since the Monitor is switched off mostly (if you don't your electric bill goes up) Aside from this there is really nothing to see. Ubuntu does provide a switching mechanism that lets you disable X-Windows and puts you onto a full screen Console (Command Screen) by using the CTRL+ALT+Fn key on your keyboard. For example pressing CTRL+ALT+FÉ  will place you onto TTY console and disables most of the X-Windows temporarily. This way you can free up additional computer resources if they are bare minimum. Usually there are 6 consoles total that can be accessed in the same manner as described above. CTRL+ALT+F3 will place you onto the TTY3 console. To re-enable X-Windows you'll have to press CTRL+ALT+F7  and the X-Windows will be reloaded.