[Aaron, N3MBH]

It’s on my todo list.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Sounds good.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Hello Jimmie,
Sounds to me like you might have missed setting up the root user or are not logged in as root. The Raspberry Pi OS comes with the pi user setup and it has sudo privileges. By default, the root user is not enabled. This is part of the Prepare your OS to Install Headless (https://github.com/OpenRepeater/scripts/tree/2.2.x#prepare-your-os-to-install-headless) section in the scripts read me.

In a nutshell:

• You Start with a bare Raspbian OS
• Under the pi user: You then fully setup SSH, the root user, and ssh privileges.
• You then log out as the pi user and login as the root user
• As the root user: you download and run the script.

My theory is if you are are using a keyboard/monitor instead of ssh, you are still logged in as pi and not root. At the end of the Prepare your OS to Install Headless section under Restart SSH, it says to log out as the pi user and back in as root. You should do this, even if you are using a keyboard/monitor. You do not want to be logged into the pi user at all when the script runs or else the script may not be able to delete the pi user. In other words don’t rely on a su (switch user) command. From you keyboard type ‘exit’ and then log back in as root with the password you set at step 7.

If you are getting errors running the ‘cd /root’ that tells me that you are 1) most likely logged in as the pi user. Now the pi user has sudo privileges, so to check this you could type ‘sudo cd /root’ if that works then you likely enabled the root user. Don’t bank on that, as that directly might still exist with the root user disabled. 2) you may have not setup the root user. Best thing to do is to log out and log in as root with the password you should have setup at step 7.

If you can get in there, then you are golden. If you didn’t get past the ‘cd /root’ then that tells me that you haven’t run the script yet. So you can pickup where you left off. Note that if you follow the other steps in the read me prior to this point then you should have SSH and the root user properly setup. You can also log in headless via SSH.

73,
Aaron – N3MBH / WRFV871

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

• This reply was modified 3 years, 8 months ago by Aaron, N3MBH.
• This reply was modified 3 years, 8 months ago by Aaron, N3MBH.

[Aaron, N3MBH]

It is really quite simple. When you image SD card, it creates two partitions. One is FAT32 called boot which you can access on a Windows machine and the other is the primary linux partition where the all the good stuff lies. You cannot see this when mounted on a Windows machine. Raspbian has a special feature when you first burn a card. Once you are done burning the IMG to the card you can remount it on the computer (some programs eject or unmount the drive when burning is completed), then you should see a drive show up called “boot” this is where you save a empty text file called “ssh” with not extension (so not something like ssh.txt). You have to make sure that it doesn’t append .txt or anything else. The file should have no contents. All this is is a means to set a flag. When Raspbian boot from the main linux partition is checks out the boot partition and if it sees this empty file, it will enable some basic form of SSH so that you can access the board headless.

Otherwise, you can certainly skip this step and use the Keyboard and Monitor. Once you follow the steps in the build script, you will fully enable SSH for the root user. Note that the script will also remove the pi user when completed.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

Thanks for your reply Dave. Didn’t think that he may only be seeing the boot (FAT32) partition and not the main Linux partition.

73,
Aaron – N3MBH / WRFV871

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

[Aaron, N3MBH]

2.2.0 will likely not be release at an IMG file for download…it’s more of a transitional version to 3.0. That said, it really isn’t hard to build if you can SSH and know some basic Linux commandline. Each of the Github repos (openrepeater and scripts) have branches. So what you see when you go to one of those branches is the default branch. That gets set to the current stable/public release. You want to change the branches to 2.2.x to see that set of code/commits. To build 2.2.x you just need a fresh copy of Raspbian and to follow the readme for the script. For 2.2.x you would go here: https://github.com/OpenRepeater/scripts/tree/2.2.x

I’m currently working on merging the 2.2.x code base with the new 3.0 UI design. That will be the next major “downloadable” release. We are also working on an interim release that will be version 2.1.3, that should be available soon. It should be functionally identical to 2.1.2, but the main difference is it will have an updated kernel to support the Raspberry Pi 4 8GB.

Yeah, I got GMRS also partially because of my wife/son who really have no interest in getting their Ham license. This will cover them when we need to use radios for whatever activities. Also figured it would be good to tinker around with ORP at some point for GMRS repeater setups as well. I believe there are already a number of users that have used it for that.

73,
Aaron – N3MBH / WRFV871

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

[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.

[Author]

Posts