-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
i improved the ecc for the ldu1 and ldu2. I added clearer comments,
shortened the code/lowered the amount of calculations it does, and put
the entire routine into one function. I have been running it for days
now with no seg fault.
- --
- ------
Matt D
- ------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)
Comment: MacGPG2 - http://www.gpgtools.org/macgpg2.html
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJStbhgAAoJECrdp7MWSIVbtHMIAJ71NZzINEGpLdFLjzA5HxKo
QVK6dTw1hc8JusFRO+49pYAi3CXonu+RS66MDHhdZVZ8bvUHjalMa9rrxz6DWAEl
pmHDE1XMKJ6+alm0ZwykvkK0JNomEy4LV6x+Q+uBq/D1hRc4ak/B87kvwfEnqx1q
Mk3sHJgGKY5KXgLs3hkYw2ws9tUuu2he/K9o8UanP2NfepdSAmK0IYKZHDpMJLya
qYBjTdn2GlKih5l1EppBsFgRubDTjSPCKnriZ8f0IuqRWl53HdmLLAU1XglxuIwe
Cph1AJXYUkiYG9uET8ym03EWXqlO1z3ZNeLZXSyp7iY4xFMHLyee+V3HS1mY/G0=
=410A
-----END PGP SIGNATURE-----
Can the nac be changed for transmitting? Haven't had a ton of time to look
through the source.
Ryan kc9gmy
On Dec 16, 2013 11:29 AM, "Matt D" <md123(a)nycap.rr.com> wrote:
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
> Would it be possible to add scanning capability to op25 so we could
> scan a list of freqs or search for active freqs within some range?
>
> If adding this feature is possible where would one start?
> - --
> - ------
> Matt D
> - ------------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.21 (GNU/Linux)
> Comment: MacGPG2 - http://www.gpgtools.org/macgpg2.html
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJSrzhgAAoJECrdp7MWSIVbL8oH/2LVZBAkNvVUNBmhzCmnz7Uu
> d86hfbmWA1GvjgMfNggp0PWgsEycbLIFq/syvTHQn8O0vjKGz0CF+3wgZ7bFujPt
> 6vMobr8iINNDub4n1bKsfLPiPzHpRt9paDB7M8Y0VszQrewaHYqNRp7/HFnMWkkO
> pOhUWJEeyn2Bv0MgNTAWt5owtJxjLtUCRDGcalXbSFWdrAr8BZdcG85htl55F3uE
> pd7DNKZgtR+dldJeRplih6bbSpDZbBxsbjOff59Wp892HhgIYsYGa7NhtFZe3BA5
> Y7GVnhEiX4fKunyCYzAtm0DwgjmsmE6Jn4V+ptN40m0I/sJIe6I/DoayvkiFduA=
> =ApBi
> -----END PGP SIGNATURE-----
>
>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Would it be possible to add scanning capability to op25 so we could
scan a list of freqs or search for active freqs within some range?
If adding this feature is possible where would one start?
- --
- ------
Matt D
- ------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)
Comment: MacGPG2 - http://www.gpgtools.org/macgpg2.html
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSrzhgAAoJECrdp7MWSIVbL8oH/2LVZBAkNvVUNBmhzCmnz7Uu
d86hfbmWA1GvjgMfNggp0PWgsEycbLIFq/syvTHQn8O0vjKGz0CF+3wgZ7bFujPt
6vMobr8iINNDub4n1bKsfLPiPzHpRt9paDB7M8Y0VszQrewaHYqNRp7/HFnMWkkO
pOhUWJEeyn2Bv0MgNTAWt5owtJxjLtUCRDGcalXbSFWdrAr8BZdcG85htl55F3uE
pd7DNKZgtR+dldJeRplih6bbSpDZbBxsbjOff59Wp892HhgIYsYGa7NhtFZe3BA5
Y7GVnhEiX4fKunyCYzAtm0DwgjmsmE6Jn4V+ptN40m0I/sJIe6I/DoayvkiFduA=
=ApBi
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
i checked out 328 from the svn source and now I get this when trying
to build.
make[2]: Leaving directory `/home/matt/op25/blocks/src/lib'
Making check in python
make[2]: Entering directory `/home/matt/op25/blocks/src/python'
make check-TESTS
make[3]: Entering directory `/home/matt/op25/blocks/src/python'
Traceback (most recent call last):
File "./qa_op25.py", line 24, in <module>
import op25
File "/home/matt/op25/blocks/src/lib/op25.py", line 24, in <module>
_op25 = swig_import_helper()
File "/home/matt/op25/blocks/src/lib/op25.py", line 16, in
swig_import_helper
import _op25
ImportError: /home/matt/op25/blocks/src/lib/.libs/_op25.so: undefined
symbol: _ZNK4ldu23lcfEv
FAIL: run_tests
==================
1 of 1 test failed
==================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/home/matt/op25/blocks/src/python'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/home/matt/op25/blocks/src/python'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/matt/op25/blocks/src'
make: *** [check-recursive] Error 1
matt@matt-Inspiron-1525:~/op25/blocks$
I cant shake it; any help will be much appreciated.
- --
- ------
Matt D
- ------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (GNU/Linux)
Comment: MacGPG2 - http://www.gpgtools.org/macgpg2.html
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSp30lAAoJECrdp7MWSIVbcDcH/0BdZHVshXzC1m72OfXYw4bV
r1rYlYSKJCC2yslR2aM12Bf4tiEwapHRuATpNTdm+6a8FeM5nXPy/e/0N327PB42
JJ9aFLLE0e0f1KBgKwg3WJwpjEl2tSyVfr16bn1BrkpukwDHIXylyFkPQQSAeQGK
3FkWkAf10ivDbyJHUqF8wAIiSmoz8satXAvR+lkS2n0WLXQqxAUPfwzOj+/IdLza
HY3lFhkn+FAvThzCewmiX9pYGzSW6jU3ZdbCRXgtkRus+srIxSkhrBRSZ1u1L5BK
mfeVuNobRp+LMZ8OWBN79XiJ1ySPPj6ZHAxx4CKy3DqvOlg3VHEOSxemYKINBgg=
=QR5x
-----END PGP SIGNATURE-----
I'm pleased to announce a major new OP25 release, which may be downloaded at http://mattrobert.com/Wireless/op25-gr3.7-0.01.tar.gz
The code has been completely reorganized with the following key changes:
1) This release of OP25 is compatible with GNU Radio version 3.7 (or newer)
2) The build system has been changed from autotools/autoconf to cmake
3) Support for gr-osmosdr has been added. This means that (in addition to USRP support) hardware support is extended to all devices supported by osmosdr (see http://sdr.osmocom.org/trac/wiki/GrOsmoSDR for a complete list of supported hardware)
4) Experimental trunk tracking support for IMBE voice channels now included (optimized for LSM/CQPSK) in the signal scope application
Not all pieces (in particular the python scripts) have been converted to the new format yet. Other pieces (for example the Wireshark plugin) should continue to be downloaded from the SVN repository while we work on pulling them into to the new codebase.
Please excuse the mess - we're working to make improvements and this release is the first step in that process. These code updates will be released as tarballs for the interim period until we can our GIT repository is established. Please notify the list of questions or problems with this new release.
For more information about the trunking and voice support which has been added to the scope.py app see the wiki page at http://op25.osmocom.org/trac/wiki.png/wiki/SignalScopePage
Hey guys,
Can anyone please explain to me what is going on in bch.cc? I am trying
to figure out what ECC is used in there and where it is used exactly.
Thanks
--
------
Matt D
------------
Hey guys,
I deleted my whole op25. checked out a new one. applied Balint's patch,
made some simple changes to the hdu.cc ldu1.cc ldu2.cc and tdu.cc files,
and built with no errors at all. the changes i made:
string
hdu::duid_str() const
{
cout << "HDU";
return string("HDU");
}
string
ldu1::duid_str() const
{
return string("LDU1");
cout << "LDU1";
}
string
ldu2::duid_str() const
{
cout << "LDU2";
return string("LDU2");
}
string
tdu::duid_str() const
{
cout << "TDU";
return string("TDU");
}
all i get in terminal when i hear the noise is a few HDUs. No LDU1s or
any of the others. There should be like 400 "TDU's.
I have been unable to figure what i am doing wrong. Any guidance will
be very much appreciated. Thanks.
--
------
Matt D
------------
Hey guys,
Is anyone getting garbage in the traffic pane UI? I deleted my whole
op25. checked out a fresh version. r328 if i remember right. did the
whole bootstrap, configure, make check, sudo make install dance; and i
am getting garbage in the UI. my logfile looks like this:
2013-11-04 11:02:15.797525 HDU Unknown (0) 0xb13f Unknown (0xc4) 0x5f73
2013-11-04 11:05:10.612410 HDU Unknown (0) 0xed38 Unknown (0x9) 0x73f5
2013-11-04 11:09:21.108211 HDU Unknown (0) 0x8100 Unknown (0x77) 0x1dec
2013-11-04 11:09:21.108955 HDU Unknown (0) 0x61 Unknown (0xa5) 0x7300
2013-11-04 11:09:21.281898 HDU Unknown (0) 0x2ba6 Unknown (0xff) 0x63f7
2013-11-04 11:09:21.460865 HDU Unknown (0) 0x63 Unknown (0x8) 0x7100
2013-11-04 11:09:21.650893 HDU Unknown (0) 0xae6f Unknown (0x7c) 0xed67
2013-11-04 11:09:21.834137 HDU Unknown (0) 0x85 Unknown (0x19) 0x6500
2013-11-04 11:09:22.022031 HDU Unknown (0) 0xf984 Unknown (0x6) 0x360c
as you can see, none of these fields are good data except the date/time.
the HDU should only show up once in while. So something is repeatedly
putting "HDU" and the nonsense data onto the thread to the GRC. In
addition to that i did a:
string
hdu::duid_str() const
{
cout << "HUD\n" ;
return string("HDU");
}
in the hdu.cc and as expected i hundreds of "HUD"s print in the
terminal. so similarly i did a:
string
ldu1::duid_str() const
{
return string("LDU1");
cout << "LDU1\n" ;
}
in the ldu1.cc. and i get no "LDU1"s in the terminal. Ive done this
whole routine 3 times and have got the same result. something weird is
going here that was not with previous versions. like i said the HDU
packets should only come up once in a blue. it would seem that
snapshot() is firing off way to many pickles without getting the right
data in to them.
i have not been able to figure what i am doing wrong here. can someone
please do a fresh install and see if the snapshot() and the traffic pane
play nice for them?
Thanks
--
------
Matt D
------------
