Quantcast

Re: Svxlink-devel Digest, Vol 122, Issue 1 - Reply Msg #3

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Svxlink-devel Digest, Vol 122, Issue 1 - Reply Msg #3

KB1NYT
Repeater Controller Setup

I got it working. The only change I made was I added NO_REPEAT=0 which
was commented out.

The issue I have now is we have an echo on the audio. The audio sounds
good but there is and echo. It sounds like you are talking with another
radio in the background.

Thanks Jay

On 1/4/2017 7:08 PM, [hidden email] wrote:

> Send Svxlink-devel mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/svxlink-devel
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Svxlink-devel digest..."
>
>
> Today's Topics:
>
>     1. Audio device busy running as daemon 4,5,6 (Jay)
>     2. Re: Audio device busy running as daemon 4,5,6 (Rob Janssen)
>     3. Repeater Controller Setup (Jay)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 21 Dec 2016 18:36:10 -0500
> From: Jay <[hidden email]>
> Subject: [Svxlink-devel] Audio device busy running as daemon 4,5,6
> To: [hidden email]
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> Thank you for the replies. The issue was pulseaudio was installed I
> removed that and now we get farther. Not sure why the pulseaudio didn't
> affect running from the cmd line only starting as a service.
>
> I am guessing the network isn't ready in time for Svxlink after boot. If
> I stop and then start no error and everything works. I guess I could
> start Svxlink from rc.local instead.
>
> "SimplexLogic"
> Wed Dec 21 15:45:59 2016:     Found /usr/lib/ModuleHelp.so
> Wed Dec 21 15:45:59 2016:     Module Help v1.0.0 starting...
> Wed Dec 21 15:45:59 2016: Loading module "ModuleEchoLink" into logic
> "SimplexLogic"
> Wed Dec 21 15:45:59 2016:     Found /usr/lib/ModuleEchoLink.so
> Wed Dec 21 15:45:59 2016:     Module EchoLink v1.3.2 starting...
> Wed Dec 21 15:45:59 2016: SimplexLogic: Event handler script
> successfully loaded.
> Wed Dec 21 15:45:59 2016: *** ERROR: No IP addresses were returned for
> the EchoLink directory server DNS query
> Wed Dec 21 15:45:59 2016: *** ERROR: EchoLink directory server DNS
> lookup failed
> Wed Dec 21 15:45:59 2016:
> Wed Dec 21 15:45:59 2016: EchoLink directory status changed to ?
>
> On 12/21/2016 3:12 PM, [hidden email] wrote:
>> Send Svxlink-devel mailing list submissions to
>> [hidden email]
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.sourceforge.net/lists/listinfo/svxlink-devel
>> or, via email, send a message with subject or body 'help' to
>> [hidden email]
>>
>> You can reach the person managing the list at
>> [hidden email]
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Svxlink-devel digest..."
>>
>>
>> Today's Topics:
>>
>>      1. REJECT_OUTGOING evaluated after ACCEPT_OUTGOING? (isladelobos)
>>      2. REJECT_OUTGOING evaluated after ACCEPT_OUTGOING? (isladelobos)
>>      3. Time for a new Svxlink release? Problem with rapid RX/TX
>>         flapping when connected to Echolink conferences (David Ranch)
>>      4. Audio device busy running as daemon (Jay)
>>      5. Re: Audio device busy running as daemon (Rob Janssen)
>>      6. Re: Audio device busy running as daemon (David Ranch)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sat, 17 Dec 2016 12:05:32 -0000
>> From: "isladelobos" <[hidden email]>
>> Subject: [Svxlink-devel] REJECT_OUTGOING evaluated after
>> ACCEPT_OUTGOING?
>> To: "SVXLIN-DEVEL" <[hidden email]>
>> Message-ID: <10E26FBD951A46CEAAA2D90B1D6AB912@dell>
>> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>> reply-type=original
>>
>> Hi.
>>
>> In the man page, about the ModuleEchoLink.conf.
>>
>> I read:
>>
>> ACCEPT_OUTGOING
>> Only accept outgoing connections where the remote callsign match this
>> regular expression. The REJECT_OUTGOING directive will be evaluated before
>> ACCEPT_OUTGOING.
>>
>> For example, i configure the next lines:
>>
>> REJECT_OUTGOING=^(\\*.*\\*)$
>> ACCEPT_OUTGOING=^(\\*CONFERENCE1\\*|\\*CONFERENCE2\\*|\\*ECHOTEST\\*)$
>>
>> We can't connect to any conference, included the ACCEPT_OUTGOING matcheds
>>
>> This configuration is because we connect to some conference in days like
>> sundays or special events.
>> But normaly is non conference connected Link
>>
>> How can accept outgoing only for the accept outgoing conferences?
>>
>> 73's
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sat, 17 Dec 2016 04:47:56 -0700 (MST)
>> From: isladelobos <[hidden email]>
>> Subject: [Svxlink-devel] REJECT_OUTGOING evaluated after
>> ACCEPT_OUTGOING?
>> To: [hidden email]
>> Message-ID: <[hidden email]>
>> Content-Type: text/plain; charset=us-ascii
>>
>> Hi.
>>
>> In the man page, about the ModuleEchoLink.conf.
>>
>> I read:
>>
>> ACCEPT_OUTGOING
>> Only accept outgoing connections where the remote callsign match this
>> regular expression. The REJECT_OUTGOING directive *will be evaluated before
>> ACCEPT_OUTGOING.*
>>
>> For example, i configure the next lines:
>>
>> REJECT_OUTGOING=^(\\*.*\\*)$
>> ACCEPT_OUTGOING=^(\\*CONFERENCE1\\*|\\*CONFERENCE2\\*|\\*ECHOTEST\\*)$
>>
>> We can't connect to any conference, included the ACCEPT_OUTGOING matcheds
>>
>> This configuration is because we connect to some conference in days like
>> sundays or special events.
>> But normaly is non conference connected Link
>>
>> How can accept outgoing only for the accept outgoing conferences?
>>
>>
>>
>> --
>> View this message in context: http://svxlink.996268.n3.nabble.com/REJECT-OUTGOING-evaluated-after-ACCEPT-OUTGOING-tp4797.html
>> Sent from the svxlink-devel mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Sat, 17 Dec 2016 13:00:42 -0800
>> From: David Ranch <[hidden email]>
>> Subject: [Svxlink-devel] Time for a new Svxlink release? Problem with
>> rapid RX/TX flapping when connected to Echolink conferences
>> To: Discussions about development issues
>> <[hidden email]>
>> Message-ID: <[hidden email]>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hey Everyone,
>>
>> I was helping a friend with his Svxlink station flapping RX/TX when in a
>> Echolink conference after 30+min and I first recommended that he first
>> make sure he's running the newest version of Svxlink.  I then looked my
>> self and it seems that the current release code is 15.08 which doesn't
>> have all of the good work committed since then.
>>
>> So... two questions:
>>
>> 1. Are there any plans to release a 2016 or early 2017 version of
>> Svxlink and Qtel?
>>
>> 2.  Has anyone observed this rapid RX/TX flapping every second issue
>> when connected long term to an Echoink conference?  I haven't but I
>> rarely use the conference feature.
>>
>> --David
>> KI6ZHD
>>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Wed, 21 Dec 2016 12:39:42 -0500
>> From: Jay <[hidden email]>
>> Subject: [Svxlink-devel] Audio device busy running as daemon
>> To: [hidden email]
>> Message-ID: <[hidden email]>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>>
>> Hello
>>
>> Svxlink runs fine from the command line but if I try to run it as a
>> daemon I get the following error in the log file. The setup is a
>> Raspberry Pi running Raspbian and a USB sound card. I am using the
>> daemon script that came with the install slightly modified for the dir
>> structure here. The only thing I did not add to the script was the audio
>> strings for start and stop. Svxlink user is part of the audio group. Not
>> sure what to look for.
>>
>> thanks
>> Jay
>> KB1NYT
>>
>> Wed Dec 21 11:54:59 2016: SvxLink v1.5.0 Copyright (C) 2003-2015 Tobias
>> Blomberg / SM0SVX
>> Wed Dec 21 11:54:59 2016:
>> Wed Dec 21 11:54:59 2016: SvxLink comes with ABSOLUTELY NO WARRANTY.
>> This is free software, and you are
>> Wed Dec 21 11:54:59 2016: welcome to redistribute it in accordance with
>> the terms and conditions in the
>> Wed Dec 21 11:54:59 2016: GNU GPL (General Public License) version 2 or
>> later.
>> Wed Dec 21 11:54:59 2016:
>> Wed Dec 21 11:54:59 2016: Using configuration file:
>> /opt/svxlink/etc/svxlink/svxlink.conf
>> Wed Dec 21 11:54:59 2016: --- Using sample rate 48000Hz
>> Wed Dec 21 11:54:59 2016:
>> Wed Dec 21 11:54:59 2016: Starting logic: SimplexLogic
>> Wed Dec 21 11:54:59 2016: Loading RX: Rx1
>> Wed Dec 21 11:54:59 2016: *** ERROR: Open capture audio device failed:
>> Device or resource busy
>> Wed Dec 21 11:54:59 2016: *** ERROR: Could not open audio device for
>> receiver "Rx1"
>> Wed Dec 21 11:54:59 2016: *** ERROR: Could not initialize RX "Rx1"
>> Wed Dec 21 11:54:59 2016: *** ERROR: Could not initialize Logic object
>> "SimplexLogic". Skipping...
>> Wed Dec 21 11:54:59 2016: *** ERROR: No logics available. Bailing out...
>>
>>
>> #!/bin/sh
>> # Debian like server start/stop script, developed for raspbian distro
>> # Copyright (c) 2013-2014 - F1RMB, Daniel Caujolle-Bert
>> <[hidden email]>
>> # Licended under GPL v2 or later
>>
>> #
>> # /etc/default/svxlink support following options:
>> #
>>     GPIO_PTT_PIN=23
>> #     <num> defines the GPIO pin used for PTT.
>>     GPIO_SQL_PIN=27
>> #     <num> defines the GPIO pin used for Squelch.
>> #
>> # AUDIO_SETTINGS_ONSTART="<string>"
>> # AUDIO_SETTINGS_ONSTOP="<string>"
>> #     <string>: shell script command(s)
>> #
>>
>> ### BEGIN INIT INFO
>> # Provides:        svxlink
>> # Required-Start:  $local_fs $remote_fs $syslog $network $ntp
>> # Required-Stop:   $local_fs $remote_fs
>> # Default-Start:   2 3 4 5
>> # Default-Stop:    0 1 6
>> # Short-Description: Start svxLink Server daemon
>> ### END INIT INFO
>>
>> PATH=/sbin:/bin:/usr/sbin:/usr/bin
>>
>> . /lib/lsb/init-functions
>>
>> PROG="svxlink"
>> DAEMON=/opt/svxlink/bin/$PROG
>> #DAEMON=/usr/bin/$PROG
>> PIDFILE=/var/run/$PROG.pid
>> LOCKFILE=/var/lock/$PROG
>> LOGFILE=/var/log/$PROG
>> RUNASUSER=svxlink
>>
>> test -x $DAEMON || exit 5
>>
>> if [ -r /etc/default/$PROG ]; then
>>        . /etc/default/$PROG
>> fi
>>
>> UGID=$(getent passwd $RUNASUSER | cut -f 3,4 -d:) || true
>> SVXLINK_OPTS="--daemon ${LOGFILE:+--logfile=$LOGFILE}
>> ${CFGFILE:+--config=$CFGFILE} --runasuser=$RUNASUSER --pidfile=$PIDFILE"
>>
>> lock_svxlink() {
>>        if [ -x /usr/bin/lockfile-create ]; then
>>            lockfile-create $LOCKFILE
>>            lockfile-touch $LOCKFILE &
>>            LOCKTOUCHPID="$!"
>>        fi
>> }
>>
>> unlock_svxlink() {
>>        if [ -x /usr/bin/lockfile-create ] ; then
>>            kill $LOCKTOUCHPID
>>            lockfile-remove $LOCKFILE
>>        fi
>> }
>>
>> gpio_setup() {
>>       NAME=$1
>>       PIN=$2
>>       DIR=$3
>>       if [ ! -z "$PIN" -a ! -e /sys/class/gpio/gpio$PIN ]; then
>>           # Enable the pin for GPIO:
>>           log_progress_msg "[GPIO $NAME #$PIN"
>>           echo $PIN > /sys/class/gpio/export
>>           # Set the direction to output for the pin:
>>           log_progress_msg ", direction"
>>           echo $DIR > /sys/class/gpio/gpio$PIN/direction
>>           # Make sure that the svxlink user can write to the GPIO pin:
>>           log_progress_msg ", owner]"
>>           chown svxlink /sys/class/gpio/gpio$PIN/value
>>       fi
>> }
>>
>> gpio_unsetup() {
>>       NAME=$1
>>       PIN=$2
>>       if [ ! -z "$PIN" -a -e /sys/class/gpio/gpio$PIN ]; then
>>           log_progress_msg "[GPIO $NAME #$PIN]"
>>           # Enable the pin for GPIO:
>>           echo $PIN > /sys/class/gpio/unexport
>>       fi
>> }
>>
>> case "$1" in
>>        start)
>>        log_daemon_msg "Starting SVXLINK server" "svxlink"
>>
>>        ## Check if svxlink user exists
>>        if [ -z "$UGID" ]; then
>>            log_failure_msg "user \"$RUNASUSER\" does not exist"
>>            exit 1
>>        fi
>>
>>        lock_svxlink
>>
>>        ## Check about pid file
>>        if [ -e $PIDFILE ]; then
>>            if $0 status > /dev/null ; then
>>            log_failure_msg "$PROG is already started; not starting"
>>            return
>>            else
>>            log_progress_msg "[Removing stale PID file $PIDFILE]"
>>            rm -f $PIDFILE
>>            fi
>>        fi
>>
>>        ## GPIO PTT support ?
>>        if [ ! -z "$GPIO_PTT_PIN" ]; then
>>            gpio_setup PTT $GPIO_PTT_PIN out
>>        fi
>>
>>        ## GPIO SQL support ?
>>        if [ ! -z "$GPIO_SQL_PIN" ]; then
>>            gpio_setup SQL $GPIO_SQL_PIN in
>>        fi
>>
>>        ## Audio settings on startup ?
>>        if [ ! -z "$AUDIO_SETTINGS_ONSTART" ]; then
>>            log_progress_msg ", audio"
>>            eval $AUDIO_SETTINGS_ONSTART > /dev/null 2<&1
>>        fi
>>
>>        ## Start the daemon
>>        start-stop-daemon --start --quiet --oknodo --pidfile $PIDFILE
>> --startas $DAEMON -- $SVXLINK_OPTS
>>        status=$?
>>
>>        unlock_svxlink
>>
>>        log_end_msg $status
>>            ;;
>>
>>        stop)
>>        log_daemon_msg "Stopping SVXLINK server" "svxlink"
>>
>>        ## Stopping the daemon
>>          start-stop-daemon --stop --quiet --oknodo --pidfile $PIDFILE
>>
>>        ## Audio settings on leaving ?
>>        if [ ! -z "$AUDIO_SETTINGS_ONSTOP" ]; then
>>            log_progress_msg ", unsetting audio"
>>            eval $AUDIO_SETTINGS_ONSTOP > /dev/null 2<&1
>>        fi
>>
>>        ## Unset GPIO PTT pin, if used
>>        if [ ! -z "$GPIO_PTT_PIN" ]; then
>>            gpio_unsetup PTT $GPIO_PTT_PIN
>>        fi
>>
>>        ## Unset GPIO SQL pin, if used
>>        if [ ! -z "$GPIO_SQL_PIN" ]; then
>>            gpio_unsetup SQL $GPIO_SQL_PIN
>>        fi
>>
>>        log_end_msg $?
>>        rm -f $PIDFILE
>>            ;;
>>
>>        restart|force-reload)
>>        $0 stop && sleep 2 && $0 start
>>          ;;
>>
>>        try-restart)
>>        if $0 status >/dev/null; then
>>            $0 restart
>>        else
>>            exit 0
>>        fi
>>        ;;
>>
>>        reload)
>>        exit 3
>>        ;;
>>
>>        status)
>>        status_of_proc $DAEMON "SVXLINK server"
>>        ;;
>>
>>        gpio)
>>        # PTT
>>        if [ ! -z "$GPIO_PTT_PIN" -a ! -e /sys/class/gpio/gpio$GPIO_PTT_PIN
>> ]; then
>>            log_daemon_msg "Initialize PTT GPIO" "gpio$GPIO_PTT_PIN"
>>            gpio_setup PTT $GPIO_PTT_PIN out
>>        else
>>            log_daemon_msg "Uninitialize PTT GPIO" "gpio$GPIO_PTT_PIN"
>>            gpio_unsetup PTT $GPIO_PTT_PIN
>>        fi
>>        log_end_msg 0
>>
>>        ## Squelch
>>        if [ ! -z "$GPIO_SQL_PIN" -a ! -e /sys/class/gpio/gpio$GPIO_SQL_PIN
>> ]; then
>>            log_daemon_msg "Initialize Squelch GPIO" "gpio$GPIO_SQL_PIN"
>>            gpio_setup SQL $GPIO_SQL_PIN in
>>        else
>>            log_daemon_msg "Uninitialize Squelch GPIO" "gpio$GPIO_SQL_PIN"
>>            gpio_unsetup SQL $GPIO_SQL_PIN
>>        fi
>>        log_end_msg 0
>>        ;;
>>
>>        *)
>>        echo "Usage: $0
>> {start|stop|restart|try-restart|force-reload|gpio|status}"
>>        exit 2
>>        ;;
>> esac
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Wed, 21 Dec 2016 18:42:32 +0100
>> From: Rob Janssen <[hidden email]>
>> Subject: Re: [Svxlink-devel] Audio device busy running as daemon
>> To: Discussions about development issues
>> <[hidden email]>
>> Message-ID: <[hidden email]>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> Jay wrote:
>>> Hello
>>>
>>> Svxlink runs fine from the command line but if I try to run it as a
>>> daemon I get the following error in the log file. The setup is a
>>> Raspberry Pi running Raspbian and a USB sound card. I am using the
>>> daemon script that came with the install slightly modified for the dir
>>> structure here. The only thing I did not add to the script was the audio
>>> strings for start and stop. Svxlink user is part of the audio group. Not
>>> sure what to look for.
>>>
>>> thanks
>>> Jay
>>> KB1NYT
>>>
>>> Wed Dec 21 11:54:59 2016: SvxLink v1.5.0 Copyright (C) 2003-2015 Tobias
>>> Blomberg / SM0SVX
>>> Wed Dec 21 11:54:59 2016:
>>> Wed Dec 21 11:54:59 2016: SvxLink comes with ABSOLUTELY NO WARRANTY.
>>> This is free software, and you are
>>> Wed Dec 21 11:54:59 2016: welcome to redistribute it in accordance with
>>> the terms and conditions in the
>>> Wed Dec 21 11:54:59 2016: GNU GPL (General Public License) version 2 or
>>> later.
>>> Wed Dec 21 11:54:59 2016:
>>> Wed Dec 21 11:54:59 2016: Using configuration file:
>>> /opt/svxlink/etc/svxlink/svxlink.conf
>>> Wed Dec 21 11:54:59 2016: --- Using sample rate 48000Hz
>>> Wed Dec 21 11:54:59 2016:
>>> Wed Dec 21 11:54:59 2016: Starting logic: SimplexLogic
>>> Wed Dec 21 11:54:59 2016: Loading RX: Rx1
>>> Wed Dec 21 11:54:59 2016: *** ERROR: Open capture audio device failed:
>>> Device or resource busy
>>> Wed Dec 21 11:54:59 2016: *** ERROR: Could not open audio device for
>>> receiver "Rx1"
>>> Wed Dec 21 11:54:59 2016: *** ERROR: Could not initialize RX "Rx1"
>>> Wed Dec 21 11:54:59 2016: *** ERROR: Could not initialize Logic object
>>> "SimplexLogic". Skipping...
>>> Wed Dec 21 11:54:59 2016: *** ERROR: No logics available. Bailing out...
>>>
>> It looks like some other software has the device open at the time you start the service.
>> Make sure the commandline version is not running and that no other software that tries
>> to open te audio device (including any "sound daemon" like pulseaudio) is running.
>>
>> Rob
>>
>>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Wed, 21 Dec 2016 12:12:34 -0800
>> From: David Ranch <[hidden email]>
>> Subject: Re: [Svxlink-devel] Audio device busy running as daemon
>> To: Discussions about development issues
>> <[hidden email]>
>> Message-ID: <[hidden email]>
>> Content-Type: text/plain; charset="windows-1252"
>>
>>
>>> It looks like some other software has the device open at the time you
>>> start the service.
>>> Make sure the commandline version is not running and that no other software that tries
>>> to open te audio device (including any "sound daemon" like pulseaudio) is running.
>> It wasn't mentioned which OS is running on the Raspberry Pi but I'm
>> assuming Wheezy as this isn't a Systemd-type startup script.  Make sure
>> that:
>>
>> 1. the svxlink user has been created
>> 2. the svxlink user does NOT have a password (don't allow logins for
>> this user)
>> 3. the svxlink user is in the "audio" unix group
>> 4. the svxlink user is in the "gpio" unix group
>>
>> If you had to add any of the above, reboot the rpi before trying to
>> start Svxlink as a service.
>>
>> If that still doesn't work, see if you can run "sudo su - svxlink" and
>> become the svxlink user.  From there, try starting Svxlink and see if it
>> works or not.
>>
>>
>> Btw, I have a bunch of these setup steps for the Raspberri Pi which also
>> includes hardening, security, etc. if you find it helpful. It's intended
>> for the Direwolf packet program but everything before that might provide
>> you some ideas.
>>
>> http://www.trinityos.com/HAM/CentosDigitalModes/RPi/rpi2-setup.html
>>
>> --David
>> KI6ZHD
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>> ------------------------------------------------------------------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today.http://sdm.link/intel
>>
>> ------------------------------
>>
>> _______________________________________________
>> Svxlink-devel mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/svxlink-devel
>>
>>
>> End of Svxlink-devel Digest, Vol 121, Issue 2
>> *********************************************
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 22 Dec 2016 09:59:18 +0100
> From: Rob Janssen <[hidden email]>
> Subject: Re: [Svxlink-devel] Audio device busy running as daemon 4,5,6
> To: Discussions about development issues
> <[hidden email]>
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Jay wrote:
>> Thank you for the replies. The issue was pulseaudio was installed I
>> removed that and now we get farther. Not sure why the pulseaudio didn't
>> affect running from the cmd line only starting as a service.
>>
>> I am guessing the network isn't ready in time for Svxlink after boot. If
>> I stop and then start no error and everything works. I guess I could
>> start Svxlink from rc.local instead.
> Which version of the OS are you using?  Are you using a classical system5 init
> package or the "systemd" disaster?
>
> The supplied /etc/init.d script has these lines:
>
> # Required-Start:  $local_fs $remote_fs $syslog $network $ntp
> # Default-Start:   2 3 4 5
>
> When you now do "insserv svxlink" the startup of svxlink will be placed way back
> in the startup order, after networking has come up.
>
> In occasional cases the network can be slow to come up due to switches with slow
> spanning tree, dhcp server taking long to assign address, etc.
>
> When your system still has /etc/network/interfaces, make sure there is a line:
>
> auto eth0
>
> for your eth0 interface, not:
>
> allow-hotplug eth0
>
> This makes the system wait for the eth0 interface at bootup, instead of just continuing
> the startup while the network gets settled.
>
> Rob
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 4 Jan 2017 19:07:50 -0500
> From: Jay <[hidden email]>
> Subject: [Svxlink-devel] Repeater Controller Setup
> To: Svxlink <[hidden email]>
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hello
>
> I am tryig to setup Svxlink as a repeater controller. I currently have
> it running as an Echolink using a PI and a TYT radio, working fine. I
> switched the radio to be the receiver on the repeater and the
> transmitter is another TYT. I used the same interface circuit and PI I
> was using for the simplex connection for Echolink. My only change was
> making a wye cable to go from the existing connector on my interface to
> both radios. Using an HT the repeater will key the transmitter but I get
> no audio. I did hear the Echolink ID through the transmitter but I get
> no receive audio. I also noticed when the SQL opens it takes a while
> before the transmitter is opened, looks like a timeout. Below are some
> sections of the config file and log. See anything?
>
> Thanks in advance
>
> Jay
>
> KB1NYT
>
>
> ###############################################################################
>
> # #
> #                Configuration file for the SvxLink
> server                    #
> # #
> ###############################################################################
>
> [GLOBAL]
> #MODULE_PATH=/opt/svxlink/lib/svxlink
> LOGICS=RepeaterLogic
> #LOGICS=SimplexLogic
> CFG_DIR=svxlink.d
> TIMESTAMP_FORMAT="%c"
> CARD_SAMPLE_RATE=48000
> #CARD_CHANNELS=1
> #LOCATION_INFO=LocationInfo
> #LINKS=LinkToR4
>
> [SimplexLogic]
> TYPE=Simplex
> RX=Rx1
> TX=Tx1
> #MODULES=ModuleHelp,ModuleEchoLink
> MODULES=ModuleHelp,ModuleParrot,ModuleEchoLink,ModuleTclVoiceMail
> #MODULES=ModuleHelp,ModuleParrot,ModuleEchoLink
> CALLSIGN=KB1NYT-R
> SHORT_IDENT_INTERVAL=60
> LONG_IDENT_INTERVAL=60
> #IDENT_ONLY_AFTER_TX=4
> #EXEC_CMD_ON_SQL_CLOSE=500
> EVENT_HANDLER=/opt/svxlink/share/svxlink/events.tcl
> DEFAULT_LANG=en_US
> RGR_SOUND_DELAY=0
> REPORT_CTCSS=67
> #TX_CTCSS=ALWAYS
> MACROS=Macros
> FX_GAIN_NORMAL=0
> FX_GAIN_LOW=-12
> #ACTIVATE_MODULE_ON_LONG_CMD=4:EchoLink
> #QSO_RECORDER=8:QsoRecorder
> #ONLINE_CMD=998877
> #MUTE_RX_ON_TX=1
> #MUTE_TX_ON_RX=1
> #STATE_PTY=/var/run/svxlink/state
>
> [RepeaterLogic]
> TYPE=Repeater
> RX=Rx1
> TX=Tx1
> MODULES=ModuleHelp,ModuleParrot,ModuleEchoLink,ModuleTclVoiceMail
> CALLSIGN=KB1NYT
> SHORT_IDENT_INTERVAL=10
> LONG_IDENT_INTERVAL=60
> #IDENT_ONLY_AFTER_TX=4Tx1: Turning the transmitter OFF
>
> #EXEC_CMD_ON_SQL_CLOSE=500
> EVENT_HANDLER=/opt/svxlink/share/svxlink/events.tcl
> DEFAULT_LANG=en_US
> RGR_SOUND_DELAY=0
> REPORT_CTCSS=67.0
> #REPORT_CTCSS=136.5
> #TX_CTCSS=SQL_OPEN
> MACROS=Macros
> #SEL5_MACRO_RANGE=03400,03499
> FX_GAIN_NORMAL=0
> FX_GAIN_LOW=-12
> #QSO_RECORDER=8:QsoRecorder
> #NO_REPEAT=1
> IDLE_TIMEOUT=30
> OPEN_ON_SQL=500
> OPEN_SQL_FLANK=OPEN
> #OPEN_ON_1750=1000
> #OPEN_ON_CTCSS=67:2000
> #OPEN_ON_DTMF=*
> #OPEN_ON_SQL=5000
> #OPEN_ON_SEL5=01234
> #OPEN_SQL_FLANK=OPEN
> #OPEN_ON_SQL_AFTER_RPT_CLOSE=10
> IDLE_SOUND_INTERVAL=3000
> #SQL_FLAP_SUP_MIN_TIME=1000
> #SQL_FLAP_SUP_MAX_COUNT=10
> #ACTIVATE_MODULE_ON_LONG_CMD=4:EchoLink
> #IDENT_NAG_TIMEOUT=15
> #IDENT_NAG_MIN_TIME=2000
> #ONLINE_CMD=998877
> #STATE_PTY=/var/run/svxlink/state
>
>
> [Rx1]
> TYPE=Local
> AUDIO_DEV=alsa:plughw:1
> AUDIO_CHANNEL=0
> SQL_DET=GPIO
> SQL_START_DELAY=3500
> #SQL_START_DELAY=0
> SQL_DELAY=300
> SQL_HANGTIME=2000
> #SQL_EXTENDED_HANGTIME=1000
> #SQL_EXTENDED_HANGTIME_THRESH=15
> #SQL_TIMEOUT=600
> VOX_FILTER_DEPTH=20
> VOX_THRESH=1000
> #VOX_THRESH=1000
> #CTCSS_MODE=2
> #CTCSS_FQ=136.5
> #CTCSS_SNR_OFFSET=0
> #CTCSS_OPEN_THRESH=15
> #CTCSS_CLOSE_THRESH=9
> #CTCSS_BPF_LOW=60
> #CTCSS_BPF_HIGH=270
> SERIAL_PORT=/dev/ttyS0
> SERIAL_PIN=CTS
> #SERIAL_SET_PINS=DTR!RTS
> #EVDEV_DEVNAME=/dev/input/by-id/usb-SYNIC_SYNIC_Wireless_Audio-event-if03
> #EVDEV_OPEN=1,163,1
> #EVDEV_CLOSE=1,163,0
> GPIO_SQL_PIN=!gpio27
> #PTY_PATH=/tmp/rx1_sql
> #HID_DEVICE=/dev/hidraw3
> #HID_SQL_PIN=VOL_UP
> #SIGLEV_DET=TONE
> SIGLEV_SLOPE=1
> SIGLEV_OFFSET=0
> #SIGLEV_BOGUS_THRESH=120
> #TONE_SIGLEV_MAP=100,84,60,50,37,32,28,23,19,8
> SIGLEV_OPEN_THRESH=30
> SIGLEV_CLOSE_THRESH=10
> DEEMPHASIS=0
> #SQL_TAIL_ELIM=300
> #PREAMP=6
> PEAK_METER=1
> DTMF_DEC_TYPE=INTERNAL
> DTMF_MUTING=1
> DTMF_HANGTIME=40
> DTMF_SERIAL=/dev/ttyS0
> #DTMF_PTY=/tmp/rx1_dtmf
> #DTMF_MAX_FWD_TWIST=8
> #DTMF_MAX_REV_TWIST=4
> #1750_MUTING=1
> #SEL5_DEC_TYPE=INTERNAL
> #SEL5_TYPE=ZVEI1
> #FQ=433475000
> #MODULATION=FM
> #WBRX=WbRx1
>
> [Tx1]
> TYPE=Local
> AUDIO_DEV=alsa:plughw:1
> AUDIO_CHANNEL=0
> PTT_TYPE=GPIO
> PTT_PORT=gpio23
> PTT_PIN=gpio23
> # ! inverts pin operation
> #PTT_TYPE=NONE
> #PTT_PORT=/dev/ttyS0
> #PTT_PIN=DTRRTS
> #HID_DEVICE=/dev/hidraw3
> #HID_PTT_PIN=GPIO3
> #SERIAL_SET_PINS=DTR!RTS
> #PTT_HANGTIME=1000
> TIMEOUT=300
> TX_DELAY=500
> #CTCSS_FQ=136.5
> #CTCSS_LEVEL=9
> PREEMPHASIS=0
> DTMF_TONE_LENGTH=100
> DTMF_TONE_SPACING=50
> DTMF_DIGIT_PWR=-15
> #MASTER_GAIN=0.0
>
> Wed Jan  4 10:56:53 2017: Starting logic: RepeaterLogic
> Wed Jan  4 10:56:53 2017: Loading RX: Rx1
> Wed Jan  4 10:56:53 2017: Loading TX: Tx1
> Wed Jan  4 10:56:53 2017: Loading module "ModuleHelp" into logic
> "RepeaterLogic"
> Wed Jan  4 10:56:53 2017:     Found /usr/lib/ModuleHelp.so
> Wed Jan  4 10:56:53 2017:     Module Help v1.0.0 starting...
> Wed Jan  4 10:56:53 2017: Loading module "ModuleParrot" into logic
> "RepeaterLogic"
> Wed Jan  4 10:56:53 2017:     Found /usr/lib/ModuleParrot.so
> Wed Jan  4 10:56:53 2017:     Module Parrot v1.1.1 starting...
> Wed Jan  4 10:56:53 2017: Loading module "ModuleEchoLink" into logic
> "RepeaterLogic"
> Wed Jan  4 10:56:53 2017:     Found /usr/lib/ModuleEchoLink.so
> Wed Jan  4 10:56:53 2017:     Module EchoLink v1.3.2 starting...
> Wed Jan  4 10:56:53 2017: Loading module "ModuleTclVoiceMail" into logic
> "RepeaterLogic"
> Wed Jan  4 10:56:53 2017:     Found /usr/lib/ModuleTcl.so
> Wed Jan  4 10:56:53 2017:     Module Tcl v1.0.1 starting...
> Wed Jan  4 10:56:53 2017: RepeaterLogic: Event handler script
> successfully loaded.
> Wed Jan  4 10:56:53 2017: EchoLink directory status changed to ON
> Wed Jan  4 10:56:53 2017: --- EchoLink directory server message: ---
> Wed Jan  4 10:56:53 2017: EchoLink Server v2.5.9997
> Wed Jan  4 10:56:53 2017:
> Wed Jan  4 10:56:53 2017: ECHO6: N.Virginia, USA
> Wed Jan  4 10:56:53 2017:
> Wed Jan  4 10:57:59 2017: Rx1: The squelch is OPEN (5.39509)
> Wed Jan  4 10:57:59 2017: Tx1: Turning the transmitter ON
> Wed Jan  4 10:58:03 2017: Rx1: The squelch is CLOSED (5.13605)
> Wed Jan  4 10:58:37 2017: Tx1: Turning the transmitter OFF
> Wed Jan  4 10:58:38 2017: Rx1: The squelch is OPEN (5.39888)
> Wed Jan  4 10:58:38 2017: Tx1: Turning the transmitter ON
> Wed Jan  4 10:58:47 2017: Rx1: The squelch is CLOSED (5.14234)
> Wed Jan  4 10:59:19 2017: Tx1: Turning the transmitter OFF
> Wed Jan  4 10:59:54 2017: Rx1: The squelch is OPEN (5.36365)
> Wed Jan  4 10:59:54 2017: Tx1: Turning the transmitter ON
> Wed Jan  4 10:59:58 2017: Rx1: The squelch is CLOSED (5.02776)
> Wed Jan  4 11:00:00 2017: RepeaterLogic: Sending long identification...
> Wed Jan  4 11:00:39 2017: Tx1: Turning the transmitter OFF
> Wed Jan  4 11:01:42 2017: Rx1: The squelch is OPEN (5.21463)
> Wed Jan  4 11:01:42 2017: Tx1: Turning the transmitter ON
> Wed Jan  4 11:01:45 2017: Rx1: The squelch is CLOSED (5.02186)
> Wed Jan  4 11:02:20 2017: Tx1: Turning the transmitter OFF
> Wed Jan  4 11:03:38 2017: Rx1: The squelch is OPEN (5.29975)
> Wed Jan  4 11:03:39 2017: Tx1: Turning the transmitter ON
>
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
> ------------------------------
>
> _______________________________________________
> Svxlink-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/svxlink-devel
>
>
> End of Svxlink-devel Digest, Vol 122, Issue 1
> *********************************************


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Svxlink-devel Digest, Vol 122, Issue 1 - Reply Msg #3

Rob Janssen
Jay wrote:

> Repeater Controller Setup
>
> I got it working. The only change I made was I added NO_REPEAT=0 which
> was commented out.
>
> The issue I have now is we have an echo on the audio. The audio sounds
> good but there is and echo. It sounds like you are talking with another
> radio in the background.
>
> Thanks Jay
>

That is an error in the setup of your soundcard.
As I already mentioned, use alsamixer to setup your card.

When your card is what alsamixer expects, you would want to set the volume of
LINE IN and MIC IN on the playback screen to zero, and on the recording screen
according to your desired input level.  When you open the LINE or MIC IN slider
on the playback screen you feed audio around the svxlink core and you get this
effect.

Unfortunately some soundcards behave strangely and this LINE or MIC slider on
the playback screen actually controls the recording volume, and you need to
set some mute toggle to prevent the feed forward.  This requires experimentation.

Rob

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Svxlink-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/svxlink-devel
Loading...