[Dan, KG7PAR]

I think the fastest way to try would be to just add a space before the callsign

[Dan, KG7PAR]

Hello,

Sounds like you are trying to use the display screen. Open repeater is meant to be run headless via web address. As such the displays are unsupported within the raspberry pi images themselves.

Being you have wifi working, you should be able to point your web browser to openrepeater.local and get in that way.

Also being this is the pi zero and the mtr2000 hardware, please review the knowledge base article on ics-ctrl.com related to this configuration as it is a special setup and the radio details are particular.

https://ics-ctrl.com/using-the-pi-repeater-1x-mtr2000-with-the-mtr2000/

[Dan, KG7PAR]

What hardware board are you using, or what is the schematic of the interface adapters you are using to convert radio signals to those compatible with the RPI?

The port 1 is a repeater, so yes it is expected that the COS would trigger the PTT to immediately go active and would stay active until the COS is released plus some small delay.

Additionally the PTT will go active when the system self identifies, and when there is an incoming echolink event.

There is nothing unstable in the default settings, this revision has been available for several years now with no reports I am aware of related to instability. Perhaps the TX radio is getting into the RX radio? I have seen this several times and will appear to be an oscillation behavior as the TX causes the RX to open which causes the TX to enable, cycle repeats indefinetely

[Dan, KG7PAR]

Hi Jeff,

The alsamixer setting seem to be constantly changing, and admittedly I have no idea what most of them do. For our purposes the only ones that matter are the line in (mic?) And line out levels and PCM (virtual mixer). We typically recommend keeping these all at 80% to help prevent digital clipping of the audio.

As for mixing between channels, there is no mixing between channels, they are completely isolated in the audio path. The linking audio is done inside the svxlink software entirely.

If you need to adjust the linked audio levels, you need to do it with the adjustment pots on the board. There is a few setting in svxlink where you can adjust gain in db, but to my knowledge nobody really uses these and they are certainly not supported by the open repeater UI.

Dan, kg7par

[Dan, KG7PAR]

Also confirm your router setting are all correct. This is most common issue with echolink.

https://secure.echolink.org/pingTest.jsp

[Dan, KG7PAR]

@Adi,

would you be able to give me a basic crash course on the selective calling functionality and the basic usage for this module? I found a Wikipedia link for the basics of selective calling in general and I think I have a grasp on that part, but nothing about how this module wraps into the schema.

I am compiling and consolidating a lot of information on SVXLink, modules, etc. and I cant really find anything at all on this particular modules usage online or in the man pages, its quite sparse. I looked at the TCL code, but not understanding the basics I am at a loss to describe what exactly the module does and the basic workflow of what to set, how to set it, how to use it, etc.

Any details you can provide would be greatly appreciated.

[Dan, KG7PAR]

@DL4BBD

I am looking to see if you happen to have the sound files in German available that you could point me to? I am looking for locations for various language pack sets and yours is the only German I have come across so far.

Appreciate if you can share

[Dan, KG7PAR]

@DL4BBD

I am looking to see if you happen to have the sound files in German available that you could point me to? I am looking for locations for various language pack sets and yours is the only German I have come across so far.

Appreciate if you can share

[Dan, KG7PAR]

Let me take a stab at some of these

#1 – I believe this is a feature that is standard on raspberry pi now, check raspi-config menu. I think that’s where I saw it. Otherwise have a google for it, this is a widely used function on rpi.

There is a gotcha here, if the system is shutdown, but then power never actually fails, the pi will never turn back on until you can forcefully trip the power.

#2 – use gpio for echolink start. Whats your end goal here? I assume you want to setup echolink on a timer or such, if so there are ways to do it with cron/scripts directly using DTMF_pty_ctrl or something close to that config variable. This allows you to inject a dtmf tone via the console so its not audible, thus not audibly hackable.

I believe if you go this route though, you will still have audible dtmf tones to deal with but you could change the access code to something ridiculous that no one would guess.

As for disabling the modules, I am pretty sure that will still be #. That will be like changing the enter key on your computer to the space bar. Possible, but not practical. Not sure how to get around this off hand, but I think there might be a config variable to mute all dtmf, but that may be going too far.

For the announcements, check svxlink.groups.io I think this was discussed there a while back.

#3 – the first thought that comes to mind is a log file monitor script. There is also state_pty option I think Aaron was planning to tinker with, maybe the state of echolink is available there??

#4 – you got it right

[Dan, KG7PAR]

Great, glad you were able to find a solution

[Author]

Posts