[Aaron, N3MBH]

Mario,
Sorry this post was overlooked. But we recently discovered this bug and it seems to be in the source code for SVXLink. We have a patch for it in the upcoming 2.1.0 build script. If you wish to patch this in 2.0.0 you will need to edit your ‘/usr/share/svxlink/events.d/RepeaterLogic.tcl’ to override the unneeded IDs that are occurring every 2-3 minutes as described.

You will need to find the ‘proc repeater_down’ function and comment out everything between the { } brackets for that function. Follow the indentation. The comment character in TCL is #. Once you have done that, save the file and go back to the GUI and make a minor change to invoke the rebuild and restart to create a new logic file which is based of the RepeaterLogic.tcl file you just edited. That file is used as a template.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Randy,
Am I correct in guessing that you are using version 2.0.0? I am unclear what you are changing as far as “repeater” to “simplex”. Are you trying to do this within the “/var/www/openrepeater/includes/classes/SVXLink.php” file? If so I don’t think you will get the results that you desire. The logic there is looking towards a database. If programming is not your thing, but you have reasonable command line experience, then you may be better off building a 2.1.0 image using the build script on a fresh install of Raspbian Lite. 2.1.0 is not officially released as of this posting, but it should be coming soon. We were working on debugging things.

2.1.0 has a simplex mode in the GUI which you can enable along with the echolink module to create a simplex node. I would recommend keeping what you have and start with a fresh SD card. Or if you can hang in there, wait for the 2.1.0 release.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

I’ve sent you a direct email with instructions.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Greetings Wolfgang,
Dan at ICS has sent me your video that you’ve shared with him. He said he was able to replicate this on the 2.0.0 image. We will see if the same issue is replicatable on the upcoming 2.1.0 image.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hello Jack,
Let me see if Dan can make some comment on here. Alsa mixer settings should stick…unless there is something else going on.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Of course I believe modules are disabled on the link ports by default in 2.0.0.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

You could try loading the 2X board profile, then after it is loaded flip the GPIO pin values and the audio channels (i.e. left & right).

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Randy,
I address the simplex question you are asking here: https://openrepeater.com/forums/topic/custom-voice-id-files/#post-2763

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Randy,
The ports on the 2X are physically identical. The function of the ports is more defined by the logic configuration in software for the ports. The aforementioned 1st port duplex / additional ports simplex was just the first step in supporting additional ports and was determined to be the most common approach. It takes a good bit of work to make a UI that is flexible for different configurations. We are working on some interim options that would offer some other configurations until we do some UI redesign. 2.1.0 should be introducing a simplex node for port 1 where you could wire it up to one radio and use that in combination with the Echolink module to create a simple Echolink node.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hello Jack,
I would assume you are referring to the knowledge base article “Custom SVXLink Configuration”. If so that is a bit out of date and needs to be rewritten/updated. The principles are the same, but in 2.0.0 things are in different locations than are mentioned in the KB article.

For testing purposes, you can try stuff in the svxlink.conf file, but you need to be careful not to overwrite it while testing. But yes, items should be modified in the PHP that writes the configs. Since writing that article, much of this has been converted into PHP classes. Most of what you are looking for should be in the “/var/www/openrepeater/includes/classes/SVXLink.php” file. These files only have what is being used, so you’d need to add in extra svxlink variable if required or find the ones you wish to change. This class is formatted a little different than previously. It builds a multi-dimensional associative PHP array…which later gets parsed into the INI format that SVXLink expects. You can still find the relative sections and the key/value pairs, but you just need to format as a PHP array.

The upcoming version of ORP will be adding a backup/restore feature, which will backup and restore the alsamixer settings.

73,
Aaron – N3MBH / WRFV871

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

• This reply was modified 5 years, 8 months ago by Aaron, N3MBH.

[Author]

Posts