op25-dev

op25-dev@lists.osmocom.org

314 discussions

sockaudio.py startup?
by 'wa8wg' wa8wg＠centurytel.net [op25-dev] 26 Jul '17

26 Jul '17

Max. I am having difficulty getting sockaudio.py working. See my error log below. Any idea of what I have wrong? gr-osmosdr 0.1.3 (0.1.3) gnuradio 3.7.5 built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy Using device #0 Realtek RTL2838UHIDIR SN: 00000001 Found Rafael Micro R820T tuner Project 25 IMBE Encoder/Decoder Fixed-Point implementation Developed by Pavel Yazev E-mail: pyazev(a)gmail.com Version 1.0 (c) Copyright 2009 This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; see the file ``LICENSE'' for details. OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO[149919077 3.506202]p25p1_fdma::rx_sym() timeout OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO[1499191063.867259]p25p1_f dma::rx_sym() timeout OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO[1499191074. 121989]p25p1_fdma::rx_sym() timeout OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO[1499191092.722864]p25p1_fdma::rx_sym( ) timeout OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOO Thank you, Bill William G. Becks, WA8WG N7027 Shady Lane Circle Porterfield, WI 54159 E-Mail: wa8wg(a)centurytel.net

4 13

RC4
by gregella53＠gmail.com [op25-dev] 23 Jul '17

23 Jul '17

I know that a while back there was a grc flowraph of op25 that handled DES. Any chance of a pybombs recipe for op25 that handles RC4 as implemented in Advanced Digital Privacy?

14 84

suggestion: logging output
by John Ackermann N8UR jra＠febo.com [op25-dev] 19 Jul '17

19 Jul '17

In normal operation, it seems that stderr.2 captures mainly messages retuning to the control channel (which is what helped me catch the issue noted in my other message, so that's not all bad). But I think it would be very useful to have the option to log each channel/talkgroup handoff (I'm not sure of the terminology). In particular, building a list of talkgroups would be handy to identify ones that don't have tags. I don't know the difficulty involved, I think it would be really nice to include something like this: 1434343.003423423 frequency: 853.500 talkgroup: 57234 for each handoff. You could then use command line tools (cut, sort, uniq) to build up channel and talkgroup lists. For extra credit, do this at different debug levels. For example, default would print only tuning errors and other things that need user attention. Then at -v 5 print handoffs, at -v 6 print handoffs plus control channel, and leave -v 10 and above as-is. Or maybe add a new command line option to specify the output file. I'm willing to work on this. If I have time, I'll play around with it this week. I will happily accept hints on how to go about it. 73, John

3 3

suggestion: handling alternate control channels
by John Ackermann N8UR jra＠febo.com [op25-dev] 17 Jul '17

17 Jul '17

My local site switched to an alternate control channel a few weeks ago. To address this, I added the primary and 3 alternate CCs in trunk.tsv. (Then last night they switched back to the primary...) I noticed from tail -f'ing stderr.2 that the program (trunking.py?) cycles through all the listed control channels, in order from trunk.tsv, each time it returns from a voice channel. If the active CC is last on the list, the time spent doing that results in dead time when calls are missed. What if the program reordered the control channel list so the active channel is first? That way the retune would immediately go to the active channel and only if it failed would the other channels be scanned (and then the new active channel would go to the head of the list). 73, John

1 0

rx.py suggestion: display available commands, and suggestion to add one
by John Ackermann N8UR jra＠febo.com [op25-dev] 17 Jul '17

17 Jul '17

I think it would be helpful to display the available commands, e.g. "(H)old, (L)ockout, (S)kip, (Q)uit" on either the top or bottom of the terminal window. Also, would it be feasible to add a pair of commands (maybe up/down arrow) that would allow adjusting the frequency correction while the program is running? Thanks! John

1 0

Success! (almost...) [1 Attachment]
by John Ackermann N8UR jra＠febo.com [op25-dev] 17 Jul '17

17 Jul '17

Fresh install of Rasbian jesse and careful following of Max's instructions got rx.py running for me. However, it crashes after a few minutes. Attached is a screenshot of stderr.2 when the crash occurs. Any ideas? I'm also have trouble when trying to use the "-P" option. I'll try to capture details of that later. (BTW -- I found I had better luck using the -T option than just running the command line. Among other things, my local system has apparently shifted to one of the alternate control frequencies, so listening on the primary didn't get me anywhere. Since trunk.tsv specified the alternates, after a few seconds rx.py was able to find the active channel and sync up to it.) John

2 6

rx.py progress
by John Ackermann N8UR jra＠febo.com [op25-dev] 04 Jul '17

