As Iain has said, there is something else going on. Please paste the full logs from when you ran the install. I can see from the top line of the attached photo another error - "sudo: build-gnuradio: command not found" which indicates there is something else going on earlier in the installation that has failed. Cheers, Matt On 2/10/18 11:01 am, iain macdonnell - N6ML n6ml@dseven.org [op25-dev] wrote:

 

On Mon, Oct 1, 2018 at 5:27 PM n3zra@yahoo.com [op25-dev] <op25-dev@yahoogroups.com> wrote:

...

I am very new to using Ubuntu OS and O op25. I cannot get the system running, my rtl sdr does work on the virtual box but op 25 is not starting.

attached is the error message I am getting. I appreciate the the help.

Unfortunately that "osmosdr source_c creation failure" message masks any exception raised when trying to setup the source, so it could be caused by a variety of issues.

To start, it'd be helpful if you described, in as much detail as possible, all of the steps that you followed to get to this point...

73,

~iain / N6ML

Hi Andy, I run op25 successfully on Ubuntu under VirtualBox as well as on the Raspberry Pi and Pine Rock64 platforms. There are a couple of points that need be observed operating op25 in on Linux in VB that I would be more than happy to share with you. Feel free to PM me if you'd like some assistance to get op25 installed and configured correctly. We could use TeamViewer to provide me remote access to help with your installation. 73, Bill, WA8WG E-Mail: <wllmbecks(*/at/*)gmail.com>

As a cheap project, grab a Raspberry Pi 3B+ - that way it's all standalone. Doesn't cost much, runs Raspbian which is well supported and known by the OP25 community, and it has enough processing power to handle an RTL-SDR quite well. On 7/10/18 6:23 pm, Andrew Hoehn n3zra@yahoo.com [op25-dev] wrote:

 

Thanks for the help, I had a fatal error after that on the windows box it was hosted on, so now I’m back to square one. Once I get everything back up and running again I will try again. 

Sent from my iPhone

On Oct 2, 2018, at 09:14, ikj1234i@yahoo.com <mailto:ikj1234i@yahoo.com> [op25-dev] <op25-dev@yahoogroups.com <mailto:op25-dev@yahoogroups.com>> wrote:

...

 

It would also be good to have you try running the osmocom_fft app - this is separate from OP25 and would help to rule out connectivity problems with the RTL USB device.   Please send all output that it might print out.

73

Max KA1RBI

Andy, Try formatting your rx.py command line as follows. ../rx.py --args ‘rtl’ --gains ‘lna:49’ -f 151.400e6 -S 2500000 -q 0 -T trunk.tsv -U -V 2> stderr.2 Note the formatting of the LNA gain setting for the RTL SDR device and you must either input the frequency in Hz or use the e6 notation to input MHz as you have done. Your sample rate -S 2500000 need not be set so high but should work fine on VirtualBox. This would place too high of a demand on the CPU on the Raspberry Pi where -S 1000000 works well. You may need to adjust the value for -q frequency correction once you can successfully start op25 (rx.py) without errors. Observe the tsbks in the console screen once rx.py starts and adjust the value as needed to get the SDR dialed in to where it begins to decode trunk signaling blocks on the systems control channel. It is normal that the tsbks counter halts as op25 follows a voice trunk but should resume upon return to the control channel frequency. You can also skip the -f 151.400e6 on your rx.py command line if you are using Graham’s boatbod version. Either way, you do need to specify the control channel and alternates in trunk.tsv. Bill, WA8WG From: op25-dev@yahoogroups.com <op25-dev@yahoogroups.com> Sent: Thursday, November 15, 2018 12:09 PM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: error message help Looks like it might be s gain setting for the dongle. What dongle do you have? And can you post the line you are trying to start op25 with?

There's really little impact having "-2" enabled even when there isn't any phase 2 traffic. Additional processing overhead is pretty small as it only tries to match the frame sync id. Conversely, there is considerable benefit to reducing the sample size (-S), especially on lower spec hardware. You only need to have it wide enough to receive one channel (57600 works well on a RPi3, 960000 and 1440000 are good on PCs). The only reason to go bigger is to see "more stuff" on the FFT plot, but it won't make op25 perform significantly better unless your entire trunked system fits within the 2.5Mhz RTL bandwidth allowing you to use center tuning.

Thanks for the advice. I’ll double-check the dependencies and configuration first, especially the virtual environment, as that could explain the conflicts.