News little Beep for Echolink user ( Release 13.07 )

    Hello,

    I search in the .tcl , the possibility for modify the news little beep in echolink module with a " CW::play "K"...

    but i don't have a good résult :? , have you a idea :?: :idea:


    Very Thank's 73

    Thierry F4FPQ

    Hi Thierry,

    look at /usr/share/svxlink/events.d/EchoLink.tcl

    Code
    proc is_receiving {rx} {
  if {$rx == 0} {
    playTone 1000 100 100;
  }
}

    overwrite this function with an own one, according to the local principle.

    vy 73's de Adi, DL1HRC

    Quote from dl1hrc

    Hi Thierry,

    look at /usr/share/svxlink/events.d/EchoLink.tcl

    Code
    proc is_receiving {rx} {  if {$rx == 0} {    playTone 1000 100 100;  }}

    overwrite this function with an own one, according to the local principle.

    vy 73's de Adi, DL1HRC

    Hello Adi !

    Very thank's for your respond but this afternoon i modify this code

    Code
    proc is_receiving {rx} {  if {$rx == 0} {    CW::play "K";    playSilence 200;  }}

    But i don't have the k but and i have the little beep


    And after i test with delete the code ...

    Code
    proc is_receiving {rx} {
  if {$rx == 0} {
    CW::play "K";
    playSilence 200;
  }
}

    And i have a little beep :o :? :?

    Thierry

    Hi Thierry,

    did you have changed it and did you made a "make install" later? Then the tcl-files are possibly overwritten.
    You should never change the proc's in the original tcl-Files. Maybe that's the reason.

    You can add a puts "Test K"; in the procedure to check if exactly this proc is called-up, e.g.

    Code
    proc is_receiving {rx} {
  if {$rx == 0} {
    puts "Testing K";
    CW::play "K";
    playSilence 200;
  }
}

    73's de Adi, DL1HRC

    Quote from dl1hrc

    Hi Thierry,

    did you have changed it and did you made a "make install" later? Then the tcl-files are possibly overwritten.
    You should never change the proc's in the original tcl-Files. Maybe that's the reason.

    You can add a puts "Test K"; in the procedure to check if exactly this proc is called-up, e.g.

    Code
    proc is_receiving {rx} {
  if {$rx == 0} {
    puts "Testing K";
    CW::play "K";
    playSilence 200;
  }
}


    73's de Adi, DL1HRC


    Adi,

    For me, it's a news full install of Svxlink ( release 13.7 ) and no a update or other, with a news sdcard for my Raspberry pi.. ;)

    My unique mods at this time is a "K" in Logic.tcl and i have a good result, and for this mods "K" in EchoLink.tcl it's a curious problem... :? :?

    And for info i don't use a "make install" later...

    And the ""puts "Test K"" have don't a good result..

    Very thank's for your help Adi. :D:D

    Thierry

    Adi good news,

    I have the solution, and it's very curious, In my tcl file, i copy a EchoLink.tcl and i rename this for a EchoLink2.tcl backup, and i think there's a conflict..

    When i delete the backup EchoLink2.tcl , and when i reboot svxlink i listen the "K" and i can look the puts "Test K"; in the screen....

    Finaly the problem is the backup .... :D


    But in this version we have a possibility for have a multi server for Echolink, but in the ModuleEchoLink.conf we have just one adresse server for example :

    [ModuleEchoLink]
    NAME=EchoLink
    ID=2
    TIMEOUT=43200
    #ALLOW_IP=xxx.xxx.xxx.xxx
    #DROP_INCOMING=^()$
    #REJECT_INCOMING=^()$
    #ACCEPT_INCOMING=^(.*)$
    #REJECT_OUTGOING=^()$
    #ACCEPT_OUTGOING=^(.*)$
    #CHECK_NR_CONNECTS=2,300,120
    SERVER=europe.echolink.org (------------- :roll:
    CALLSIGN=F4FPQ-L
    PASSWORD=xxxxxxxxx
    SYSOPNAME=F4FPQ
    LOCATION=Grenoble 145.2375 Raspi Svx
    MAX_QSOS=10
    MAX_CONNECTIONS=11
    LINK_IDLE_TIMEOUT=300
    #AUTOCON_ECHOLINK_ID=9999
    #AUTOCON_TIME=1200
    USE_GSM_ONLY=1
    #DEFAULT_LANG=en_US
    DESCRIPTION="QTH: Grenoble\n"
    "QRG: Simplex link on 145.2375 MHz\n"
    "Trx: Pocket Dual band 0.5w\n"
    "Antenna: Dual band Antenna\n"

    Have you idea ?

    Thierry

    Hi Thierry,

    Quote

    In my tcl file, i copy a EchoLink.tcl and i rename this for a EchoLink2.tcl backup, and i think there's a conflict..


    Yes thats the problem! SvxLink loads _all_ files with the extension .tcl in the directory independently from the name.
    If you want to backup a tcl file then rename the extension. So set it to EchoLink.sik or something like that. The more important thing is the content of the file. All of them contain a structure like

    Code
    namespace eval XXXX {  proc first {} {  }  proc second {} {  } ...}

    So a file SimplexLogic.tcl with the content "namespace eval RepeaterLogic { ... }" will overwrite the RepeaterLogic-namespace!!!

    Maybe:

    Code
    SERVER=europe.echolink.org asia.echolink.org servers.echolink.org

    vy 73's de Adi, DL1HRC

    PS: The best way is to hadle own changes by the local principle! The local (private) tcl-files will be loaded after the main tcl's so your private changes in the procedures will remain in the namespace under all circumstances. So your copy EchoLink2.tcl doesn't has any influence anymore (problem with the "K").
    Again: It's not a good idea to change the originally files like EchoLink.tcl, SimplexLogic.tcl, ....

    vy 73's de Adi, DL1HRC