Forum Replies Created
-
AuthorPosts
-
Aaron, N3MBHForum Administrator
OK, not home at the moment but I’m trying to remember if the SVXLink card has any hardware pre-emphasis/demphasis options.
Also on the GM350s you probably have some audio options in the RSS software as well. You may also wish to experiment with the pinout on the 16 pin connector on the radios. So on your TX radio maybe try pin 5 instead of pin 2 for audio out or vice versa.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
- This reply was modified 4 years, 12 months ago by Aaron, N3MBH.
Aaron, N3MBHForum AdministratorI now have a basic ORP version of this module packaged up for testing. Seems to work well on my end.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorRolf,
No problem, use what works for you. I have been working to add support for Hidraw devices as interface hardware in an upcoming version. I expect this to available in the UI most likely in version 3.0. I currently have this functionality working on the back end in a development version, but the UI is not built out yet. I’ve been working on that on the side as well.I currently have test Hidraw hardware that I’ve been developing with and there will be support added for the DMK Engineering URI as well as the Repeater Builder RIM Lite off the bat. This should also work with other CM108/CM119 home brewed hardware as well provided that it is pulling COS and PTT from supported pins.
I’ve also been starting to flirt with Allstar a little as time allows. That will likely have to be a parallel install of Asterisk and apt-rpt and audio routed via software between asterisk and svxlink. It will be a significant amount of coding. Last I tried to install Allstar on the same system I was unable do do the build as the package didn’t support running on Buster. I will get back to it eventually, but I’m currently working on a new UI design to support future updates.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorKlaus,
I don’t think that your main problem will be with trunk but with the module it’s self and how it is implemented within ORP. We would need to build the Metar Information Module into an ORP Module like we’ve been doing with some other modules. This is basically wrapping up the SVXLink module files, any sound files, into a specific directory structure along with some custom ORP files to make the module “installable” withing ORP. Check out some of our other modules in our github (github.com/openrepeater). ORP has a specific way that it generates configuration files and this would probably be the simplest and most future proof way to implement it without hacking ORP. I haven’t dipped my toes into the Metar module in SVXLink, but I can probably help assist with that if you’d like to help test it.I don’t know if the Metar Module requires any of the functionality in SVXLink 19.x or not. If you want to do a build that includes that version of SVXLink, I would suggest using the 2.2.x branch of the build script (https://github.com/OpenRepeater/scripts/tree/2.2.x). This uses the 19.x release version of SVXLink for the express build. There are advanced build options in the script, but that has not been recently tested with trunk. We ususally go of release versions for stability reasons. Be sure to follow the scripts readme file.
Hope that helps.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Klaus,
That is strange that both services are not starting. I don’t see any indication in the log provide mentioning anything failures with the nginx service, but that doesn’t mean much. If you say it’s not running then I will take your word for it.My guess would be either something got corrupted at the system level on your SD card, or if you happened to run system updates which you would have had to do via SSH, then that could have broken something.
I would say your best bet it to start with fresh build. I would advise using a different card for 2 reasons: 1) if the other card is being flakey, then you want have any repeat issues and 2) so you have the option to mount the defective card and pull files from it.
If you do your new build as the same version you should be able to copy over your openrepeater.db file to the new install. Also if you happen to have any custom files like courtesy tones, identifications, etc, you could manually copy those over as well.
If you happened to use the backup feature and download an offline file before it corrupted, you can use that to restore on the new build a little more automated. That will package up the important table in the database as well as all the sound files uploaded into the UI, and alsamixer settings.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHi Richard,
Yes that would probably be the desired result under normal operation. That way if the Pi locked up or power was lost then restored, then it would keep trying to get the pi to boot. It is a stand alone circuit so it has no really way to communicate with the OS. I haven’t messed with the Watchdogs at all myself.Looking at the Schematic, you’d have to set JP12 to enable it. If you desired to shut it down you could pull the JP12 or wire in a toggle switch to JP12.
There is also a watchdog built into the Pi itself…which I have also not messed with. You can find a discussion of it here: https://www.raspberrypi.org/forums/viewtopic.php?t=210974
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorSo sounds like you got it working. I will try to come back to this for a future release. I am hoping to add a line to run a board specific bash script for certain boards. This would be in the board presets definitions. If a script is referenced then it would run that too. Still considering how to implement this, but I have another piece of hardware that will likely require something like this.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Richard,
The watchdog feature built into the SVXLink card does not currently have built-in support in the ORP images, it would be a feature you would need to manually configure.They have a starter guide here: http://svxcard.f5uii.net/doku.php?id=en:configuration_watchdog
That should help you get started. Up to this point we have not really had any requests for the feature in ORP. Just would need some folks to help test and come up with a solution. I’ve been considering adding a field to the board presets table that could reference a bash script to fire off when a specific preset is loaded. This might be able to handle the automation of setting up something board specific like the watchdog on the SVXLink Card. That script would need to probably write out a python file, set permissions on the file and call it on boot up as well as set the referenced GPIO pins.
Hope that helps.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorThis link might help:
https://groups.io/g/svxlink/topic/echolink_login_message/37955829?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,37955829
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorAm I correct in assuming the file that says: “You have connected to an OpenRepeater Echolink node. For more information, please visit openrepeater.com”
If that is the case, the easiest thing to do is to rename the audio file and replace it with something else. You can just do some command line renaming and copying.
First, Backup the greeting file by renaming it:
mv /usr/share/svxlink/sounds/en_US/EchoLink/greeting.wav /usr/share/svxlink/sounds/en_US/EchoLink/greetingORIG.wav
Then, copy the “connected” file by renaming it:
cp /usr/share/svxlink/sounds/en_US/EchoLink/connected.wav /usr/share/svxlink/sounds/en_US/EchoLink/greeting.wav
Now instead of the message above it will just say “connected” from the remote node.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
-
AuthorPosts