When I run scope ./scope.py I get import error no module named op25
What am I missing
--------------------------------------------
On Sun, 1/31/16, russ.innes(a)gmail.com [op25-dev] <op25-dev(a)yahoogroups.com> wrote:
Subject: [op25-dev] Re: op25
To: op25-dev(a)yahoogroups.com
Received: Sunday, January 31, 2016, 3:35 PM
~/pybombs/src/gr-op25/op25/gr-op25_repeater/apps/
run
scope.py (./scope.py)
You will have to pass
arguments - what are you using for a receiver?
So I just stumbled upon Luke's Trunk Recorder, and I'm a bit unsure how to install it. Specifically, I already have OP-25 installed and working on a Kali machine. So, can I also compile Trunk Recorder without massive conflicts with the existing OP-25 install? Any suggestions would be appreciated. Thanks!!
-Nate
Greetings
It looks like the balint256 'op25' repo tracks the op25 repo at op25.osmocom.org only up to commit 2051a96198c.
The op25.osmocom.org repo has more than a dozen additional commits beyond that, which means that the balint256 op25 install is approx. one year out of date. All of balint's changes don't affect the op25_repeater, so there shouldn't be a big hassle when the time comes to merge everything into master. It looks only like one or two CMakeLists.txt files might have merge conflicts, YMMV.
Accordingly, I recommend as follows (until such time as the merge may happen)
- use only the op25.osmocom.org build when running scope.py
- use only the balint256 one with balint's associated changes
- keep them otherwise separate
Max
ps. Knuckle Punch to Balint!!
Looking for some help, I have 3 machines running Ubuntu 14.04 LTS and OP-25 and all are experiencing the same issues.
Machine 1 is a HP ProBook 6570b with 8GB ram and Core i5-3230M cpu
Machine 2 is a HP ProBook 6570b with 8GB ram and Core i5-3210M cpu
Machine 3 is a HP ProBook 4530s with 4GB ram and Core i3-2350M cpu
We are using RTL-SDR.com Blog sticks (the ones with the TXCO) and monitoring 2 different P25 systems, 1 is a mostly phase 1 and the second is all phase 2. All sites we monitor are LSM sites.
Machine 1 will run for several hours normally and then begin the aUaUaU on what appears to be every other packet. Most of the time closing scope and relaunching it fixes the issue.
Machine 2 will begin this after 20-30 minutes and machine 3 will begin after 10 or so minutes.
No adjustment of antenna location, gain, ppm, fine tune makes a difference once it starts the underrun. Location or proximity to the site also doesn't effect it.
Machine 1 was setup a few weeks before 2 and 3 so I'm not sure if there were any changes to op25 during the last few weeks.
Also I noticed that the op25.osmocom.org site is down. Is there another place to get current information?
Thanks to anyone who can offer any tips on how to make these machines reliable.
I am trying to record a Phase 1 P25 Trunking systems. I have a bunch of OP25 records hooked up to the different channels that the system could use. I have a Valve in the flow graph that will allow samples to pass or dump them to a null_sink. This lets me turn P25 recorders on or off.
The problem is that the recorders using OP25 seem to using a ton of CPU even if they are not getting samples. I tracked it down to the p25_frame_assembler block. Whenever it is connected to a flow graph, it seems to be using a lot of CPU, even if it is not getting any samples.
Any ideas why the p25_frame_assembler block would be using CPU cycles even if it is not getting samples in?
I am running it with the following params:
bool do_imbe = 1;
bool do_output = 1;
bool do_msgq = 0;
bool do_audio_output = 1;
bool do_tdma = 0;