Feat. Request: add CW id string

[gustavc39]

Hi,

I'd like to suggest an improvement in he CW id feature, to make it more flexible.
The default behavior is to send (callsign)/R for repeaters and only (callsign) for link type logics. The problem arises when some information needs to be added to that id string. For example, in my country (Argentina), the rules establish that the minimum data that must be included in the id of a repeater are the callsign and location (city). Also, the addition of the "/R" string is not useful in our case and it must be removed to comply with regulations (in my country that would mean to be operating from a different province). While it's not difficult to make a custom Logic.tcl to accomplish this, it ends up being a hack, and if there's more than one repeater defined in the node, things get more complicated. In short, the suggestion is to add a new variable in the svxlink.conf file to allow the user to define a string that is will be appended to the callsign to create the id. The new variable would be included in the logic config. The "/R" string could be the default value for that variable (in repeater type logics) to get the original behavior. Thank you!

Gustavo - LU7WA

[dl1bz]

That's not really difficult. Make a new /usr/share/svxlink/events.d/local/Logic-mods.tcl and overwrite the procedures (e.g. proc send_short_ident {{hour -1} {minute -1}} ) you want to change. This is part of concept from svxlink for customizing things. If you do so, it's "update-safe".

I do so too and change only this part:

# Play CW id if enabled
if {$short_cw_id_enable} {
  puts "Playing short CW ID"
  if {$CFG_TYPE == "Repeater"} {
    set call "$mycall"
    playSilence 200;
    CW::play $call
    playSilence 200;
  } else {
    playSilence 200;
    CW::play $mycall
  }
  playSilence 500;
}

Don't forget to do this in the right namespace at the begin of Logic-mods.tcl:

namespace eval Logic {
# start of user-defined procedures

}

We also have a lot of repeaters, so we make a git-repo for /usr/share/svxlink/events.d/local and so we can sync and harmonize our changes for rollout to all repeaters. I think that way is ok and there is no need for additonal variables in svxlink.conf (which is up to now more than overloaded with parameters).

73 Heiko, DL1BZ