August 2017 - op25-dev - lists.osmocom.org

A couple of patches [1 Attachment]
by John Ackermann N8UR jra＠febo.com [op25-dev] 15 Oct '17

15 Oct '17

Attached is a patch file that updates Max's terminal.py and trunking.py in a few ways: 1. terminal.py reads the window size at startup and adjusts the curses settings accordingly. If you set xterm or equivalent to more rows (I'm using 38), you can handle sites with more than 20 frequencies without crashing. This is the patch I posted a week or so ago. (Max, I think your idea of making the main window two columns is still a good one, and the space that frees up could be used to display other interesting info. I don't think I'll have the time to learn how to implement that, though.) 2. terminal.py now displays an info line at the bottom of the screen showing the keyboard commands that are available. I also added a blank line or two to make the display look (IMHO) a bit cleaner. 3. If you set -v to 5 or higher, every frequency or talkgroup command is output on stderr (this will generate a lot of output on a busy system!). If you want to generate a list of every unique frequency used by the system, this will produce it from the stderr.2 file: grep freq: stderr.2 | cut -d" " -f3 | sort | uniq or to get all the unique talkgroups: greg freq: stderr.2 | cut -d" " -f5 | sort | uniq Max, this was actually a bit less trivial than first thought. The code is easy, but where to put it wasn't. Your suggestion about the end of update_state() led to only one update per second, and lost many freq/talkgroup set commands. I think I found a spot that doesn't miss any. Lots of output, but lets you build a comprehensive tgid list. 4. The stderr output of "set trunk_cc..." was not all that useful, so it's now set to appear only when the -v level is set to 6 or greater. (Behavior of -v 10 includes the above but is otherwise unchanged.) 5. I cleaned up all the logging/status/debug outputs in trunking.py to use "sys.stderr.write()" rather than "print". That will stop them from showing up in the terminal screen. While I was at it, I also added newlines to the end of all output and did some other cleanup. Hope this is useful. 73, John

2 1

Raspbian Jessie Stretch Lite
by wa8wg＠centurytel.net [op25-dev] 25 Sep '17

25 Sep '17

I attempted to built the MAX branch of OP25 on the August release of Raspbian Jessie Stretch Lite but was unable to compile the code resulting in the following error during make. [ 52%] Building CXX object op25/gr-op25_repeater/lib/imbe_vocoder/CMakeFiles/imbe_vocoder.dir/pitch_est.cc.o /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘32970’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] }; ^ /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘33226’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘33482’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘33482’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘33738’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘33994’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘34250’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘34506’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘34506’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘34762’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘35018’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘35274’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘35530’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘35530’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘35786’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘36042’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘36298’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘36554’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘36554’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘36810’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘37066’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘37322’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘37578’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘37578’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘37834’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘38090’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘38346’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘38602’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘38602’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘38858’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘39114’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘39370’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] /home/pi/op25/op25/gr-op25_repeater/lib/imbe_vocoder/pitch_est.cc:60:1: error: narrowing conversion of ‘39626’ from ‘int’ to ‘Word16 {aka short int}’ inside { } [-Wnarrowing] op25/gr-op25_repeater/lib/imbe_vocoder/CMakeFiles/imbe_vocoder.dir/build.make:326: recipe for target 'op25/gr-op25_repeater/lib/imbe_vocoder/CMakeFiles/imbe_vocoder.dir/pitch_est.cc.o' failed make[2]: *** [op25/gr-op25_repeater/lib/imbe_vocoder/CMakeFiles/imbe_vocoder.dir/pitch_est.cc.o] Error 1 CMakeFiles/Makefile2:737: recipe for target 'op25/gr-op25_repeater/lib/imbe_vocoder/CMakeFiles/imbe_vocoder.dir/all' failed make[1]: *** [op25/gr-op25_repeater/lib/imbe_vocoder/CMakeFiles/imbe_vocoder.dir/all] Error 2 Makefile:127: recipe for target 'all' failed make: *** [all] Error 2 Any ideas on how to patch Raspbian Jessie Stretch Lite to correct the Makefile recipe error? Thank you, Bill, WA8WG

4 9

OP25 and Wireshark
by James K4JK k4jk.james＠gmail.com [op25-dev] 25 Sep '17

25 Sep '17