04 Jul '17

So, first: I'm quite convinced there is something broken in building the components using the build-gnuradio script. Something in incompatible between the gnuradio, gr-osmosdr, and rtlsdr repositories (and/or my computer and/or Linux Mint 18.1 and/or the RTL-SDR.com dongle). So this time I did it with Max's install.sh in the latest commit, and after installing the needed packages (build-essentials, swig, python-numeric, and gnuplot-x11) got a successful build, and have the rx.py app running -- I think. The problem is, I can't tell if anything's happening. The main window has a single line at the top showing NAC, WACN, SYUSID, tsbks and a single line at the bottom showing the frequency. The NAC value appears to be read from the trunk.tsv file. Neither has changed since I started the program several minutes ago. The stderr.2 output shows a "set trunk_cc to 853600000" command about every 6 to 7 seconds, but nothing else. The audio pipe is running but I haven't heard a peep. Sunday morning is quiet, but it shouldn't be *this* quiet! I've tried running the plot modes (including the undocumented 'fft') but none of them indicate any organized data -- the constellation is just noise, the fft shows a spectrum but without the control channel (most of the time), and the symbol display is just noise. All the plots throw various errors into the stderr.2 file. I've had this RTL-SDR.com dongle working with the old version of op25, on a difference computer, and I know that I have a very strong control channel signal available. So I don't think there's an RF issue. I also tried using a hackrf on this box and had the same results. In each case, the initialization seems to go fine, with the frequency, gain, and sample rate being set without error. I'm just not sure what to do next... Thanks, John

3 4

Wireshark for OP25
by flkmrz＠gmail.com [op25-dev] 03 Jul '17

03 Jul '17

Hi All, Been trying to get wireshark patched and running for op25, without much success. The latest version for which there seems to be a patch is wireshark-1.8.5, which I did get built and running without the op25 patch or plugin. The problem seems to be with getting the plugin and patch via subversion. Trying to follow the posted instructions (from http://op25.osmocom.org/trac/about/wiki/WireSharkPage http://op25.osmocom.org/trac/about/wiki/WireSharkPage) works until attempting to execute svn checkout http://op25.osmocom.org/svn/trunk/wireshark/plugins/p25 p25 at which point it just hangs for a while, and finally comes back and says that it's unable to connect to a repository at that url. There was what appears to be a mirror listed at http://www.sedition.org.au http://www.sedition.org.au which no longer seems to be operational. I'm probably missing something simple, so I hope someone can point me in the right direction to get this working. Thanks!

1 0

OP25 on the Raspberry PI
by ikj1234i＠yahoo.com [op25-dev] 01 Jul '17

01 Jul '17

Below is a guide to the install process, please supply feedback so that it can be improved... First, the testing has been done on the PI 3 "B" with the default install of Raspbian. You'll need to edit the /etc/apt/sources.list file; the file contains the needed "deb-src" line in it, but it's commented out. To fix, edit the file and remove the '#' so the 'deb-src' appears in column one of the file. Save the file, then proceed with the install as follows, first installing the OP25 prerequisites: sudo apt-get update sudo apt-get build-dep gnuradio sudo apt-get install gnuradio gnuradio-dev gr-osmosdr librtlsdr-dev libuhd-dev libhackrf-dev libitpp-dev libpcap-dev git then install OP25 cd ~ git clone https://git.osmocom.org/op25 https://git.osmocom.org/op25 git checkout max cd op25 mkdir build cd build cmake ../ make sudo make install sudo ldconfig The previous generation OP25 application (scope.py) is being deprecated soon; instead we now use the new rx.py. This app is discussed in the README file that's in the OP25 repo that you checked out: op25/gr_op25_repeater/apps/README Max

2 2

OP25 Setup Info
by John Ackermann N8UR jra＠febo.com [op25-dev] 11 Jun '17

11 Jun '17

While I still remembered the steps it took for me to get OP25 running, I thought I would document them on my "John's Geekblog" blog. I broke it into multiple parts; part 1 is at http://blog.febo.com/wp/?p=158. I would welcome any additions/corrections! I also recorded a few minutes of scanning last night -- it was Friday evening and things were hopping so there are a number of missed messages. That video is at https://www.youtube.com/watch?v=_1jO3yM0MIA You may note that my GUI looks a bit different than yours. I spent some time fiddling around to give more display space for the talkgroup tag. I have no idea what I actually did (WX GUI is incomprehensible to me), but I finally came up with a result that doesn't look too bad. Thanks again for all the help! John

4 6

← Newer
1
...
7
8
9
10
11
12
13
...
32
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

op25-dev