[Aaron, N3MBH]

I shot you an email that you can reply to.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Bryan,
I am not sure how much assistance I can be. I cannot say that I’ve had any experience setting up echolink with a proxy. The proxy settings in the module are an extension of those settings found in SVXLink and were added at the request of another user. It was a while ago, but I seem to recall that it worked in his case and it got committed into the next release.

If you want to post the configuration file that ORP outputs, I will try to take a look at it and see if I see anything out of place. I don’t have my test rig setup at the moment, but if I recall correctly the config file gets saved out to /etc/svxlink/svxlink.d/ModuleEchoLink.conf. If it’s the ORP file it should have a OpenRepeater header at the top of the file. Be sure to obfuscate any sensitive info like your password.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

It is achievable in the current development build (2.2.0) but that is not available publicly as a downloadable image. You’d have to do a custom build from script to get it up and running. This code will likely not be publicly released, but rather absorbed into version 3.0 when the new UI design is completed. If you are adventurous and good with linux then you can use the script to do a 2.2.0 build.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

I have not been able to test the selective call function yet. There are a number of SVXLink features that have yet to be incorporated into ORP. And…I am trying to incorporate them as they make sense.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Perhaps but it has not been tested yet with older release.

• within the module (/var/www/openrepeater/modules/MetarInfo) rename your settings.php to back it up.
• Create a new settings.php file in it’s place with the same permissions
• Copy the contents of the trunk version of the settings.php file from GitHub into this file (https://github.com/OpenRepeater/MODULE_Metar_Info/blob/master/settings.php). This will add a drop down to select the server that is not in the released version 0.1
• On line 66 of that file change the https to http.
• Go to the Metar Module settings page. You shouldn’t need to change anything, just hit Submit. This should write the non-https URL into the database settings.
• Rebuild & Restart Repeater to right the new config files.

Let me know if that works. I’d be curious to know.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hello Edward,
Yes, this module is still in early beta. I am just now starting to get some other testers involved to try it. In working with another tester that seems to be the consensus right now, but we have not fully verified this. Version 2.1.2 of ORP is built with the 17.12.2 release of SVXLink.

While the METAR module is a native SVXLINK module with an ORP wrapper, it appears at this point that it will require the 19.09.1 release of SVXLink or newer to work. As of this post 19.09.1 is the latest release beside the development trunk. We have a development branch of ORP currently versioned as 2.2.0. This is what I build the module under. This is not available as a downloadable IMG file an needs built with a script.

I am talking with another tester that is working to make this build and test the METAR module under 2.2.0 to validate my theory. He was reporting the same issues on 2.1.1 and 2.1.2. This should resolve the https issues the module is having issues with. I suspect it should work after that, but there is another minor issue in the SVXLink code that will cause the report to play twice. Not a horrible issue, but I don’t expect that to be resolved until SVXLink drops another release from their trunk code.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

I will certainly keep it on the radar to look into for future features. I haven’t received a lot of requests for paging, so that might be a bit further down the list to test. I have my hands full with a number of other features and updates currently being worked on.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hello Dale,
Sorry for the delayed response. The ICS Controllers Pi-Repeater-2x only support 2 ports. I know Dan has been developing a newer controller platform that will support more ports. I don’t know if he has a release date on this yet and we would need to test the hardware to make sure it is fully supported. You could probably send them a message and inquire.

You could use the 2X and also some USB hidraw devices like the DMK URI or the RIM-Lite to come up with 4 ports. As of this post, this is currently under development and testing. It probably won’t be fully available until the new UI is done in version 3.0. I have had good success in the “lab” with a mix of the ICS hardware and supplemental USB hidraw devices. If you are interested in testing this let me know.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Just to add on to my previous post the SVXLink Card does not have any hardware based pre-emphasis/demphasis settings. I know the ICS interfaces do, so that is why I couldn’t remember. This sounds like more of a function of your radios as mentioned above. It could also be the USB sound cards that you are using with the SVXLink Card.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hello Klaus,
Yes, the metar module I believe is a little more complex than a straight TCL module. I haven’t dug into it too deep, but looking at the SVXLink trunk code there appears to be an additional CPP file with the metar module which I would imaging has the bulk of the code in it and gets compile with SVXLink. So it would be a little more integrated.

The repeating of the airport information twice as mentioned seems to be a know bug, and I’ve see the same thing on my end. I believe I saw mention of this somewhere recently, so it my be corrected in trunk but would need to wait to make it into the next release of svxlink to be utilized by ORP.

73,
Aaron – N3MBH / WRFV871

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

[Author]

Posts