Forum Replies Created
-
AuthorPosts
-
Aaron, N3MBHForum AdministratorEcholink should always be persistent (when activated in modules). You will get a timemout if you are not connecting to outbound nodes, but you will still be listed in echolink directory and inbound stations will activate the module when using your node id. Is that what you are asking?
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorN0FON,
First make sure that alsamixer is recongnized:
which alsamixer
Should give you a response with a path to alsamixer. If you get nothing in response then it is not installed.Secondly, I have seen before where the sound device doesn’t get assigned the anticipated card number and alsa mixer can’t find it?
What is the output of:
aplay -lDepending on the card number returned you may need to use a switch after alsamixer to select the card. What exactly that is I cannot say at the moment, as I’m not at my home office at the moment.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorGregg,
Yes that is correct and something I didn’t really think to include above.Randy,
If you are testings connecting to your own station…say using the EchoLink iPhone app to connect to your OpenRepeater…then yes you do need to have separate node IDs registered with EchoLink. So in my case I used N3MBH on my phone and N3MBH-R on my OpenRepeater. Not sure if that would be your problem or not, but it is certainly work mentioning.73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
-
This reply was modified 6 years ago by
Aaron, N3MBH.
Aaron, N3MBHForum AdministratorGreetings Paulo,
Sorry for the delay in replying…it’s been a busy new year already. You may want to check that your port forwarding is setup correctly. EchoLink requires that your router or firewall allow inbound UDP to ports 5198 and 5199. Echolink has some good information here: http://www.echolink.org/firewall-friendly.htm Not all of it will apply to EchoLink on ORP/SVXLink, but much is the same.Perhaps check out this recent formum topic where I go into a bit more detail: https://openrepeater.com/forums/topic/echolink-port-forwarding
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorGregg,
Sounds like you are making some progress. OK, so you are using a USB cable. I might try when time permits with my FT450D. I have a USB to Serial cable for that. I would guess that the IC-7100 driver is not fully developed and is waiting for someone with the ambition to do so to build it out and debug it.I would start with the TCL files and manually creating your config files first for the SVXLink side of the Module. With that you can simply use “orp_helper svxlink restart” to restart the SVXLink core and load the changes to your config.
Once you start working on the UI side of open repeater and using the build_config.php file to save out config variable, then you will need to make a change in the GUI to invoke the red bar at the top then use the Rebuild & Restart button. That will generate new files from the DB settings or anything you have hard coded in your build_config.php file, then restart SVXLink.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Randy,
The first step is to ensure that your pi has a static IP address on the network. You don’t want your ip address changing randomly otherwise port forwarding will not work. For me, I have a more advanced router that allows me to map a static IP address to my devices based on their network adapters MAC address. I find this the easiest way to assign a static. If your router doesn’t have that feature then you will need to manually configure it. In previous versions of Debian/Raspbian this used to be done in “/etc/network/interfaces” but I pretty sure that has changed in Stretch, but I have not familiarized myself with how to configure that. We have a KB article on this, but it needs to be updated to work with Stretch.Once you have a static set, then you can concentrate on port forwarding. Note that the main ports you need to worry about (5198 and 5199) are incoming so you won’t be able to test internally. You can probably use an external or web based port scanning tool and scan your WAN IP of your router provided by your ISP.
EchoLink requires that your router or firewall allow inbound and outbound UDP to ports 5198 and 5199, and outbound TCP to port 5200. Note the most routers will just open up the requested outbound port (5200 upon request). It is just the inbound ports that you need to configure. You will need to configure the router to “forward” UDP ports 5198 and 5199 to the IP address assigned to your OpenRepeater controller. Note I say forward as opposed to just opening the ports. It needs to know where to send the incoming traffic once it comes in. So Both ports 5198 and 5199 will need to forward to the internal IP address of your ORP controller. They also need to be configured as UDP ports and not TCP ports.
Echolink has some good information here: http://www.echolink.org/firewall-friendly.htm Not all of it will apply to EchoLink on ORP/SVXLink, but much is the same. They mention a site called https://portforward.com that might be able to help you with the specifics of your DSL Router.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorGregg,
Yes I would tend to agree that the command list is extensive, but mileage will vary from rig to rig. There is a command I believe that list the rig models and it think to also shows what development level that the driver is at.Perhaps I can get with you at some point to share ideas on how you are interfacing to your rig via the GPIO, unless you are using a USB to serial cable. I might start to tinker with the HamLib on the Pi myself as time permits.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorAs Dan is describing above, this would be the current setup for two radios. If you happen to be trying to connect this to one radio with the standard repeater logic used for the first port you will get some weird behaviors. Let us know if you intend to use one radio (simplex/half duplex) or two radios (repeater/full duplex). Of course you could run into some desense issues with two radios unless proper separation or RF filtering is used which is an entirely different subject.
As mentioned, I can probably help you customize to use a simplex logic with one radio if required. It’s been on my bucket list for a while if you wish to be a guinea pig.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorRandy,
Sorry for the delayed reply. I moved your response into this forum for ICS stuff which is relatively new. I never subscribed to the forum, so I was not getting email notifications. Dan may have the same issue, not being subscribed. I will check.As for EchoLink, there are some instructions in the EchoLink settings page about opening up some ports on your router. If you’ve use EchoLink on a computer, it should be the same procedure. Without the ports forwarded It will show you as connected to the EchoLink server, but stations won’t be able to connect to your node. The log does show Echolink activity. It will show what server you’ve connected to when you first start up or restart the repeater (SVXLink). It will also show connecting and disconnecting stations in the log.
As for radios…Yes, as of right now it is best to use a duplex setup with the first port (only port in your case). As ORP is in it’s current state the first port is a duplex port and any additional ports are simplex link ports. It’s in the works to improve the UI for more customization in a future release. If you want to use a single radio, then you’d need to be using a Simplex logic instead of the ORP default duplex/repeater logic. It’s possible, but I may need to help you some code modifications in your case until the UI updates are made.
There are some classes in place so it would simply be modifying the /var/www/openrepeater/functions/svxlink_update.php file. It has some loops in check the database and make calls to appropriate classes. Let me know if using a simplex logic (one radio) with the modules (i.e. Echolink) is what you are after. I can probably tell you how to make the modifications to your svxlink_update.php file.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorRandy,
Firstly, I moved your topic into the ICS Controllers forum since it pertains to that hardware.Dan will be best to help you on some of the hardware settings, but I wanted to ask you if you have tried loading the board presets in on the bottom of the interface page? This should set your sound card levels in alsa as well as the GPIOs, and there active hi/low state that ORP needs to see them. There are two active high/low states that you would need to be aware of: 1) would be between the Pi/OS/and your 1X board. This is what the board presets will address. Then you shouldn’t have to worry above any of the advanced settings for the port. 2) would be the active high/low relation between your radio and the 1X board. This should be taken care of in your cabling and the COS switch on the 1X board.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
-
This reply was modified 6 years ago by
-
AuthorPosts
