Re: [Discuss-gnuradio] Getting gnuradio 3.6.5 working on Linux Mint 14
> Did you follow the suggestions for PYTHONPATH that are made at the end of the
> script output?
Yep:
cja@cja-laptop ~ $ echo $PYTHONPATH
/usr/local/lib/python2.7/dist-packages
Also:
cja@cja-laptop ~ $ echo $LD_LIBRARY_PATH
/usr/local/lib
> What happens if you:
>
> python -c "from gnuradio import gr"
>
> If it errors, what is the complete trace output?
cja@cja-laptop ~ $ python -c "from gnuradio import gr"
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/__init__.py",
line 27, in
from gnuradio_core import *
File "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/gnuradio_core.py",
line 23, in
from gnuradio_core_runtime import *
File
"/usr/local/lib/python2.7/dist-packages/gnuradio/gr/gnuradio_core_runtime.py",
line 26, in
_gnuradio_core_runtime = swig_import_helper()
File
"/usr/local/lib/python2.7/dist-packages/gnuradio/gr/gnuradio_core_runtime.py",
line 22, in swig_import_helper
_mod = imp.load_module('_gnuradio_core_runtime', fp, pathname, description)
ImportError: /usr/local/lib/libgnuradio-core-3.6.5.so.0.0.0: undefined
symbol: volk_64u_byteswap_u
Chris
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] A basic but critical problem in stopping of python code
When run a python script file, as we know main function will be run first. We send the class to a object "tb",for instance,we use tb.start or tb.run.but if we want to stop a flawgraph and reconfiguration.we must use tb.stop with tb.wait and then restart tb.when I use this ,the tb.wait() can not finish . I don`t know why. even I use tb.lock() and tb.unlock() it doesn`t work too. I take this test in tunnel.py.___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Getting gnuradio 3.6.5 working on Linux Mint 14
On 23 June 2013 02:55, Josh Blum wrote: > ... > We have had issues with builds compling against installed headers. Try > removing installed volk hdrs in /usr/include and /usr/local/include first. No volk headers anywhere in /usr/include. I removed the volk directory from /usr/local/include and ran build-gnuradio again - it re-created the /usr/local/include/volk directory and header files. I still get the same error when making multimode. So I dont think it is a problem with pre-installed volk headers. Hmmm... interestingly in /usr/local/lib, libvolk.so points to libvolk.so.0.0.0 - surely it should have a name like libvolk-3.6.5.so.0.0.0 ? Chris ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Getting gnuradio 3.6.5 working on Linux Mint 14
On 06/23/2013 03:32 AM, Chris Adie wrote:
Did you follow the suggestions for PYTHONPATH that are made at the end of the
script output?
Yep:
cja@cja-laptop ~ $ echo $PYTHONPATH
/usr/local/lib/python2.7/dist-packages
Also:
cja@cja-laptop ~ $ echo $LD_LIBRARY_PATH
/usr/local/lib
What happens if you:
python -c "from gnuradio import gr"
If it errors, what is the complete trace output?
cja@cja-laptop ~ $ python -c "from gnuradio import gr"
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/__init__.py",
line 27, in
from gnuradio_core import *
File "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/gnuradio_core.py",
line 23, in
from gnuradio_core_runtime import *
File
"/usr/local/lib/python2.7/dist-packages/gnuradio/gr/gnuradio_core_runtime.py",
line 26, in
_gnuradio_core_runtime = swig_import_helper()
File
"/usr/local/lib/python2.7/dist-packages/gnuradio/gr/gnuradio_core_runtime.py",
line 22, in swig_import_helper
_mod = imp.load_module('_gnuradio_core_runtime', fp, pathname, description)
ImportError: /usr/local/lib/libgnuradio-core-3.6.5.so.0.0.0: undefined
symbol: volk_64u_byteswap_u
Chris
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
I would re-run build-gnuradio with --logfile
And go over the log with a fine-toothed comb to see if there was an
issue when building/installing VOLK.
--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP for physics project
Regardless of whether you use the stock FPGA design or a custom one to do raw data capture you are going to run up against the basic limits of 1GB/s i.e 1Gb/S = 125MB/S = 62.5M 16bit samples/S The stock image is always going to want to send an I and Q channel, and has the option of either 25MSamples/S @ 16bit or 50MSample/S @ 8bits and it's going to pass the data through either 1 or 2 low pass FIR filters to decimate to that data rate. Even if you write a very custom FPGA design that packs 14bit data efficiently and uses a raw UDP transport, you would be doing well to achieve 70MSample @14bits over ethernet since real world performance never quite matches theoretical. Interesting project though, the USRP could definitely be a useful generalized scientific data capture device. -ian On Jun 22, 2013, at 8:11 PM, n...@gu.pe wrote: > I'm looking at using USRPs for data acquisition in a physics project using an > LFRX. > Rather than for more typical SDR applications. I'd be interested in hearing > from > anyone who's done this. > > At first however I was wondering if this application sounds feasible, is it > crazy to > use the USRP for non-SDR applications? Are their other better suited devices? > > I'd like to use it to replace this product: > http://sine.ni.com/nips/cds/view/p/lang/en/nid/209713 > And possibly eventually integrate into our own PCB, I guess the n200 is still > mostly open hard/software? > > So real rather than IQ data I guess. I'd like to samples at 100MS/s 14bit, > and stream it > over the network, would this require changing the FPGA code? > > I've pinged a few people off list, so apologies if this is a duplicate, I'll > post here > if I receive a reply. > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP for physics project
On 06/23/2013 11:34 AM, Ian Buckley wrote: Interesting project though, the USRP could definitely be a useful generalized scientific data capture device. -ian I've used USRPs for radio astronomy for years, so, yeah :) But I think with a customized image you could send 100Msps of real-mode-only data down the wire... -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP for physics project
At 8bits sure, no problem, 14bits and we are into real-time lossless data compression…another somewhat hard but interesting project. Unless the OP wants to only capture for short intervals, in which case I guess you could capture to the 1M SRAM and read back data non-real time. On Jun 23, 2013, at 8:38 AM, Marcus D. Leech wrote: > On 06/23/2013 11:34 AM, Ian Buckley wrote: >> >> Interesting project though, the USRP could definitely be a useful >> generalized scientific data capture device. >> -ian >> >> > I've used USRPs for radio astronomy for years, so, yeah :) > > But I think with a customized image you could send 100Msps of real-mode-only > data down the wire... > > > -- > Marcus Leech > Principal Investigator > Shirleys Bay Radio Astronomy Consortium > http://www.sbrac.org > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GRC Fails to Display QT/WX Elements
On Thu, Jun 20, 2013 at 09:55:29PM -0500, Crypto.Troop wrote: > > I would like to stay with the latest GNURADIO simply to support my > HackRf board, in which the HackRf gr-osmosdr library seems to only > support the latest version. I tried with 3.6.5 and it failed to > compile... The gr-osmosdr repo has a gr3.6 branch for compatibility with GNU Radio 3.6. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP for physics project
> Regardless of whether you use the stock FPGA design or a custom one to do raw > data capture you are going to run up against the basic limits of 1GB/s > i.e 1Gb/S = 125MB/S = 62.5M 16bit samples/S > > The stock image is always going to want to send an I and Q channel, and has > the option of either 25MSamples/S @ 16bit or 50MSample/S @ 8bits and it's > going to pass the data through either 1 or 2 low pass FIR filters to decimate > to that data rate. > Even if you write a very custom FPGA design that packs 14bit data efficiently > and uses a raw UDP transport, you would be doing well to achieve 70MSample > @14bits over ethernet since real world performance never quite matches > theoretical. Thanks for your reply, I think I'll go ahead and order one to play with. I can live with 25MSamples/S for the moment and try and do some compression later. The I/Q stuff is more worrying, I guess I can always convert back to real in software on the host? It would be nicer not to have to so I may try looking at the Verilog and see how easy it would be to make these changes. Alternatively if there's a contractor out their who would be interested in doing this please mail me! ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] GUIs are not showing in 'master'
This fixed my "GUI issues" ... thanks a bunch for tracking down the error and pushing a fix for it so quickly! I appreciate it. On Sat, Jun 22, 2013 at 1:19 PM, Johnathan Corgan wrote: > On Fri, Jun 21, 2013 at 6:48 PM, Michael Dickens wrote: > >> >> So fixing the init call as above with "attribList=attribList" should fix a >> bug that might effect all implementations. If the prior commit worked on >> OSX, and I believe it did, then this version should too since all it does >> differently is fix this one bug. Nice catch, Sylvain! >> >> I would encourage other Linux & Windows users to try out this fix, to make >> sure it works across all major platforms. - MLD > > > I've restored Balint's original fix, added the one line change from Sylvain, > and merged it into maint/master. > > > -- > Johnathan Corgan > Corgan Labs - SDR Training and Development Services > http://corganlabs.com > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
