[Aaron, N3MBH]

Ok so it sounds like two separate issues you both are describing:

Maurizio – You may need to check your port forwarding on your router. I am in the process or working on better documentation. I have a Knowledge Base that is in the works so it isn’t publicly linked just yet. There is a start to an EchoLink section: https://openrepeater.com/knowledgebase/category/echolink and there is a minimal article right now that just links to the appropriate place on EchoLinks site. You might want to download and EchoLink application on your computer and use that to run some test. Let me know if this works for you.

F5BCB – You won’t here the system identify over EchoLink. This is for very good reason. If you conferenced your Echolink Node into another group of repeaters, all the identification and announcements on the other systems would be unnecessary and possibly annoying. Hope that makes sense.

73, Aaron – N3MBH

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Aaron, N3MBH]

Send me an email at info at openrepeater dot com. Thanks.

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Aaron, N3MBH]

Thanks for reporting back. Yes, I was aware we were probably going to need to tweak some things with DEEMPHASIS/PREEMPHASIS as well a PL/CTCSS tones, but I haven’t had the opportunity or the setup to test these. I kind of figured, we would get some feedback from the community. Thanks, as this gives me a starting point when I get to that step.

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Aaron, N3MBH]

Not a problem

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Aaron, N3MBH]

Hello Bjorn,
Yes, that is on the todo list. That is exactly where I anticipate placing it also…on the dashboard.

Due to security reasons, trying to access root level commands within the web server is a bad idea or doesn’t always work. We have a couple scripts for things like that and we have to give them special permissions within the OS sudoers file. I think my plan is to make one main “helper” bash script that can control a number of thing by issuing different switches. That way we can add other options in the web gui like being able to set a static IP, timezone, etc.

For the time being, you can turn the web server on and off via SSH (root user).

To turn it off:

service svxlink stop

To turn it back on:

service svxlink start

OR “Rebuild & Restart” from the Web GUI.
OR Reboot

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Aaron, N3MBH]

Not a problem. Now that 1.1.0 is out I am trying to focus on improving documentation. I am working on a Knowledge Base that will have many specific sub topics/tutorials That will go live soon. Hopefully I will get a change to draw up some basic schematics soon and include in the KB.

Juan (from France) is working on a larger board design he is just starting to take pre orders on. This will not have onboard sound and will still require an external USB sound card. It will however have relays to control external devices. It will be offered in kit form where you can purchase the PCB and components pack separately. Last I calculated, I believe it will be over the $100 mark in USD. So doing multiples will be costly.

I think Juan was working on some standardized pinouts that will be shared between his “big board” and the ORP board concept we have shared in the past. I don’t have those pins handy at the moment. If you are building your own interface, it really doesn’t matter, Just so long as you declare your pins in the Web GUI. The background scripts will take care of registering the pins with the OS and svxlink. For example on my RPI2, I am using GPIO 27 for COS and GPIO 22 for PTT.

Hope that Helps.

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Aaron, N3MBH]

Doug,
In theory this should be possible, check out the SVLink documentation here: http://svxlink.sourceforge.net/man/man5/svxlink.conf.5.html.

You would need to add a voter section to the config as well as a network receiver I think. I have yet to try this, but the core appears to support it. Building a web gui for it is another animal.

You can try modding your svxlink config file to test:
/etc/openrepeater/svxlink/svxlink.conf

To prevent the web gui from overwriting these changed you will need to incorporate them into the svxlink_update.php file that is responsible for writing the change to the svxlink.conf file: /var/www/openrepeater/functions/svxlink_update.php

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Aaron, N3MBH]

I know there are talks about doing a WX module, so I don’t know if this would have the tones, but the general idea for svxlink is to code modules to add additional features. I have just started working with svxlink modules and am working with some of Juan’s test code to make an ORP remote relay module. Still testing and learning with modules, but I hope to eventually build a plugin type framework to make adding modules easier. There is a lot of work to do.

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Aaron, N3MBH]

Hi Bjorn,
If it is not in the svxlink manual then I would probably say no. I don’t claim to be an svxlink expert. That is part of the reason for the project is to improve configurability. No it probalby won’t utilize every single feature of svxlink, but I will try to add gui support for things that are important and can be implemented in a sensible way.

P.S. See my other post about about where to make your changes.

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Aaron, N3MBH]

That’s correct. Just so you understand how ORP works, it is a custom GUI on top of svxlink that builds config files for you. When you edit setting in the web gui, they get saved into a sqlite database. When a change is made a memcache flag is set so the gui prompts your to rebuild and restart. So nothing physically changes with the svxlink config until you take this step.

Upon Clicking the Rebuild and Restart button, this will run svxlink_update.php which is responsible for reading the setting out of the database and writing them to the svxlink.conf file you say gets over written, so that is why. You will want to make you changes within the svxlink_update.php file. It also includes some sub files to help break it up and make it a little more readable. So you should know php before jumping into this file. There are a lot of setting that are hard coded into this file. In essence it is basically quote the whole file a a bunch of substrings then combining those and writing it out to various files. You can fine this file in the web directory: /var/www/openrepeater/functions/svxlink_update.php

Again changed you don’t want to be overwritten should be hard coded into this file.

73,
Aaron – N3MBH / WRFV871

OpenRepeater is offered free of charge. Find out how you can support us.

[Author]

Posts