[Aaron, N3MBH]

This one looks weird. It shouldn’t be loading “SimplexLogic” at all. That’s an indication it is loading the wrong config file. Check the recommendations I just posted in your other topic regarding port settings.

Also, if you are trying to start/stop svxlink via SSH, make sure you are using “service svxlink stop” and “service svxlink start”. Just typing “svxlink” will not work as expected and give you the above results. OpenRepeater runs svxlink as a service and not as cli.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Milan,
I checked with Richard earlier tonight and he is running Beta 3 with no issues like this. Looking at your code my hunch is that the sound cards under ports is configured incorrectly. That may partially be my fault for not documenting it very clearly. I just updated the Getting Starting Guide with a little more detail.

Here is an excerpt:

Before the repeater will be operational you will need to set the following:

• Go to the “Repeater” settings menu, set your Callsign and click “Update”.
• Go to the “TX/RX Ports” menu, set your TX and RX port settings and click “Update”. Sample Settings:
  • RX Mode: COS
  • RX GPIO Pin: 22
  • RX Audio Device: alsa:plughw:1
  • RX Audio Channel: 0
  • TX GPIO Pin: 27
  • TX Audio Device: alsa:plughw:1
  • TX Audio Channel: 1
• At the top of the screen click the “Rebuild Configs & Restart SVXLink” button.
• Restart the system. This is necessary to initiate the GPIO pins you just set with the OS.

Your settings may vary some. Give this a try and let me know if this helps.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Joe,
I checked with Richard earlier tonight and he is running Beta 3 with no issues like this. Looking at your code my hunch is that the sound cards under ports is configured incorrectly. That may partially be my fault for not documenting it very clearly. I just updated the Getting Starting Guide with a little more detail.

Here is an excerpt:

Before the repeater will be operational you will need to set the following:

• Go to the “Repeater” settings menu, set your Callsign and click “Update”.
• Go to the “TX/RX Ports” menu, set your TX and RX port settings and click “Update”. Sample Settings:
  • RX Mode: COS
  • RX GPIO Pin: 22
  • RX Audio Device: alsa:plughw:1
  • RX Audio Channel: 0
  • TX GPIO Pin: 27
  • TX Audio Device: alsa:plughw:1
  • TX Audio Channel: 1
• At the top of the screen click the “Rebuild Configs & Restart SVXLink” button.
• Restart the system. This is necessary to initiate the GPIO pins you just set with the OS.

Your settings may vary some. Give this a try and let me know if this helps.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hello Milan,
Welcome to the forums. The errors that you are getting looks like it might be related to your USB sound card. First make sure that card is showing up using “lsusb” and “aplay -l”. Also check that you audio ports are set correctly in the PORTS tab in the web interface. If they are not you’d probably get an error like this. “RepeaterLogic” is part of the SVXLink core system. It is looking to RX and TX sections in the config file and if they have errors then it cannot start. So it is a domino effect. You get rid of the audio card issue, then everything else will likely resolve also. Good luck and let us know how it goes.

73,
Aaron

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hey Joe,
You’re running on a RPI2 right? What image are you running on? Richard has a Beta 2 image up that fixed some stuff on the RPI. I have had success with CM-108 cards. as well as another generic USB sound card. We are working on a hardware design that will incorporate the sound card into the interface board and accessed over I2C instead of USB.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Eirik,
Thanks for the comment. We feel there is a niche for an open source repeater controller as there really isn’t anything else like it. Being open source gives us many advantages: it allows a broader range of hams to get involve in its development and improvement, better community, and a greater long term prospect in a cost conscious vertical market.

We’re still getting things rolling, but we have some exciting update coming up including software and hardware. Stay tuned for more.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Excellent Nils, glad you got it up and working! Looks like a great setup you have and your PDF is nicely documented. Looking at your schematic of your interface and other notes about config, it looks like you are using the software vox. Your radio appears to have a COS line since you have a carrier LED. If that comes on when it receives an incoming signal, then with a little extra circuitry (optocoupler and a resister) you can tie that into a GPIO pin on the PI for more reliability. We don’t have that very well documented at the moment, but we hope to make some basic schematics here soon to work towards an interface board.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Nils H, Thanks for your input on the Beta. Just a couple comments.

#1 – As you have stated, others are aware of the PW issue, this only affects the RPI2 and C1. We plan to address this on the next build. For the time being, I have entered what the PWs are for the board in the Getting Started guide.

#4 – Yes every situation might be a little different especially when folks are bringing their own hardware to the table. We plan to add script that reads in the available audio devices and channels to populate a dropdown to facilitate easier detection and selection for ports.

#5 – Right now the CTCSS is on the main settings page and is not fully implemented. CTCSS is support in the core but has not been tested for reliability. I am thinking of moving the CTCSS into the ports section. This will allow different tones/settings to be selected for different ports. The ports section is still under construction an was recently added to make provision for…well more ports.

#6 GPIO will vary from device to device. One thought I have had when we design our own hardware is to include an eprom that can be read when the board it plugged in to auto set this if it is present.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Thanks for the ideas. We are considering many things, but we want to build a solid base first. Incorporating other VoIP services like Allstar or Dstar are considerations, but we will also have to make sure there are no licensing conflicts. Some of these systems are proprietary.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

OK. All that should be achievable with properly routed ports for SSH and HTTP. Weaved should make it much simpler. We plan to take a look into Weaved and do some tests with it.

73,
Aaron – N3MBH / WRFV871

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

[Author]

Posts