op25-dev

op25-dev@lists.osmocom.org

1 participants
309 discussions

rx.py Quirks
by Brett Friermood brett.friermood＠gmail.com [op25-dev] 18 Nov '17

18 Nov '17

Hello all, I've been excited about trying the new rx.py since it was first announced and finally was able to install it last night and was quite impressed. In the last couple weeks I've attempted to run it on my Toughbooks, running Debian, but have not been able to cleanly install the python-gtk2-dev dependency for gnuradio. Last night I dug my SDR/DSP computer back out from recent desk remodeling and fired it up. I purpose built this computer specifically to run OP25 and SDRTrunk on Ubuntu with an i7 processor, and large amounts of RAM, and an SSD. In addition to updating the original OP25 to latest, I also installed the boatbod version and spent most of my time running it. It was very nice to run in CLI only mode which I've wanted to do for a long time. By using the internal audio server and the "t" trunk-tracking command I was able to dial up every site I tried within my coverage area and start following traffic. It has been a while since I've used OP25 so I was midly surprised when I was able to receive a site that other software will not receive. I did notice a couple issues, though. I observed a crash when toggling off a plot. Turning on the plot would work fine, and even trying to turn on another would produce a warning that only one can be active, but everything continued running. However, when I turned off the plot the window would close as expected but then the terminal would freeze. After a couple seconds "0"'s would begin showing as if there was no data from the SDR. The only way I was able to fix it was to kill the python process. After starting again everything would work until turning off a plot. It also wasn't limited to a single plot as it happened with all of them. The second issue I faced was when trying to use a trunk.tsv file with the "T" option. After fixing my .tsv files after the quotes got obliterated it appeared to load and start running, however only showed a single site's information at the top of the terminal and another site's control channel frequency at the bottom. I ran short of time so I wasn't able to determine if it heard voice traffic or not, but it did not appear to be stepping through the different sites' control channels as configured in the .tsv file. Am I incorrect as to how the .tsv file is handled? Brett

3 6

boatbod's op25 github fork updated
by gnorbury＠bondcar.com [op25-dev] 30 Oct '17

30 Oct '17

For anyone interested, I have merged the latest changes to the osmocom max branch into my op25 github fork https://github.com/boatbod/op25 and added the ability to dynamically turn on and off the various plots (fft, constellation, symbol & datascope). These are controlled from the terminal window by pressing the 1, 2, 3 & 4 keys. 1 = fft 2 = constellation 3 = symbol 4 = datascope Presently it is only possible to enable one plot at a time. Once I figure out how to track and untangle the gnuradio inter-block connections, I will see about making them operate simultaneously. Graham

2 2

No audio
by Tom Hayward tom＠tomh.us [op25-dev] 19 Oct '17

19 Oct '17

I have an older system working fine on the master branch and I'm currently trying to set up a new VM running the max branch. The goal is to send audio from two talkgroups to darkice. The problem is that I'm not getting any audio out of rx.py. I know the darkice config works, because I can do this and hear pink noise on the stream: speaker-test -r 8000 -D hw:Loopback,0,0 But starting rx.py with the same audio device like this, I never hear anything: ./rx.py --args rtl=0 -N LNA:42 -f 774081250 -S 1320000 -v 5 -2 -T ss911_tacoma.tsv -O hw:Loopback,0,0 The receiver seems to be working. I can see the name of the talkgroup I'm interested in at the bottom of the screen while it's active, I just don't hear anything on the stream: """ NAC 0x1e1 WACN 0xbee00 SYSID 0x1e7 774.431250/804.431250 tsbks 2390 voice frequency 773.431250 tgid(s) 40306 40107 0.3s ago count 77 voice frequency 774.681250 tgid(s) 59197 40106 0.3s ago count 166 Frequency 774.431250 Talkgroup ID 40106 PCSO East """ Is there something obvious I'm doing wrong here? P.S. Is there a better way to pipe audio to darkice than snd-aloop? Tom

2 6

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

Ubuntu 14.04 Audio Crashing
by 'William Becks' wa8wg＠centurytel.net [op25-dev] 12 Oct '17

12 Oct '17