Hi All, I'm looking for hints as to how to get P25 frames to decode properly using rx.py and wireshark. I'm using the max branch of OP25 on Debian 8. I'm trying to monitor a phase 2 system. I have compiled wireshark 1.8.6, with the OP25 patches and have it running on Ubuntu 14.04 on another machine. I can see P25 frames in wireshark, they show up but I have very strange information in them. Lots of TGIDs set to 0, etc. There are also very few if any LDU1 and LDU2 frames making it into the traces on both Phase 1 and 2. Mostly HDU and link control stuff. I'm watching OP25 switch to a voice channel in the console so I know that there is audio on one of the monitored TGs. Does anyone have any pointers or gotchas for this? I have tried both with and without the -2 and -v switches. I am using -w and -W 224.0.0.1. Should I be using the old branch for this? Is this possible? I have also noticed on Phase I systems that the TGID, ALGID, and MI shows up in the stderr file when debug (-v) is set to 10, I think. But this does not happen on Phase 2. Any way to make this happen on Phase 2? Thanks for any assistance. James

5 6

OP25 for noobs by a noob (long)
by flkmrz＠gmail.com [op25-dev] 08 Sep '17

08 Sep '17

Trying to get op25 running was pretty much an exercise in frustration and annoyance. I've been doing computers for quite a few years, but I'm not a linux power user. After quite a bit of trial and error, wading through multiple forum posts, and doing more trial and error, I came up with a (hopefully) complete set of step by step instructions for getting op25 up and running. These instructions assume that you have just done a clean install of ubuntu 14.04 32bit linux. I ran into multiple problems with the 64 bit version. While I'm sure that they could be overcome, it seems the 32 bit version is easier. There are also probably other easier and/or faster ways of doing some of this stuff. Some of the stuff may be redundant. The bottom line is this is what worked for me. Your mileage may vary. Batteries not included. So, without further ado.... Make sure you have a working internet connection. Click on the settings icon on the left. When the system settings window opens, click on "software and updates". The first tab (ubuntu software) should have everything checked. Click on the second tab (other software). The first two options should be unchecked. Check them. You may be asked for your password to authenticate after checking the first one. Give it, then check on the second one. Click close on the lower right. You'll be told that the software needs to be updated. Let it. x out of the system settings window. Open a terminal window by typing <CTRL><ALT>t type in the following sequence of commands, pressing the enter key after each line. Anything in parentheses is a comment. sudo apt-get update sudo apt-get update sudo apt-get install aptitude sudo apt-get install aptitude sudo aptitude update (Yes, some of the commands are issued twice. I found that it makes it work. ) sudo apt-get update sudo apt-get build-dep gnuradio (hum the theme from Final Jeopardy. Make a sandwich. Get some chips to go with the sandwich. Get a cold drink to go with the sandwich and chips. Eat the sandwich and chips, and drink the cold drink. Quietly hum In A Gadda Da Vida. The long version. You're going to be here a while.) sudo apt-get install gnuradio gnuradio-dev gr-osmosdr librtlsdr-dev libuhd-dev libhackrf-dev libitpp-dev libpcap-dev git (go refill the cold drink and get some cookies for dessert. Eat the cookies slowly, and drink your cold drink.) cd ~ sudo git clone git://op25.osmocom.org/op25.git cd op25 sudo mkdir build cd build sudo cmake ../ sudo make sudo make install sudo ldconfig Now, we're going to blacklist the standard rtlsdr driver. To do this, use the following series of commands: cd /etc cd modprobe.d sudo gedit blacklist.conf Go to the end of the file, hit enter to add a blank line (for readability) and type in the following two lines: # this line prevents the standard dvb driver from loading blacklist dvb_usb_rtl28xxu At this point, you should have gnuradio and op25 installed. The next thing to do is to edit the files invoking op25 so you can listen to your system of interest. use the following sequence of commands to create a shell file to invoke op25 on your system of interest: cd ~ sudo gedit op25 Now, type in the following lines. We're going to assume that you want to listen to a P25 Phase II system. #!/bin/bash cd ~/op25/op25/gr-op25_repeater/apps python scope.py --args 'rtl' -g 65 -f 851.200e6 -N 'LNA:49' -2 -V -v 0 -S 1000000 -q 2 -T trunk.tsv cd ~ Save the file, and x out of gedit. An explanation of each of the command line arguments is available in the documentation. For now, we'll point out that the number following -f is the frequency of the control channel of interest, and the number following -q is the correction factor in ppm for the sdr stick that you're using. Next, we have to edit the trunking control files. Do the following series of commands: cd ~/op25/op25/gr-op25_repeater/apps sudo gedit trunk.tsv The default file that comes with the install lists a number of systems. Delete everything after the double quotes around "Center Frequency". Hit enter to get to the beginning of a new line. Type in the following line: "Kokomo"<tab>"851.200"<tab>"0"<tab>"0x734"<tab>"CQPSK"<tab>"trunkk.tsv" where <tab> is the tab key. Do not insert any spaces -- use tab only. By way of explanation, the first is the name of the system. Then comes the frequency of the control channel. You could insert several control channel frequencies separated by commas between the quotes, but I've found that this gives less than optimal performance. The remaining fields are offset, then the system ID (which you can find on RadioReference.com) the modulation type, and a file listing talkgroups. Substitute the appropriate data for your system. There is also a provision for whitelisting and blacklisting particular talkgroups, which I won't cover here. *** Make sure that there is absolutely nothing after the final quotes. Any spaces will make the program crash. *** At this point, save the file, and x out of gedit. Almost there..... Finally, we need to create a listing of talkgroups and names. This is actually optional, but it's much better listening when you can see what talkgroup is active, rather than just a number. While there are several ways of getting a talkgroup listing into a file, I'm only going to cover manually entering talkgroups. Talkgroups are in a tab delimited file, without quotes around the talkgroup numbers and tag names. For the example file, I'm only going to put in a couple of talkgroups -- just enough that the idea is obvious. If you've been following, you should still be in the ~/op25/op25/gr-op25_repeater/apps directory. Perform the following series of commands: sudo gedit trunkk.tsv Then, enter the following lines. Press the <tab> key between the talkgroup number and talkgroup name, and press enter after the talkgroup name. 10008 County All-Talk 10022 EMS Dispatch After you've entered your desired talkgroups, save the file, and x out of gedit. Go back to your home directory by typing: cd ~ To start op25, type the following bash op25 The operation of the program has been documented elsewhere, and it's mostly self-explanatory. A couple of hints: If you're getting choppy audio, turn off the displays for the tabs from spectrum through symbols. A Celeron 530 at 1.73 GHz would barely handle the audio with the displays turned off. If you get a NAC error when trying to start the program, check for trailing spaces in your trunk.tsv file. *Any* spaces at the end will crash the program. Hopefully, this will make it easier for people to get op25 up and running. Enjoy!

13 40

Building on OSX
by 'O'Connor, Daniel' darius＠dons.net.au [op25-dev] 17 Aug '17

17 Aug '17

Hi, I'm trying to build op25 on OSX and while I can get it to build and install it doesn't work. It sends up installing into /opt/local/lib/python2.7/site-packages instead of /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/ If I add /opt/local/lib/python2.7/site-packages to sys.path or copy the files into the 'right' directory I get the following error.. In [2]: sys.path.append('/opt/local/lib/python2.7/site-packages/') In [3]: import op25 --------------------------------------------------------------------------- ImportError Traceback (most recent call last) <ipython-input-3-7d3debe9ed1a> in <module>() ----> 1 import op25 /opt/local/lib/python2.7/site-packages/op25/__init__.py in <module>() 43 44 # import swig generated symbols into the op25 namespace ---> 45 from op25_swig import * 46 47 # import any pure python here /opt/local/lib/python2.7/site-packages/op25/op25_swig.py in <module>() 15 except ImportError: 16 return importlib.import_module('_op25_swig') ---> 17 _op25_swig = swig_import_helper() 18 del swig_import_helper 19 elif _swig_python_version_info >= (2, 6, 0): /opt/local/lib/python2.7/site-packages/op25/op25_swig.py in swig_import_helper() 14 return importlib.import_module(mname) 15 except ImportError: ---> 16 return importlib.import_module('_op25_swig') 17 _op25_swig = swig_import_helper() 18 del swig_import_helper /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/importlib/__init__.pyc in import_module(name, package) 35 level += 1 36 name = _resolve_name(name[level:], package, level) ---> 37 __import__(name) 38 return sys.modules[name] ImportError: No module named _op25_swig There is a file called /opt/local/lib/python2.7/site-packages/op25/_op25_swig.so so I don't know why it can't find it :( I tried renaming it from .so to .dylib but it still can't find it. I note that some of the GNUradio stuff is installed as a .so so..?! :) I have GNURadio installed using Macports and that seems to work fine. Any help appreciated, thanks. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C

2 5

libairspy-dev in Unbuntu 14.04?
by wa8wg＠centurytel.net [op25-dev] 11 Aug '17

11 Aug '17

Can anyone assist in how to add Airspy (libairspy-dev) to GNU Radio + OP25 on Ubuntu 14.04? I am presently using the RTL-SDR but would like to use my Airspy SDR. I have come across some information that uses PyBombs to install libairspy-dev but can't seem to get PyBombs install properly on Ubuntu 14.04. I would also like to try it on Raspbian Jessie on my Pi3-B but don't believe that the Pi has enough processing power to run the minimum sampling rate of the Airspy. Any help would be appreciated. Bill, WA8WG

1 0