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
Every now and then, shortly after startup I am seeing the error shown in
the attached screenshot. It causes the program to exit. It doesn't
show up every time, and if it doesn't appear within 30 seconds or so, it
won't ever.
I have no clue what's causing it; I don't think it's related to my
patches (at least, the offending line is well before any of my changes).
Maybe something isn't always initialized properly?
John
I've much improved the frequency/talkgroup logging in the patch I sent
to the list on Monday. That version just dumped out, once per second,
the freq and talkgroup list shown in the console main window (one line
per freq, with last used tgid.
New version:
-v 5 prints:
[timestamp] new freq: [freq]
[timestamp] new tgid: [tgid] [tag if tagfile present]
[timestamp] set control freq: [freq] (note: only if cc_trunk changes)
This makes it easy to build a list of all the frequencies and talkgroups
seen on the system, without creating excess output.
-v 6 includes the above and adds a line for every tgid whether new or not:
[timestamp] set tgid: [tgid] (note: tag not included)
In addition to the above, this allows simple traffic analysis (how often
is this tgid used, and when).
Also changed: there was a fairly frequent line printed to console about
"process_data_unit timeout". I changed that to go to stderr when -v is
set to 10 or above, and also added a timestamp. I have no idea what
this message means, but it doesn't seem to affect program operation.
Attached are both the original patch file from Monday, and the new
patch. Apply the original one, then patch2 on top of it.
John
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
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?
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
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
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
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
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