Life of RPi, using svxlink as Echolink node in RPi


A new article introduces svxlink 14.08.1 as an Echolink node was uploaded. Please click: Here for detail.


This article is the English Edition of my Blog article, hope to share my experience to the ham all over the world.



What is Echolink

Simply to say, the Echolink via the Internet connection across the world to link up the ham radio station together. The technology used on Internet connection is VoIP, and the reset is the traditional method.



Topology of Echolink network (courtesy of K1RA Power point)


The mode of Echolink operation:

PC to PC

The ham use the Echolink software installed on the PC to communicate to each other.


Courtesy of K1RA Power point

Sys Op Mode

The Ham communicates between PC and transreceiver. There are 2 modes: simplex and Repeater.


Courtesy of K1RA Power point

Simplex Link

An Echolink user connected to a node via Internet connection, and a ham operator connect the same node though the air. The simplex node callsign format is Callsign-L .


Courtesy of K1RA Power point

Repeater Link

It similar to simplex link, and the node was connected to a repeater. The format of the repeater node is Callsign-R.


Courtesy of K1RA Power point

There are a few articles to describe how to use Raspberry Pi as an echolink server. A valuable article is from German magazine. But some of the information not details enough. Now I describe the procedure.

Hardware requirement:

  • Raspberry Pi which removed the USB port protection fuse, or later ver 1.0, or ver2.0 .
  • A USB Sound card, not all the USB sound card are compatible
  • USB to RS232 cord, the chip inside is PL2032
  • Sound Modem, the one used for APRS signal handling, but I modify some value to optimize the performance.
  • USB Hub, The RPi equipped 2 USB port only, so we need add a Hub
  • USB Keyboard, for command enter

Software Requirement:

The Audio setting of Raspberry Pi

When install the OS (16-dec-2012), It install the PulseAudio as the Audio driver. However, it is NOT compatible with the one we use which named alsamixer. Please remove the PulseAudio by the following command:

sudo apt-get purge pulseaudio gstreamer0.10-pulseaudio pulseaudio-utils


If you see the warning message, you should remove the PulseAudio

Please reboot after the removal, the warning message should disappear.


Echolink software used in RPi: Svxlink, a free open source program.


Introduction of svxlink

Svxlink is a ham ware used under Linux environment. It designed in modular bias.

It mainly used on repeater control and it also support multi transceiver. The module we used here is the Echolink.

The features of the Echolink module:

  • Echolink contact by voice & text mode
  • Support APRS map, the format of the Echolink station is EL-yourcallsign
  • Software decodes DTMF signals & PL tone, no need extra hardware
  • No more CW, use human voice to report station callsign, PL tone and time reporting every 15min.
  • Support Echolink enabled repeater


Let’s register the Echolink service

If you got an Android phone, I propose you download the Echolink app & process the validation first; we need it for the future testing. If you consider setup an Echolink node, please also registry callsign-L. Please be remind that the validation process was completed before your echolink node test.

Reminder on the Hardware used:

I got 2 USB Sound Card.



The blue is an old one which used few years ago for the APRS test. And the black one was bought recently.

Test result shows that the blue one is not compatible with RPi. The volume of the MIC of the alsamixer will always reset to 0 and mute after run svxlink.

But the black one is OK.

Sound Modem


Courtesy of VE3ELB Website

Although information from web mentioned the 600Ω : 600Ω Audio isolation Transformer suitable on vehicle /Desktop transceiver, Handheld should consider the speaker impedance matching issue. However, my test shown the result of using 600Ω or 32Ω : 1200Ω (ST-32) is similar.


In order to reduce components type, Both TX/ RX Audio use 600Ω : 600Ω.

Please be remind that the resistance of 600Ω audio transformer primary and secondary are different. For primary, the resistance should around 51 Ω. For secondary, the resistance should around 70 Ω.


Echolink connection Diagram


The installation of svxlink

Before the installation, please plug in all the related hardware to the RPi.

Step 1

Updated the OS & library to latest by the following commands:

sudo apt-get update && sudo apt-get upgrade

Please reboot afterward. If you are upgrade from an older version. The PulseAudio may be installed. Please remove it.

Step 2

