![how i install dailymotion in echolink receiver how i install dailymotion in echolink receiver](https://3.bp.blogspot.com/-Vq2z_q2_T94/WZMLD6aZ42I/AAAAAAAABL0/BiljTSFr85swTj7YiMMUD2S-s5KscL-MwCLcBGAs/s1600/IMG_20170815_175605.jpg)
Thu Feb 27 10:00:00 2020: Tx1: Turning the transmitter ON Thu Feb 27 10:00:00 2020: SimplexLogic: Sending long identification… It should have successfully connected to EchoLink. Open up the terminal again and tail the svxlink log. Now reload the systemctl daemon, start the svxlink service, and reboot the Pi. Save the changes to the file and exit nano using “ctrl + x” | “y” | “enter”. sudo nano /lib/systemd/system/rviceĭescription=SvxLink repeater control softwareĪfter= remote-fs.target time.targetĮxecStartPre=-/bin/touch /var/log/svxlinkĮxecStartPre=-/bin/chown $RUNASUSER /var/log/svxlinkĮxecStart=/bin/sh -c ‘/usr/bin/svxlink –logfile=/var/log/svxlink –config=$CFG$ Be sure you add the ExecStartPre=/bin/sleep 30 BEFORE THE OTHER ExecStartPre lines. This allowed the Pi to complete the boot process before starting the svxlink service. Making a slight edit to the rvice file and adding a ‘sleep’ delay of 30 seconds resolved the issues for me. The log would show the Pi eventually connecting to EchoLink and then disconnecting. In my case I had several errors relating to DNS and failed lookups for the EchoLink servers. Thu Feb 27 09:43:14 2020: - EchoLink directory server message:. Thu Feb 27 09:43:13 2020: EchoLink directory status changed to ON Thu Feb 27 09:43:13 2020: SimplexLogic: Event handler script successfully loaded. Thu Feb 27 09:43:13 2020: Found /usr/lib/arm-linux-gnueabihf/svxlink/ModuleTcl.so
![how i install dailymotion in echolink receiver how i install dailymotion in echolink receiver](https://3.bp.blogspot.com/-BG09XnTZwP0/Wj5BTJE0w2I/AAAAAAAADV8/yAlaVG1Yy2MtMkkzzwmtDohCk7kCXfa_gCLcBGAs/s1600/IMG_20171223_125756.jpg)
Thu Feb 27 09:43:13 2020: Loading module “ModuleTclVoiceMail” into logic “SimplexLogic” You’ll see the EchoLink Module load and connect to the EchoLink $ tail -f /var/log/svxlink Now ‘tail’ the svxlink log and see if its running. Press “q” to quit when you are done reviewing the service status. Open terminal again and let’s check the svxlink service. Reboot the Pi and let’s get back on track! sudo reboot Issuing the “sudo -u svxlink svxlink” command was starting a second svxlink processes. Therefore, rvice was starting when the Pi booted and already opened the Mic port on the USB Sound Card. Ultimately, I discovered svxlink set itself up as a service during the installation. Honestly, it took me a while to figure out what was happening here. *** ERROR: Could not initialize Logic object “SimplexLogic”. *** ERROR: Could not open audio device for receiver “Rx1”
![how i install dailymotion in echolink receiver how i install dailymotion in echolink receiver](https://i1.wp.com/dishdl.com/wp-content/uploads/2020/03/YE-18000-HD.jpg)
*** ERROR: Open capture audio device failed: Device or resource busy Once the Pi reboots open terminal and start svxlink as we have been. Save the changes and exit nano using “ctrl + x” | “y” | “enter” Let’s dive in and get Rx working.įirst let’s head back to our nf and enable Rx under the section. At the end of part 1 we had Tx setup and working from the Raspberry Pi to the Baofeng HT.