[Aaron, N3MBH]

So you are saying that your RICK is operating as a bidirectional controller? ORP and the SVXLink standard repeater logic for that matter, operates as a as one directional controller. Maybe I will see if Dan chimes in as well, but I am thinking for your V/U Crossband (bi-directional) you would need two simplex logics for each radio, one for VHF and one for UHF, and them have them linked together persistently. Then for your “Link Radio” you would need to have another link defined that can join all three when requested by DTMF.

Check out the svxlink configuration manual (http://www.svxlink.org/doc/man/man5/svxlink.conf.5.html) and search for the “Logic Linking” section. In ORP 2.1.2 this is not available. but in 2.2.0/3.0 we are improving the linking. We will be calling it link groups, but unfortunately for the time being, the ORP code structure only allows for one of our link groups being defined per port or svxlink logic section. I think you can add more than one link to a logic in straight SVXLink. You would either need to custom the PHP a good bit to output these results or you might be better going to straight SVXLink for now.

If you wanted to build a straight SVXLink system on a Pi, you should be able to use our build scripts, there should be an option in there to build an SVXLink only setup without the ORP UI on top. You loose the ORP UI, but you gain some flexibility in the ability to implement more unique SVXLink configurations. Just some thoughts.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

That is main repo for the web UI. There is also the scripts repo. Note that what is considered stabled code in set as the master branch. There is currently branches for 2.2.x and 3.0.x that are in development. You’d have to manually switch to those branches. You can certainly build a 2.2.x build using the associated script repo. It is more of development code and will likely not be released as a downloadable IMG file. I would avoid 3.0.x as that is still unusable at this point as there is a lot of work going on with it right now, but you will see that it is getting active commits to get it ready.

None of the these branches have code it it yet for the QSO recorder functions I mentioned. That is a local experiment only as a proof of concept.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hello Alexandros,
I cannot say that I fully understand your questions. Can I assume that you are using a stock IMG of 2.1.2 that only supports 1 repeater (full duplex port) and any additional port is a linked simplex port…is that correct? So you’d have one repeater port (2 radios…RX & TX), then a third simplex radio?

If you are having issues with DTMF decode on your simplex port, that might be because by default (in 2.1.2) the simplex ports are stripped down to function more as a link port. Modules are currently not loaded in the simplex logics (links). It shouldn’t take too much work in PHP to enable this, but it would share the same module as the primary port, so DTMF codes would be the same.

If your needs are very specific, it could suit you to do a SVXLink only build. If you need the module to behave entirely different on the additional port, you’d likely have to clone the module files, rename them to a new name and edit the module code to change the namespaces to match. Then call the cloned module from your second port.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

There is no distribution IMG of 2.2.0. As mentioned it needs built via a script on top of a fresh OS. The actual build script is located here: https://github.com/openrepeater/scripts/tree/2.2.x

The read me is pretty detailed and the commands are pretty much copy and paste.

I’m currently working on starting to merge 3.0 UI design code with base 2.2.x code so I can get to a point of being able to have others test the code.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hi Jason,
I actually flirted with this feature a month or two ago. I got it to work to some degree but didn’t fully test it yet, more of a proof of concept. You’d need to make some hard coded PHP arrays within the /var/www/openrepeater/includes/classes/SVXLink.php class file. I You’d have to generated code that writes out a new section for the recorder, then add the PHP array element to the logic section that you’d want to call it. You also need to make sure that SVXLink has write access to the folder.

I even create a crude page to view the list of the folder and play them back within a browser. Nothing I have committed yet. I’d have to boot up a different stick to see the files.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Yes the site does currently block URLs except from admins.

The branch for the script would be under 2.2.x

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

By default 2.1.2 and I think back to maybe 2.0.0, port 1 functions as a full duplex repeater, any additional ports are setup as simplex ports with reduced ID and all link together.

In 2.2.0, I’ve reworked the back end to add more support for the SVXLink linking feature. The new linking features are going to be referred to in ORP as link groups. You can have up to link groups and put each port into one of those four groups. Yes, four is to deal with an large amount of ports. ICS has been working on an 8 port controller. The links can be set as persistent or on demand. In 2.2.0, some of that has to be configured through the temporary dev_ui and PHP arrays as mentioned above to get the proper settings into the database that the backend expects. When 3.0 is release it will expose these setting in a more friendly way in the UI.

Aside from EchoLink (which is Ham), we do have a beta module for FRN (Free Radio Network). Some of the work we are doing on 3.0 is to make way to add different port types in the future like VOIP ports using SVXReflector. This is not tied into a Ham only network, so it should be a good candidate for GMRS users.

I went ahead and got my GMRS license last year. So once things settle down, I hope to do some more configuration options with ORP and GMRS applications.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Jason,
I think you are on the correct path. Yes you would have to fire /var/www/openrepeater/functions/svxlink_update.php or a copy of it to update the config files. That is what the button triggers. While you should be able to run PHP from the cli or a bash script, note that the svxlink_update.php does have a session wrapper on it to check to see if the user is actively logged in. This might cause issues from the cli. You’d have to bypass it or make a copy with the bypass. That PHP fires off some PHP class files that do the majority of the work.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

No problem and it is coming. Just keep an eye out for version 3 of ORP as it will be accessible within the new UI.

If you are comfortable with Linux and RPI, then you would likely have no issues building a 2.2.0 image using our script on GitHub. To implement the USB RIM device, it is just a matter of editing a PHP file (which some example configs exist) and running that file to inject the proper settings into the DB. This is a run once operation. The 3.0 UI will just make this more accessible and straight forward.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hello Klaus,
This function is not built into ORP just yet, but it is on my todo list after getting 3.0 released. From the config side to write out the files it would currently involve hard coding some PHP to write the config. 2.2.0, already contains part of the linking functionality via the temporary dev_ui. The [ReflectorLogic] sections are not there yet. I believe that there may be some custom compiling of SVXLink or SvxReflector, but I am not completely certain as I’ve not really had a chance to dig into this yet. It’s on my to do list, so if you make any headway, or want to help get it built into ORP, please let me know. Thanks.

73,
Aaron – N3MBH / WRFV871

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

[Author]

Posts