Please install the prerequisite file, ensure no typo of the commands:

sudo apt-get install g++ make libsigc++-1.2-dev libgsm1-dev libpopt-dev tcl8.5-dev libgcrypt-dev libspeex-dev libasound2-dev alsa-utils libqt4-dev

Step 3

Download the svxlink, the latest version is 11.11.1, commands:

sudo wget

Step 4

Untar the svxlink file

tar xvzf svxlink-11.11.1.tar.gz

Then enter the folder, and compile the svxlink

cd svxlink-11.11.1

sudo make

If the installation of the prerequisite files is correct, this step should process at least 30min. if it complete around several minutes, it means the installation of the prerequisite files was incorrect. You should delete the svxlink folder, and re-install the prerequisite files again.

If compile files are OK, now we install by the following command:

sudo make install

The installation of svxlink was complete.


Installation of the sound clips files

As mention above, svxlink provides voice announcement for callsign, time, PL tone information. The sound clips files have 2 versions: 8k and 16k. We use 8k because RPi did not compatible to 16k.

Download the sound clips by the following command:


Untar the file to folder:

tar -jxvf sounds-en_US-heather-11.11.tar.bz2

Build up the destination folder:

sudo mkdir –p /usr/share/svxlink/sounds/en_US

Enter the folder, and copy all the contents to the destination folder:

cd en_US-heather-11.11

sudo cp –r * /usr/share/svxlink/sounds/en_US

The installation of sound clips files complete.


Edit configuration files

We need edit the following files:






Edit the file alsa-base.conf, command:

sudo nano /etc/modprobe.d/alsa-base.conf

options snd-usb-audio index=-2 Please change the value from -2 to 0

Press ctrl + x save & quit the editor.


Edit the file ModuleEchoLink.conf, commands:

sudo nano /etc/svxlink/svxlink.d/ModuleEchoLink.conf

#ALLOW_IP= Remove the #

CALLSIGN=yourcallsign-L Enter your callsign with –L prefix

PASSWORD=your_password Enter your password

SYSOPNAME=VR2XKP Your callsign for the echolink list

LOCATION= 144.640MHz, Hong Kong Brief describe your location


The following description used to describe your equipment:

DESCRIPTION=”You have connected to a SvxLink node,\n”

“a voice services system for Linux with EchoLink\n”


“Check out for more info\n”


“QTH: Hong Kong\n”

“QRG: Simplex link on 144.640 MHz\n”

“CTCSS: 110.9Hz \n”

“Trx: FT-51R\n”

“Antenna: Ducky\n”

Press ctrl + x save & quit the editor.


Edit the file svxlink.conf by the following command:

sudo nano /etc/svxlink/svxlink.conf

We need handle the section: [GLOBAL][SimplexLogic][Rx1][Tx1][LocationInfo]


LOCATION_INFO=LocationInfo   If your decide to display your echolink node in, your need change it to LocationInfo


MODULES=ModuleEchoLink The module used is “ModuleEchoLink”, you may remove the rest modules

CALLSIGN=VR2XKP      Please input your callsign


AUDIO_DEV=alsa:plughw:0 The AUDIO_DEV change to 0 for the USB sound card

SQL_DET=VOX     Set to VOX

SERIAL_PORT=/dev/ttyUSB0       Set to value for the USB to RS232 cord


AUDIO_DEV=alsa:plughw:0   The AUDIO_DEV change to 0 for the USB sound card

PTT_PORT=/dev/ttyUSB0       set to value for the USB to RS232 cord

[LocationInfo]      Update the server list to to rotate type

CALLSIGN=EL-YourCallSign         Input your callsign shown on, format is EL-YourCallSign

Press ctrl + x save & quit the editor.


Please be reminding that the SQL_DET should set to VOX, not CTCSS. It is because the audio isolation transformer ‘s frequency response is starting from 200-300Hz which higher than the tone used locally.

If want to use CTCSS detection, you may need direct connection method for the HT & sound card. However, I do not recommend use this method for long term operation. And the sound quality was poor than audio transformer.



Courtesy of

Edit the file asound.conf by the following command:

sudo nano asound.conf

