Good evening,
Would You kindly to answer a few questions about the OP25 project and how
to organize a transmitter with it using SDR devices (RTL-SDR, LimeSDR)?
In the creation process of DMR-standard transmitter in the GnuRadio
environment, we came across the absence of some necessary blocks: 4FSK
modulator, DMR encoder, packet shaper.
Inside the OP25 project we found a file that contains some functionality of
DMR TX (dv_tx.py), but only in form of code, not as a GRC block.
Could you tell us does this file fully implements the TX-side of the DMR
system and whether there is an analogue of it, in the form of a GRC block
for GnuRadio?
We will be very grateful if you can help us sort this out.
Yours faithfully,
Vladislav.
Any updates to fix the CMAKE issues?
https://github.com/boatbod/op25/issues/25
d$ make
[ 21%] Built target gnuradio-op25
[ 23%] Built target test-op25
[ 24%] Built target _op25_swig_doc_tag
[ 26%] Built target _op25_swig_swig_tag
[ 29%] Built target op25_swig_swig_compilation
[ 31%] Built target _op25_swig
[ 33%] Built target pygen_op25_gr_op25_swig_ac751
[ 34%] Built target pygen_op25_gr_op25_python_b78db
[ 34%] Built target pygen_op25_gr_op25_apps_383eb
[ 51%] Built target imbe_vocoder
[ 78%] Built target gnuradio-op25_repeater
[ 85%] Built target op25-d2460
[ 86%] Built target scan4sync
[ 87%] Built target BER
[ 90%] Built target test-op25_repeater
make[2]: *** No rule to make target
'op25/gr-op25_repeater/swig/op25_repeater_swig.py', needed by
'op25/gr-op25_repeater/swig/op25_repeater_swig.pyc'. Stop.
make[1]: *** [CMakeFiles/Makefile2:954:
op25/gr-op25_repeater/swig/CMakeFiles/pygen_op25_gr_op25_repeater_swig_a9103.dir/all] Error
2
make: *** [Makefile:130: all] Error 2
ddejr@ddejr-pc:~/op25/build$
same result using "./install.sh" method
http://osmocom.org/issues/4225
"make2: * No rule to make target
'op25/gr-op25_repeater/swig/op25_repeater_swig.py', needed by
'op25/gr-op25_repeater/swig/op25_repeater_swig.pyc'. Stop.
make1: [CMakeFiles/Makefile2:874:
op25/gr-op25_repeater/swig/CMakeFiles/pygen_op25_gr_op25_repeater_swig_26094.dir/all] Error
2
make: [Makefile:130: all] Error 2
[ 26%] Built target gnuradio-op25
[ 29%] Built target test-op25
[ 30%] Built target _op25_swig_swig_tag
[ 32%] Built target _op25_swig_doc_tag
[ 36%] Built target op25_swig_swig_compilation
[ 38%] Built target _op25_swig
[ 40%] Built target pygen_op25_gr_op25_swig_388ba
[ 42%] Built target pygen_op25_gr_op25_python_4bea1
[ 42%] Built target pygen_op25_gr_op25_apps_383eb
[ 63%] Built target imbe_vocoder
[ 86%] Built target gnuradio-op25_repeater
[ 89%] Built target test-op25_repeater
[ 91%] Built target _op25_repeater_swig_swig_tag
make2: No rule to make target
'op25/gr-op25_repeater/swig/op25_repeater_swig.py', needed by
'op25/gr-op25_repeater/swig/op25_repeater_swig.pyc'. Stop.
make1: [CMakeFiles/Makefile2:874:
op25/gr-op25_repeater/swig/CMakeFiles/pygen_op25_gr_op25_repeater_swig_26094.dir/all] Error
2
make: * [Makefile:130: all] Error 2"
This breaks OP25 for dummies the most used HOWTO... and even using
just the standard git and running the install.sh
I'm trying to make a OP25 Transmitter with a B200 mini, as in the video. I'm using the same command line as in the video (./dv_tx.py -p p25 --args 'uhd' -t ./1011.dat -r -Q 430137500 -q 1 -gains 'PGA:90 -v 3 -i 400000). I keep receiving the error "Attribute Error: 'file_source_sptr' object has no attribute 'set_gain_adjust'".
I'm new to using SDRs and the B200 mini, so I'd appreciate any advice! Thanks!
Before I go down a hole and end in a dead end....
I have some questions on using the -L option for "logging."
Logging in my universe means logging the audio to Dictaphone/tape/disk/CD/what
ever physical media... NOT the -v option, thats a log, not logging! :) ;)
So after reading about 30 different files on this -L option, it appers that it
will act as A LOGGING RECORDER and RECORD the audio to disk... Great!
What I am after is to record UNKNOWN GROUPS for analysis for ID purposes....
My question(s) are what options are used with this for:
rx.py
trunk.tsv
whitelist.tsv
blacklist.tsv
ie:
rx.py example
./rx.py --args 'rtl' -N 'LNA:47' -S 2400000 -f 8xx.xxxxe6 -o 25000 -q 72 -L 4
-v 10 -T trunk.tsv -V -2 -U -O loop0 -M mysystem.json -l
http:192.168.0.26:8080 -x 3 2>> stderr.2
trunk.tsv then REQUIRES a "center frequency" for the system... 8xx.xxxx based
on the channels of the system... I've determined this for this system,
and it will just fit the way this is setup.
This will then RECORD the various groups that are NOT BLACKLISTED to disk as
WAV's from what I understand... Correct????
Ie: OP25 tunes to a group, it records it.
Anything that is exlusive of each other on this -L option with other optons
for rx.py????
Any thing I am missing in this?????
Goal is simple to log any group I've not blacklisted as known user/use..
Thanks.
In reviewing the various setups of trunking_file.tsv, id_file.tsv
etc... and looking over various documentation, I am not seeing a means
to do RID(LID) or Radio ID aliasing...
I am I missing this some place???
The systems can be setup to alias out $47E136 as "Helo1" etc... The
systems have places to do this from the start and update from consoles
etc...
Any way to do that in OP25???????? ie:
rid.tsv
47e136 Helo1
47e137 Helo2
etc...
Turning RID into an alias would be a plus to ID units... ie: Ladder1,
Ladder1_Portable, FF152521, etc.. Many of these are pretty static..
now some depending on you agency(s) may not be... in on a particular
group would need some updates each year, as they change based on a
progression system.
CC Data is there some sort of aggregate that determines the quality of
the CC data coming out???? That can accessed programmatically???
Or maybe that question is better referenced as is the there something
that documents the API to OP25 that the various python scripts are
using to possible do what I want... The plots are not useful as I
desire text data to use in another place....
So I guess something that documents interacting with the underlying
mechnations of OP25 would probably help to do what I am after with the
CC.
Thanks.
As the next round of P25 PII systems take hold in my area... OP25 is
the goto solution... but...
Audio dying is not a good thing... to send out silence on feeds....
Seems this is related to the metatag update when using -M tags.json
option with rx.py...
Whats frustrating is
Pi3B+ with a cheapo junky asian dongle WORKS with -M tags.json and the
audio goes on... .. I have another issue not related to that, which a
commit fixes, just can't update to handle that right now...
A DUAL CORE laptop with a junk asian dongle... the audio dies after awhile.
SAME DUAL CORE laptop with a V3 Blog dongle... audio dies after awhile
SAME DUAL CORE laptop with V3 blod dongle, REMOVE the -M option and
the audio seems to be stable out to loop0!
URRRGGRRRHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH!
The only thing I can seem to possibly pinpoint is my standard A1
whipping or flogging boi,,, puslecrapdio! RURRRRRHHGHHH!
The laptop has it the Pi3 doesn't....
Any one else seeing similar ? ? ? ? ?
Once I have a new image setup for my Pi feed boxes.. and if that works
reliably great...it seems to on my existing feed, other issue not
witstanding.....
Jusy annoying that a laptop has these issues where as a Pi3B+ doesn't......
I am grasping for answers here... and as I said... my standard A1
whipping or flogging boi,,, puslecrapdio! just gets my attention and
foucs as the problem area.
So to wrap up my screed and vent BS post.. .:) ;)
Any seeing similar with xUbuntu's 18.04 or even other distros on
lap/desktops v. Pi3B+???
Welp... there goes my theory in the time it took to type this OP25 is
now not playing audio out loop0 again, and no -M option was used....
CC channel did rotate... (Harris nee M/A-COM system)??? So maybe CC
rotation kills audio ? ? ? ?
Any one with ideas? ? ? ? Bueller????
Trying to report an bug/issue, but
https://github.com/boatbod/op25/issues doesn't work, goes to wrong
place, and there is no link on the main page of it.
BUG: Program dies due to uncaught exception
Details:
When updating the metadata/"tags" to IceCast, if the connection has
died for some reason, LAN goes down, what ever... There is an uncaught
exception which will kill OP25 running.
1547434556.069343 set tgid=53, srcaddr=0
Exception in thread Thread-4:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/home/pi/op25/op25/gr-op25_repeater/apps/icemeta.py", line 60, in run
self.send_metadata(self.msg.to_string())
File "/home/pi/op25/op25/gr-op25_repeater/apps/icemeta.py", line
77, in send_metadata
r = requests.get((requestToSend), auth=("source",self.cfg['icecastPass']))
File "/usr/lib/python2.7/dist-packages/requests/api.py", line 70, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests/api.py", line 56, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line
488, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line
609, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line
487, in send
raise ConnectionError(e, request=request)
ConnectionError: HTTPConnectionPool(host='audio.myserver.net',
port=8000): Max retries exceeded with url:
/admin/metadata?mount=/RedactedFeed&mode=updinfo&song=[idle] (Caused
by
NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection
object at 0x691bc8d0>: Failed to establish a new connection: [Errno
110] Connection timed out',))
This is not about an issue with the connection, there was, and
eventually led to the Pi being replaced as faulty or melted down from
use of OP25 :) ;)
If the max retries is exceeded or any error where the update fails, it
shouldn't kill OP25 from running...
Glad to add to the issues section of github, but see top part, for
some reason its not there. (??????)
Hi --
After a few months away, I fired up the op25 machine today and updated
to the latest boatbod version. Great improvements, especially the web
interface!
I'm having a minor issue, though. It seems as though my whitelist file
is no longer working. The log shows that it's being read, but doesn't
list the included groups, and I'm hearing lots of traffic from TGs that
aren't on the list. Has anything changed in whitelist handling? (My wl
file is in two column format: TGID<tab>TAG which worked after patches
that Graham applied last year.)
And, by the way, thanks Graham for fixing the statistics.sh script; I
never quite got around to that after the log file format changed.
Thanks,
John
Before I go down a hole and end in a dead end....
I have some questions on using the -L option for "logging."
Logging in my universe means logging the audio to Dictaphone/tape/disk/CD/what
ever physical media... NOT the -v option, thats a log, not logging. :) ;)
So after reading about 30 different files on this -L option, it
appears that it
will act as A LOGGING RECORDER and RECORD the audio to disk... Great!
What I am after is to record UNKNOWN GROUPS for analysis for ID purposes....
My question(s) are what options are used with this for:
rx.py
trunk.tsv
whitelist.tsv
blacklist.tsv
ie:
rx.py example
./rx.py --args 'rtl' -N 'LNA:47' -S 2400000 -f 8xx.xxxxe6 -o 25000 -q 72 -L 4
-v 10 -T trunk.tsv -V -2 -U -O loop0 -M mysystem.json -l
http:192.168.0.26:8080 -x 3 2>> stderr.2
trunk.tsv then REQUIRES a "center frequency" for the system... 8xx.xxxx based
on the channels of the system... I've determined this for this system,
and it will just fit the way this is setup.
This will then RECORD the various groups that are NOT BLACKLISTED to disk as
WAV's from what I understand... Correct????
Ie: OP25 tunes to a group, it records it.
Anything that is exclusive of each other on this -L option with other optons
for rx.py????
Any thing I am missing in this?????
Goal is simple to log any group I've not blacklisted as known user/use..
Thanks.
I am noticing as I set this up and letting it run that after some
point the audio dies on loop0, thus the feed is silence, nicht gut!
Any one else seeing this????
This is both on a PI3B+....and an old dual core laptop.....
The laptop has a -V10 and I tail the output log, and the decode
traffic is still good for the CC, no errors in it...
I can see TG's appear in the tags for the groups from both, just no
audio.... :( :(
Simply killing rx.py, restart, audio comes back,....
Doesn't seem to be much to tie it down... runs overnight, no issues, I
even restarted OP25 on both setups to make some changes to use the TG
priority option... and that was about 10 or so hours of run time....
as some point after the 5-6 hour time period it die{d|s} .. can't be
exact as real work gets in the way...
Dongle related?? But if it was that would expect to see CC decode
errors etc... but I see CC decodes stream, and then decodes for data
when voice is active..... ? ? ?
Any one else seeing this ??? Any corrective action???? ? ? ? ? ? ??
? ? ? ? ? ?
THANKS!
