Forum Replies Created
-
AuthorPosts
-
Aaron, N3MBHForum AdministratorHello James,
There isn’t really a setting in alsamixer for this. I would just make sure that your outputs and inputs are set first to a reasonably level in software (alsamixer) so you get better dynamic range, then adjust your pots on the SVXLink card.Outside of that, I would suspect 1 of 2 things. Either you are getting RF introduced back into the input audio via your sound card or cabling, or you just have cheap sound cards. I have some sound cards that introduce hissing. If you can try to test input and output on a computer and see if the hissing is present. For the first item, try running into a dummy load to see if you can attenuate your TX signal enough as to not effect the RX side.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Maarten,
I don’t think the EchoLink was really intended to function as a persistent link between repeaters. There are two timeout values associated with the EchoLink Module that I am aware of. The first is just the general module time out that is settable in the EchoLink settings. There is a second timeout setting that is hard coded at 5 minutes when the EchoLink configuration file is written out.Even if you change both of these, it is also going to be dependent upon if the other repeater that you connect into is going to time you out as well. If you want, you can try to temporarily edit the /etc/svxlink/svxlink.d/ModuleEchoLink.conf file and comment out both the TIMEOUT and LINK_IDLE_TIMEOUT values (or set them to zero), then restart the SVXLink service using the following command as root: “orp_helper svxlink restart”. You won’t be able to make any modifications within the Web UI otherwise they will overwrite your configuration changes.
You can try this and see if you can keep your link persistent or if the other EchoLink node boots you after a certain time period. If that works, I can give you further instructions on how to modify your PHP code for now to allow for the customization. Then we can consider improvements in future releases.
Ultimately, SVXLink, the core of OpenRepeater, has another feature called SVXServer that allows for IP linking between repeater. Both repeater would need to be running SVXLink based controllers. We have been talking about implementing this feature in a future release of ORP.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Brett,
Yes the code has change for V2.0.0 that generates the svxlink.conf file. If you you look at the svxlink_update.php file, which is where you were probably making your modifications before. You will notice that it is making some calls to some new PHP classes. The first port it will call the repeater class and any additional it will use the simplex logic and add those to a link logic. You should be able to customize the svxlink_update.php and get it to call what you want, but I would need to understand what you are doing first. The ORP_SimplexLogic_Port1 logics are custom logics created by the class. They are copies of the original SimplexLogic.tcl files with updated namespaces and some other tweaks.You may also be able to use the experimental “advanced mode” introduced in 2.0.0 for direct svxlink.conf editing. I would set it up as close as you can with the options that you want before switching to advanced mode. Again this is undocumented and experimental mode. To switch to advanced mode, log in, then go to https://xxx.xxx.xxx.xxx/advanced.php (this is a hidden page). You should be prompted with options to switch. Once switched you can directly edit your svxlink.conf and gpio.conf files. Here you will probably want to switch back to the standard logic section naming of SimplexLogic.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorVery good and thanks for pointing out that the SOX package is missing on the 1.1.0 image. Perhaps that will be of help to others until the 2.x.x version is released.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Ronualdo,
I recall a couple other people have had that problem as well with 1.1.0. Version 2.0.0 is on the horizon. I mostly have the build script done and successfully built a full install last night. Now the only thing left to do is some bug squashing.In the new 2.0.0 version (ionosphere), I have completely rewritten the audio functions into a class. While doing that I cannot remember what the problem was with the 1.1.0 setup. Whether is was a bug in the php code or the permissions not getting set correctly on the upload folder.
If you want to be an early tester for 2.0.0, let me know. In the mean time, as long as you can select the existing sounds and they play, a work around would be to upload new sounds via SFTP to the appropriate folder under “/var/lib/openrepeater/sounds/”. You will just need to make sure that you save them into the very specific WAV format that SVXLink requires to play them back otherwise they won’t play. You can open one of the existing files in an audio editor and match the same formatting or you can convert is from the command line using the SOX utility:
sox "/path/to/original.wav" -r16000 -b16 -esigned-integer -c1 "/path/to/converted.wav"
Once you do that is should show up in your list of files to be selected.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorUI code is available on GitHub repo, Ionosphere is the development branch.
https://github.com/OpenRepeater/openrepeater/tree/ionosphereStill working on build scripts to create new system with Debian/Raspbian Stretch and latest version of SVXLink.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorJust to retouch on this issue…I had not encountered this myself until last week. I was working on a development image on a small card. I downloaded some packages and filled up the allowed space. It seams that once the card is full ORP will boot, but can only read but not write to the database or the web server log. THIS WILL PREVENT LOGIN.
If you have a good sized card, be sure to expend the installation to fill the card to give you more space as the initial partition when first imaged is quite small.
See this KB article: https://openrepeater.com/knowledgebase/topic/expanding-the-file-system
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorThanks Brett for your support. With you post here, it definitely adds it to the list of feature requests when we revisit in the future. Right now I am working on frying some bigger fish for the next release.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Ronualdo,
You should be using version 1.1.0 which is the publicly available version at the time of this post. The simplest thing would be to make the modification in the the PHP file that writes out the configurations: /var/www/openrepeater/functions/svxlink_update.phpThere is a knowledge base articles located here https://openrepeater.com/knowledgebase/topic/custom-svxlink-configuration to get you started.
You will see that down around lines 189-212 is the code that builds the echolink config. ID, TIMEOUT, SERVERS, MAX_QSOS, MAX_CONNECTIONS, LINK_IDLE_TIMEOUT, and USE_GSM_ONLY are currently hard coded values. You may change these to whatever you want in this file and they will get written out to the config file as such. After you make changes, just be sure to change some value in the UI so that you get prompted to rebuild the config file. This is what executes the PHP.
To add them into the UI will take a bit more work, especially if you don’t plan to change them much. You will need to make modifications to the database as well as the front end PHP. Also in the next upcoming version the echolink will be grouped under a new module section and options will be saved into a serialized array for each module. For that reason I wouldn’t modify the DB structure just yet.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHi Brett,
That has certainly been a consideration, but is a bit farther down the list. On consideration is there are a number of displays on the market, so trying to support all of them or even a few will be a considerable bit of work. It may not be an out of the box solution built into to ORP or one that would need to be added and customized by each users needs. There have been bits and pieces worked on.I know Dan KG7PAR has messed with the displays with an external script to what the GPIOS for COS and PTT status on multiple ports. As for watching what echolink nodes are connecting, the core SVXLink program doesn’t currently have that capability built in for a separate log file. Any of those connections get logged into the main log file. I have simple PHP script/page that I was experimenting with that reads in the main log file and GREPS it for just the echolink connections/disconnections. It is still kind of crude and experimental. Right now it would have to be accessed from a web browser, but the same logic could be copied over into a python script that would provide data to a display.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
-
AuthorPosts