pcm.mmap0 {

type mmap_emul;

slave {

pcm “hw:0,0”;



Add # to disable the following rows:

#pcm.!default {

# type plug;

# slave {

# pcm mmap0;

# }


And add the following code to the bottom:

pcm.lowrec {

type plug

slave {

pcm “hw:1,0”



Press ctrl + x save & quit the editor.


All the configuration & setup was completed, please reboot your system.


The setup of your broadband router

The FAQ of the Echolink official site mentioned TCP port 5200, UDP 5198,5199 should be open.

If those ports was closed, the other cannot connect your node via internet.



To test does your home’s network setup to fulfill Echolink requirements, please install Echolink client software to your computer at home. Run it after installation, then Tools => Firewall / RouterTest.



The above test result shown that UDP protocol was unsucessful, while TCP is OK.

Login to the BB router, Enter the Port forwarding section, forwarding the Port 5198,5199 UDP packets to your RPi’s IP address.


Port Forwarding setup (for reference)



Virtual Server setup (for reference)

Also register the RPi’s IP address for the virtual server.


System tuning

For the RPi audio volume setup, please enter the following command:


The default setting of the MIC was mute & volume is 0. Use Tab to select the mic, and then press m button. It will unmute the Microphone input. Use upper arrow key to increase it’s volume to the same level of speaker. Then press ESC save & exit.





Adjustment the VR of the sound modem

According my testing result, the sound card to Handheld side use the default value (middle) is OK. For the input side, we need enter svxlink to tune the VR value.

Please enter command svxlink to enter the program, key the PTT on the handheld, if the screen shows “Distorsion detected! Please lower the Input volume “, adjust the VR to the GND side slowly. Retry until the message did not show.


The adjustment was complete. We can trial run now.


Trial Run

We can run svxlink in 2 ways:

Enter command: svxlink. It will shown detail operation status. It suitable for the new beginner.

Enter svxlink –daemon. It runs the program on daemon.

We enter svxlink to start the trail run. It will prompt to login echolink server. As we activated the location info feature, you will see your station in .


When press * in the handheld, the echolink node will play your callsign, PL tone message.

If the above step was success, Please press 9999# to login the Echolink Testing server. It used to simulate the situation of QSO, it is a sound recorder, and will replay your voice afterward your release the PTT a while. The QSO status will be shown on the message detail of your station in


Please be reminding that the DTMF is software decoding, so do not enter the key too fast. If svxlink success decodes the key, the corresponded key will be display on the screen. If your handheld do not equipped with DTMF feature, you may direct enter the key by your USB keyboard.

After the Echolink test, please press # logout the server. You may launch your node for production.

Problem found in the production phase

It founds the svxlink will not respond after run 6 – 17 hours, the RPi hang up, all the LED light, not flash as usual. You may also found your station disappear in the map.

I used a RPi ver2.0 which RAM size was doubled to proceed test again, the operating time increase to 2-3 days and then hangup, too. So far I cannot find any solution to fix it.


Experience sharing to use svxlink as an Echolink Node

It always found the svxlink cannot login to the Echolink server successfully on the first time, it prompt it need wait several minutes. If you do not want to wait; simply reboot the RPi and run svxlink again, it always success to do so on second time.


There are 2 ways to contact with Echolink node. The first is entering the destination node number, and the other one is enter the callsign.

The Callsign is combined by DTMF signal according the following table.

1 = Other Character2 = A B C3 = D E F
4 = G H I5 = J K L6 = M N O
7 = P Q R S 8 = T U V9 = W X Y Z
* = Start / Wildcard# = End

If there are one more callsign according the DTMF combination, it will shows in a list

Here are some examples:

Example 1:

If want talk to node No. 788906 (VR2XKP), please enter:


Example 2:

If want search local (VR2) online echolink station, please enter:




Example 3:

Want to QSO with VR2VOI-L, please enter:

6 *87286415#

As the DTMF combination of VR2VOI-L and VR2UNG-L is identical, if both of them are online, svxlink will list their callsign. You can press 1 or 2 to select talk to whom.

Here is my demo in YouTube:



Although the svxlink cannot operate in RPi for long term, but it should be the cheapest costs to play echolink.

As the OS of RPi always release update version, I hope the problem will be solve soon.

This entry was posted in English Articles and tagged , . Bookmark the permalink.

56 Responses to Life of RPi, using svxlink as Echolink node in RPi

  1. Mike AE4ML says:

    I was following your instructions above. Very nicely done. when I got to sudo nano asound.conf . I dont see that file anyplace to edit. Any thoughts ?

    Edit the file asound.conf by the following command:

    sudo nano asound.conf

    – See more at:

    • administrator says:


      1/ Have you remove the pulseaudio ?

      2/ Can you enter alsamixer ?

      3/ have you plug the USB sound card before installation ?



      • IW5EKI says:

        same here file asound.conf is empty….

        any suggestion, maybe my usb-soundcard it isn’t compatible?

        • administrator says:


          1/ ensure plug the USB sound card before setup

          2/ after boot up the RPi, type command “lsusb”, you should found the USB sound card device in the list.

          3/ google asound.conf missing in Raspberry pi, there are many useful info.

          4/ The file is a configuration files for ALSA drivers , try command to install it:

          sudo apt-get install alsa-utils

  2. Fabiano says:

    Hello, excellent publication.
    Could be made available for download is ready image?
    I have practice with linux and I need to ride my echolink link
    Thank you!

  3. Ian G0TJH says:

    Hi like the last post ,have you an image file as i am new to the Pi and linux and it`s a bit over my head i think . Ian

    • administrator says:

      As the configuration will various on different setting, no image provided. And the setup procedure was included on the article, please try.

  4. Ian G0TJH says:

    Well not wanting to give up just yet …last time  . I got on fine till the part "loading the sound files".

    it looks like the line    >sudo mkdir –p /usr/share/svxlink/sounds/en_US  has a mistake in it as

    the next line >cd en_US-heather-11.11         but that is not directory we just made ?

    but no matter how i change it… i cant get passed this problem. 

    • VR2XKP says:

      tar -jxvf sounds-en_US-heather-11.11.tar.bz2
      This is the command to untar the sound clip files to a TEMP folder named "en_US-heather-11.11"

      sudo mkdir –p /usr/share/svxlink/sounds/en_US
      This is the command to built up the destination folder, it meams the svxlink will use it.

      cd en_US-heather-11.11
      This is the command to change to folder to the above TEMP folder

      sudo cp –r * /usr/share/svxlink/sounds/en_US
      This is the command to copy all the files from the TEMP folder to destination folder.

      Of course you can untar the sound clips files to the destination folder directly, if you fluent on Linux command

    • Gabriele says:

      sudo mkdir -p/usr/share/svxlink/sounds/en_US

      this command return to me "mkdir cannot create directory no such file or directory"


      cd en_US-heater-11.11

      return "no such file or directory"

      i'm sure that i have no typo due to copy paste of the command.


      can you help me?? sorry for bad english

      tar -jxvf sounds-en_US-heather-11.11.tar.bz2


      tar -jxvf sounds-en_US-heather-11.11.tar.bz2

      tar -jxvf sounds-en_US-heather-11.11.tar.bz2

      sudo mkdir –p /usr/share/svxlink/sounds/en_US  has a mistake in it as – See more at:

      sudo mkdir –p /usr/share/svxlink/sounds/en_US  has a mistake in it as – See more at:

      sudo mkdir –p /usr/share/svxlink/sounds/en_US  has a mistake in it as – See more at:

      • administrator says:


        A space should after the “-p”.

        If you are not fluent on Linux command (like me), Do not just copy & paste the command. You should check the syntax before every step.

      • David-ZR6DLG says:

        Hi there

        1: ” sudo mkdir -p/usr/share/svxlink/sounds/en_US”
        should read
        “sudo mkdir /usr/share/svxlink/sounds/en_US -p”

        2: “cd en_US-heater-11.11”
        should read
        “cd en_US-heater”

        And in still having no luck with the asound.conf file .
        it does not exist in the current location

  5. Ian G0TJH says:

    yes it was those instuctions that did not work ,, but i install them in the right place with the gui desktop………and it works !

    but i have one problem . With my usb>serial adpt when the Pi is just sitting there and booting to the cmd promt the TX is on untill i start svxlink then it stops.

    1 is this normal or is it my adpt ?
    2 if so will it be the same with the gpio keying .

    At the moment i am doing a test on running its been around 13 hours to date Thats running in a cmd window on the desktop with a vnc server running and only echolink and help modules running .

  6. Dave says:

    I had the same problem trying to make the directories, it says it did not make them. Use the cd command and change directory into the /usr/share location and make sure the directories are there. I was suprised to find they were. Then instead of using sudo to move the files, use the command “sudo su” to bring you to root access. Then change directory into the sound files, then use the command to move the sound files. For some reason I could not even move them using the GUI, but I found that the permissions in the folder required root access.

    Also when you un tar the sound files, use the “dir” command to check the name of the directory, mine was shortened quite a bit over the name listed above. Hope that helps someone.

  7. Zsolt says:


    nice article! I wonder if it would be more stable to use a BeagleBone Black instead of Raspberry Pi. You know Beagle is more powerful.

  8. Peter says:

    Hi, great article, thanks!

    I have a few problems. When I try to connect to echolink with mobile phone app I get this error:

    Incoming EchoLink connection from VK4QC (Peter) at
    Spurious audio packet received from
    Incoming EchoLink connection from VK4QC (Peter) at
    *** WARNING: Ignoring incoming connection from VK4QC since the IP address registered in the directory server ( is not the same as the remote IP address ( of the incoming connection.

    Any ideas?

    • VR2XKP says:

      Hi Peter

      Double check the BB router port forwarding / virtual server setup. it seems your Echolink RPi cannot talk to the outside world completely.

  9. Peter says:

    Hi, it’s a Linux issue, but how do you stop the daemon?

    Thanks, Peter VK4QC

    • administrator says:

      Hi Peter

      All the installation procedure shown on the article. I did not stop any daemon.

      If you means stop the Echolink service, I simply turn off the power or by shutdown command.

  10. Peter says:

    Hi again,

    Well I’m not too clever, but you mentioned there are two ways to start svxlink, the 2nd being svxlink –daemon. Then I wondered how to stop the daemon (if you wanted to). I googled everywhere and NOBODY seems to know! Turning off the power to the Pi can cause corruption of the sd card. Had that happen a few times! So I would like to know is there a command for stopping a service rather shutting down or rebooting the Pi.

    [email protected]

    • David says:

      You can send a kill signal to the svxlink process. If you run it in non-daemon mode, you will notice that you can stop it with ctrl+C (which sends a SIGINT signal and says so in the log output). Since there should be only one, it’s pretty simple to just use the killall command:

      killall -sSIGINT svxlink


      killall svxlink

      probably works just as well. I just use SIGINT because it’s a signal I know svxlink responds to.

      If you want more details about signals that can be sent to processes, read the man pages for signals:

      man 7 signal

  11. VR2XKP says:

    Hi again

    I refer some links, some hams write a shell script to start /stop the daemon.

  12. Richard, G0EWH says:


    First, I must say I found your details very good and helpful.

    I also had the problem of no asound.conf file to edit, so created it, but did not make any difference to my sound problem.

    Newer versions of SvxLink (such as the latest 13.12) have the ability to use 16 kHz samples voices, but when using 8k ones, svxlink will not play them and says they are not supported.  Changing the sample rate in the [GLOBAL] section of svxlink.conf causes the program startup to fail with an error saying only 16k & 48k files are supported. However, both 8k & 16k audio files are available for version 13.12?

    I find that the audio I am getting is distorted and very poor in quality.  The USB sound adaptor is a 7.1 channel Cm108 similar to the black one shown, but doing a "lsusb -t" shows it has a Cm109.

    Any suggestions please?


    • VR2XKP says:


      I did not tested the latest svxlink. But the Rpi did not support 16k sound files on the moment I test.

      You may try update your RPi firmware to latest, the sound config file should appear, otherwise the USB sound card is not supported.

      To know your sound card is CM108 or 109, plug it to a MS windows system, e.g. XP or windows 7, it will show the chipset use after the driver sucessfully installed

    • administrator says:

      Please try the following command to update the Rpi firmware:

      sudo apt-get install rpi-update
  13. Kevin says:

    Thanks for the article. It helped a lot. Being a noobie I needed that. The Rpi and Svxlink are up and running. Now I am tweeking the settings. One thing I have tried to find a solution with no luck. When I connect to my node on Echolink from my laptop, the Description information does not appear in the right hand upper window of Echolink. Isn’t this where it should be displayed? Or how/where do I see the information from the DESCRIPTION field in the ModuleEchoLink.CONF file?



    • VR2XKP says:

      If the Descrption field was missed on the CONF files, try add it manually according the article's info.

      • Kevin says:

        The DESCRIPTION filed is in there, but I do not see where that information is ever displayed. Is this what a user should see if they connect with Echolink program?

        • administrator says:

          I did not have idea on it. Some description may be used for the user reference, not for the machine show to others.

  14. Lee Lewis says:

    Great Article, I noticed an update for svxlink , mainly for the raspberry pi

    could you please help me with the commands to update to the latest version of svxlink


  16. Glen says:

    I under stand the sudo mkdir -p /usr/share//svxlink/sounds/en_US
    but the code cd en_US-heather-11.11 does not work it says no such file or directory

  17. Glen says:

    I made a mistake in the code for I put too many Forward slashes in the last reply sudo mkdir -p /usr/shaes/svxlink/sounds/en_US. thecode cd en_US-heather-11.11 does not work

  18. Glen says:

    thanks for the help I got a little further than before
    when i input the code: sudo mkdir -p /usr/share/svxlink/sounds/en_US I can’t tell if it works because the next line of code:cd en_US-heather-11.11 comes back saying no such directory HELP

  19. Glen says:

    why when I enter this command I get a blank screen : sudo nano /etc/svxlink/svxlink.d/ModuleEchoLink.conf

  20. Glen says:

    it’s me again
    I can get through the wget
    and: tar -jxvf sounds-en_US-heather-11.11.tar.bz2
    and: sudo mkdir -p /usr/share/svxlink/sounds/en_US
    and when I get to cd en_US-heather-11.11 it says no dir found
    so I can,t get to sudo cp -r* /usr/share/svxlink/sounds/en_US

  21. Glen says:

    I think I got had to do some looking around but I got 13.12 loaded with sounds so far so good

  22. David-ZR6DLG says:

    Hi all …

    I Cant seem to find that file , I’m not quit Shaw if it might be a different folder
    can any one put some light on this matter ..

    Please …….

  23. Peter Norris says:

    Thank you for a great article. I have an error during installation of the files; unable to locate package libsigc++-1.2-dev , couldn’t find any package by regex ‘libsigc++1.2-dev’.
    Can some help me please find the right one. VK3JUG

  24. Hi to every body, it’s my first pay a visit of this weblog; this weblog contains remarkable and in fact fine stuff in favor of visitors.

  25. Hello everyone!
    I have a raspberry pi 2 with 900 MHz and 1GB and preocessador Quadricore unfortunately so far was unable to work because it presents alsa problems, it will be that this is incompatible raspberry 2 ?? I’m using sound card virtual 7.1 channel sound with Jessie installed, someone can help me
    Thank You
    Pu7iss – Brazil

  26. F5UII says:

    Hello Francis, Hello to all readers,

    I just wanted to know that with my friend Juan F8ASB, we have finalised a nice board that is directly to plug on a Raspberry Pi, and usable with the famous Svxlink software.

    We have it called ‘SvxLink Card’ or ‘SvxCard’. You have all details and running developpement on

    For those who are interested in having a board to mount, you can participate to an opened grouped purchases on

    With my 73 !
    Chris, F5UII

  27. Michael K9DBX says:

    Well done, thanks. I have a few questions you may be able to help me with:

    I get “Distortion detected! Please lower the input volume!” And I can’t seem to get that message to go away. If I turn down the radio volume too much svxlink won’t detect any squelch. You talk about VR2, is this the pot on your mic line? Why wouldn’t the radios volume knob do the same thing?

    When I connect and then press 9999#, I connect with the test server but never get the announcement from the Echolonk server that says “welcome to the Echolink test server, this server records and plays back your transmission……..”, even though I can record and playback my voice test. My router passes all of the open ports tests.

    Thanks for a great blog page on this subject – Mike K9DBx

    • administrator says:


      VR2 is the prefix of the amateur radio callsign of Hong Kong, please do not mixed with Variable Resistor together.

      Please refer the diagram from VE3ELB Website, It is a recommended connection between the radio and the sound dongle, and it includes a variable resistor for level adjustment on each sides.

      Any do you heard any sound from svxlink ? e.g. time announcement in regular period say every 15min.

  28. Great article, exactly what I was looking for.

  29. I got the fallowing errors

    pi@raspberrypi:~/svxlink-11.11.1 $ sudo make
    — Creating .config…
    — Checking if chgrp understand the -h switch…yes
    — Checking if chown understand the -h switch…yes
    — Checking if echo parses –…no
    — Checking for QT…yes (pkg-config QtCore)
    — Checking for sigc++ 1.2…yes
    — Checking for TCL development library…8.5
    — Checking for speex…1.2rc1
    — Checking for libgcrypt…1.6.3
    ————– async ————–
    ————– async/core ————–
    — Creating ../../include/AsyncApplication.h…
    — Creating directory ../../include…
    — Creating ../../include/AsyncFdWatch.h…
    — Creating ../../include/AsyncTimer.h…
    — Creating ../../include/AsyncIpAddress.h…
    — Creating ../../include/AsyncTcpClient.h…
    — Creating ../../include/AsyncDnsLookup.h…
    — Creating ../../include/AsyncUdpSocket.h…
    — Creating ../../include/AsyncTcpServer.h…
    — Creating ../../include/AsyncTcpConnection.h…
    — Creating ../../include/AsyncConfig.h…
    — Creating ../../include/AsyncSerial.h…
    ../../ depend/AsyncApplication.dpp: No such file or directory
    ../../ depend/AsyncFdWatch.dpp: No such file or directory
    ../../ depend/AsyncTimer.dpp: No such file or directory
    ../../ depend/AsyncIpAddress.dpp: No such file or directory
    ../../ depend/AsyncDnsLookup.dpp: No such file or directory
    ../../ depend/AsyncTcpClient.dpp: No such file or directory
    ../../ depend/AsyncUdpSocket.dpp: No such file or directory
    ../../ depend/AsyncTcpServer.dpp: No such file or directory
    ../../ depend/AsyncTcpConnection.dpp: No such file or directory
    ../../ depend/AsyncConfig.dpp: No such file or directory
    ../../ depend/AsyncSerial.dpp: No such file or directory
    ../../ depend/AsyncSerialDevice.dpp: No such file or directory
    — Creating dependency file depend/AsyncSerialDevice.dpp…
    — Creating dependency file depend/AsyncSerial.dpp…
    — Creating dependency file depend/AsyncConfig.dpp…
    — Creating dependency file depend/AsyncTcpConnection.dpp…
    — Creating dependency file depend/AsyncTcpServer.dpp…
    — Creating dependency file depend/AsyncUdpSocket.dpp…
    — Creating dependency file depend/AsyncTcpClient.dpp…
    — Creating dependency file depend/AsyncDnsLookup.dpp…
    — Creating dependency file depend/AsyncIpAddress.dpp…
    — Creating dependency file depend/AsyncTimer.dpp…
    — Creating dependency file depend/AsyncFdWatch.dpp…
    — Creating dependency file depend/AsyncApplication.dpp…
    — Compiling AsyncApplication.cpp…
    — Compiling AsyncFdWatch.cpp…
    — Compiling AsyncTimer.cpp…
    — Compiling AsyncIpAddress.cpp…
    — Compiling AsyncDnsLookup.cpp…
    — Compiling AsyncTcpClient.cpp…
    — Compiling AsyncUdpSocket.cpp…
    — Compiling AsyncTcpServer.cpp…
    — Compiling AsyncTcpConnection.cpp…
    — Compiling AsyncConfig.cpp…
    — Compiling AsyncSerial.cpp…
    — Compiling AsyncSerialDevice.cpp…
    — Creating archive ../../lib/libasynccore.a…
    — Creating directory ../../lib…
    — Linking ../../lib/…
    ————– async/cpp ————–
    — Creating ../../include/AsyncCppApplication.h…
    ../../ depend/AsyncCppApplication.dpp: No such file or directory
    ../../ depend/AsyncCppDnsLookupWorker.dpp: No such file or directory
    — Creating dependency file depend/AsyncCppDnsLookupWorker.dpp…
    — Creating dependency file depend/AsyncCppApplication.dpp…
    — Compiling AsyncCppApplication.cpp…
    — Compiling AsyncCppDnsLookupWorker.cpp…
    AsyncCppDnsLookupWorker.cpp: In destructor ‘virtual Async::CppDnsLookupWorker::~CppDnsLookupWorker()’:
    AsyncCppDnsLookupWorker.cpp:171:22: error: ‘close’ was not declared in this scope
    AsyncCppDnsLookupWorker.cpp:175:22: error: ‘close’ was not declared in this scope
    AsyncCppDnsLookupWorker.cpp: In member function ‘virtual bool Async::CppDnsLookupWorker::doLookup()’:
    AsyncCppDnsLookupWorker.cpp:195:14: error: ‘pipe’ was not declared in this scope
    if (pipe(fd) != 0)
    AsyncCppDnsLookupWorker.cpp: In static member function ‘static void* Async::CppDnsLookupWorker::workerFunc(void*)’:
    AsyncCppDnsLookupWorker.cpp:291:42: error: ‘write’ was not declared in this scope
    ret = write(worker->notifier_wr, “D”, 1);
    ../../ recipe for target ‘AsyncCppDnsLookupWorker.o’ failed
    make[3]: *** [AsyncCppDnsLookupWorker.o] Error 1
    Makefile:44: recipe for target ‘all’ failed
    make[2]: *** [all] Error 2
    Makefile:115: recipe for target ‘all’ failed
    make[1]: *** [all] Error 2
    Makefile:115: recipe for target ‘all’ failed
    make: *** [all] Error 2
    pi@raspberrypi:~/svxlink-11.11.1 $ sudo make
    ————– async ————–
    ————– async/core ————–
    ————– async/cpp ————–
    — Compiling AsyncCppDnsLookupWorker.cpp…
    AsyncCppDnsLookupWorker.cpp: In destructor ‘virtual Async::CppDnsLookupWorker::~CppDnsLookupWorker()’:
    AsyncCppDnsLookupWorker.cpp:171:22: error: ‘close’ was not declared in this scope
    AsyncCppDnsLookupWorker.cpp:175:22: error: ‘close’ was not declared in this scope
    AsyncCppDnsLookupWorker.cpp: In member function ‘virtual bool Async::CppDnsLookupWorker::doLookup()’:
    AsyncCppDnsLookupWorker.cpp:195:14: error: ‘pipe’ was not declared in this scope
    if (pipe(fd) != 0)
    AsyncCppDnsLookupWorker.cpp: In static member function ‘static void* Async::CppDnsLookupWorker::workerFunc(void*)’:
    AsyncCppDnsLookupWorker.cpp:291:42: error: ‘write’ was not declared in this scope
    ret = write(worker->notifier_wr, “D”, 1);
    ../../ recipe for target ‘AsyncCppDnsLookupWorker.o’ failed
    make[3]: *** [AsyncCppDnsLookupWorker.o] Error 1
    Makefile:44: recipe for target ‘all’ failed
    make[2]: *** [all] Error 2
    Makefile:115: recipe for target ‘all’ failed
    make[1]: *** [all] Error 2
    Makefile:115: recipe for target ‘all’ failed
    make: *** [all] Error 2

  30. Maurice says:

    Great site. Using your comments I was able to get my Raspberry Pi 3, Svxlink Echolink Simplex node up and operating. Now that I have it up I wanted to add some features but don’t understand how. I would like to add some modules to bring up specific repeaters that I use. I’ve entered the proper statement in the macros section but don’t know how or where to create a module that corresponds to the macro name. The standard Echolink macro works but not others that I enter. Could you enlighten me?

Leave a Reply

Your email address will not be published. Required fields are marked *