I have been chasing a problem with the audio crashing after 24 hours of continuous operation in Ubuntu 14.04 that appeared to have been caused by pulseaudio. However, that was apparently not the cause as the audio server still crashes after 24 hours even with pulseaudio removed from the system. This is the response that scrolls when performing a speaker-test once the audio server crashes. op25@op25-VirtualBox:~$ sudo speaker-test -t sine -f 500 -c2 [sudo] password for op25: speaker-test 1.0.27.2 Playback device is default Stream parameters are 48000Hz, S16_LE, 2 channels Sine wave rate is 500.0000Hz Rate set to 48000Hz (requested 48000Hz) Buffer size range from 2048 to 16384 Period size range from 1024 to 1024 Using max buffer size 16384 Periods = 4 was set period_size = 1024 was set buffer_size = 16384 0 - Front Left 1 - Front Right Time per period = 0.162188 0 - Front Left 1 - Front Right Time per period = 0.172795 0 - Front Left 1 - Front Right Time per period = 0.171719 0 - Front Left 1 - Front Right Time per period = 0.170190 0 - Front Left 1 - Front Right Time per period = 0.168764 0 - Front Left 1 - Front Right Time per period = 0.176896 0 - Front Left 1 - Front Right Time per period = 0.172278 0 - Front Left 1 - Front Right Time per period = 0.172175 0 - Front Left 1 - Front Right Time per period = 0.171800 0 - Front Left 1 - Front Right Time per period = 0.172193 0 - Front Left 1 - Front Right Time per period = 0.170080 0 - Front Left 1 - Front Right Time per period = 0.173308 0 - Front Left 1 - Front Right Time per period = 0.172197 0 - Front Left 1 - Front Right Time per period = 0.172493 0 - Front Left 1 - Front Right Time per period = 0.172013 0 - Front Left 1 - Front Right Time per period = 0.171716 0 - Front Left 1 - Front Right Time per period = 0.172795 0 - Front Left 1 - Front Right Time per period = 0.176432 0 - Front Left 1 - Front Right Time per period = 0.172236 0 - Front Left 1 - Front Right Time per period = 0.172164 0 - Front Left 1 - Front Right Time per period = 0.172311 0 - Front Left 1 - Front Right Time per period = 0.171918 0 - Front Left 1 - Front Right Time per period = 0.169485 0 - Front Left 1 - Front Right Time per period = 0.169537 0 - Front Left 1 - Front Right Time per period = 0.176434 0 - Front Left 1 - Front Right Time per period = 0.172278 0 - Front Left 1 - Front Right Time per period = 0.168199 0 - Front Left 1 - Front Right ^CWrite error: -4,Interrupted system call (Control-C entered here to interrupt speaker-test.) xrun_recovery failed: -4,Interrupted system call Transfer failed: Interrupted system call op25@op25-VirtualBox:~$ Has anyone seen this behavior while running op25 on Ubuntu? Could there be a cron task that executes every 24 hours causing loss of the audio server?? Thank you, Bill, WA8WG

1 0

OP25 on Ubuntu 14.04
by 'William Becks' wa8wg＠centurytel.net [op25-dev] 11 Oct '17

11 Oct '17

Gents, Has anyone else observed that pulse audio seems to crash consistently after approximately 24 hours of continuous operation of Ubuntu14.04? This happens regardless of the branch of op25 built on the system. I have searched the web for this problem and have tried a number of fixes for the pulse audio crash but none of them have corrected the problem. I have tried uninstalling pulse audio to use the underlying ALSA, but can't seem to maintain reliable audio level settings after a shutdown or a reboot. Any ideas or suggestions would be appreciated. Thank you, Bill, WA8WG

2 7

Some op25 patches [2 Attachments]
by John Ackermann N8UR jra＠febo.com [op25-dev] 26 Sep '17

26 Sep '17

Hi -- Back in July I got Max's then-current branch running on my RPi 3, and then proceeded to make some changes around the edges. In terminal.py I did a couple of things: 1. Made the terminal window size-aware so that you can display more than 20 "voice frequency..." lines without crashing Without this, if a site has more than 20 channels, the program will crash when the 21st shows up. With the patch, just make the console window taller and avoid the problem. 2. Cleaned up the console display a bit, and added a "help" line to display the available commands. I don't think there have been any recent changes that would impact these changes and my diff seems to apply cleanly to the current version. The more interesting set of changes are in trunking.py where I cleaned up the log lines for consistency, moved one set of messages from console to stderr, added some granularity to the -v settings, and added a couple of new log messages that provide additional info. As a result, the stderr.2 output is now (IMHO) more useful, and you can analyze it to learn fun facts. For example, attached if Yahoo allows are screenshots of activity by hour, and a sorted list of the most active talkgroups on the site. I wrote a shell script that reads stderr.2 to generate this data. I see that there's been some recent activity in Graham's new fork. It looks like trunking.py has been updated and I don't know if my changes might conflict. My patch-fu is not the greatest, and I don't want to screw things up, but I'd like to contribute my stuff to the project. Graham, I don't have your direct email address. Can I send you my files (based on the Max branch as of mid-July) and ask you to diff them and add them to your repo if they are OK? I'll also provide the traffic analysis script. Of course, I'm happy to send the files to anyone else who might want them. Thanks, John N8UR jra(a)febo.com PS -- and I am hoping to make a ready-to-go RPi op25 image file available as soon as I get these patches integrated.

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

Undefined Symbol Error
by James K4JK k4jk.james＠gmail.com [op25-dev] 21 Sep '17

21 Sep '17

Hi again all, I'm trying to get the main branch running with some of the changes that Joe incorporated last year. Everything compiles fine (this is a fresh install of Ubuntu 14.04) but when running scope.py I'm getting and undefined symbol error: (most recent call last): File "./scope.py", line 55, in <module> import op25_repeater File "/usr/local/lib/python2.7/dist-packages/op25_repeater/__init__.py", line 45, in <module> from op25_repeater_swig import * File "/usr/local/lib/python2.7/dist-packages/op25_repeater/op25_repeater_swig.py", line 28, in <module> _op25_repeater_swig = swig_import_helper() File "/usr/local/lib/python2.7/dist-packages/op25_repeater/op25_repeater_swig.py", line 24, in swig_import_helper _mod = imp.load_module('_op25_repeater_swig', fp, pathname, description) ImportError: /usr/local/lib/libgnuradio-op25_repeater.so: undefined symbol: _ZN8p25p2_vf12encode_dstarEPhPKi Searching around for this does not turn up anything really. Has anyone seen this before? Thanks, James

4 8

← Newer
1
...
5
6
7
8
9
10
11
...
31
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

op25-dev