[Discuss-gnuradio] Runtime error

Hi Everyone. can u please let me know how to solve runtime error issue and also somtimes device serial number not found. Thanking you Regards: Khwaja ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org

Re: [Discuss-gnuradio] runtime error while running flowgraph

 I am trying to implement this discussion:[Discuss-gnuradio] Change frequency in USRPsource automatically(https://lists.gnu.org/archive/html/discuss-gnuradio/2016-03/msg00402.html). My objective is to create a block which changes the frequency automatically in steps of 2e6, starting from

Re: [Discuss-gnuradio] runtime error while running flowgraph

Have you first registered the "clock" message port? This looks like you're trying to set a handler for a message port that doesn't exist. Also, when asking for help, it's usually very helpful to have your *exact* code somewhere, not a reference to code that is /similar/. Best regards, Marcus On

[Discuss-gnuradio] runtime error while running flowgraph

Icreated a block using gr_modtool add -l python -tsync command, whereI tried to implement this discussion:[Discuss-gnuradio] Change frequency in USRPsource automatically(https://lists.gnu.org/archive/html/discuss-gnuradio/2016-03/msg00402.html) And thenused this block in a flowgraph

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

Guilty as charged, Marcus :-) Thanks again for your help! On Tue, Jan 31, 2017 at 12:53 PM, Marcus Müller wrote: > Hi Sonny, > > that's why I explicitly asked you to confirm you didn't have multiple > versions installed before we went down the detailed backtrace

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

Hi Sonny, that's why I explicitly asked you to confirm you didn't have multiple versions installed before we went down the detailed backtrace route... Ah well, I'm happy it's sorted out now :) Cheers, Marcus On 31.01.2017 17:59, Sonny Rajagopalan wrote: > Thanks, Kevin! > > I think that was

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

Thanks, Kevin! I think that was the issue. I had, in my early days of learning about SDR, installed another version of gnuradio. Also, I was not calling the pybombs-installed gnuradio correctly. Instead of $ pybombs run gnuradio-companion I was calling it like so: $ gnuradio-companion That is

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

On Mon, Jan 30, 2017 at 11:12 AM, Sonny Rajagopalan < sonny.rajagopa...@gmail.com> wrote: > RuntimeError: list contains invalid format! > FWIW, I've seen this error before, and if I remember correctly it's a symptom of multiple versions installed (such that the GR Python code is not the same

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

Try the enclosed Qt version of your HelloWorld.grc: HackRFHelloWorld-Qt.grc But before you do, press the small blue button on the far left hand side of the HackRF - it's the reset button. After you hit the reset button, there should be 2 green, 1 orange, and 1 red LED lit. If a red dot

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

Attached. On Mon, Jan 30, 2017 at 4:10 PM, Marcus Müller wrote: > Huh. Can you share your top_block.py with us? > > Best regards, > > Marcus > > On 01/30/2017 10:00 PM, Sonny Rajagopalan wrote: > > Hi Marcus, > > Appreciate your time with this. This output was observed

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

Huh. Can you share your top_block.py with us? Best regards, Marcus On 01/30/2017 10:00 PM, Sonny Rajagopalan wrote: > Hi Marcus, > > Appreciate your time with this. This output was observed when I > followed your instructions: > > linux; GNU C++ version 4.8.4; Boost_105400;

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

Hi Marcus, Appreciate your time with this. This output was observed when I followed your instructions: linux; GNU C++ version 4.8.4; Boost_105400; UHD_3.11.0.git-59-g52ca2e0b gr-osmosdr v0.1.x-xxx-xunknown (0.1.5git) gnuradio 3.7.10 built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

Hi Sonny, please always make sure to reply to the list! Ah, shoot, it backtraces the wrong thread :/ I can help you get a proper backtrace, but maybe we'll just take it the other way around: Can you please make a clean, new flowgraph, use the osmocom source. Connect it to a null sink instead of

Re: [Discuss-gnuradio] RunTime error in runtime_swig.py

Hi Sonny, that's unusual. Can you run gdb -ex run -ex bt --args python2 '/mymachine/sdr/gnuradioProjects/flowGraphsFromGRC/top_block.py' and copy & paste the output backtrace? Ideally, we'd see *exactly* what crashes where. Best regards, Marcus On 01/30/2017 08:12 PM, Sonny Rajagopalan

[Discuss-gnuradio] RunTime error in runtime_swig.py

Hello, I have a simple flow graph as shown (from this video tutorial http://greatscottgadgets.com/sdr/1/): [image: Inline image 1] The *.py that is created is attached. The code crashes with the following error: Generating: '/mymachine/sdr/gnuradioProjects/flowGraphsFromGRC/top_block.py'

Re: [Discuss-gnuradio] Runtime error on Mac OSX 10.7

Hi Matthew - Hmm ... well, testing on 10.7 will be tricky for debugging purposes. It looks like you installed GR via MacPorts ... yes? This looks like the same issue as < https://trac.macports.org/ticket/53236[1] >, yes? OK; I'm working on fixing this; hopefully this afternoon. Cheers! - MLD On

[Discuss-gnuradio] Runtime error on Mac OSX 10.7

I get the following error when I try to run anything that uses gnuradio, such as gqrx, gnuradio-companion or uhd_rx_nogui. $ uhd_rx_nogui Traceback (most recent call last): File "/opt/local/bin/uhd_rx_nogui", line 23, in from gnuradio import gr, gru, uhd, audio File

[Discuss-gnuradio] Runtime error - Empty Device Address in GRC Flowgraph build

Hello, After installing GRC into Ubuntu 15.05 64bit I get the following error when trying to run a GRC flow graph example:- --- RuntimeError: LookupError: KeyError: No devices found for

Re: [Discuss-gnuradio] Runtime error - Empty Device Address in GRC Flowgraph build

On 08/15/2015 06:58 AM, Mark wrote: Hello, After installing GRC into Ubuntu 15.05 64bit I get the following error when trying to run a GRC flow graph example:- --- RuntimeError:

Re: [Discuss-gnuradio] Runtime error - Empty Device Address in GRC Flowgraph build

When running uhd_find_devices, do you happen to use sudo? On 08/15/2015 07:30 PM, Marcus D. Leech wrote: On 08/15/2015 06:58 AM, Mark wrote: Hello, After installing GRC into Ubuntu 15.05 64bit I get the following error when trying to run a GRC flow graph example:-

[Discuss-gnuradio] Runtime Error

I am using DVB-T dongle RTLSDR2832U with gnu radio, i have installed all the required files, but when i compile my flowgraph I get an error. Runtime Error:Failed to open rtlsdr device. What is the problem and its solution?? Sohaib bin Altaf pakistan

Re: [Discuss-gnuradio] Runtime Error

Hello Sohaib, from http://sdr.osmocom.org/trac/wiki/rtl-sdr: If the device can't be opened, make sure you have the appropriate rights to access the device (install udev-rules from the repository, or run it as root). The osmo project has for your conveniences generated a rule that assigns

[Discuss-gnuradio] Runtime error from boost 1.52 issue on OSX

I'm writing to describe an issue, and to provide a workaround, related to gnuradio with boost 1.52. I built the current gnuradio repo from source on Mac OSX 10.6.8 (satisfied dependencies using MacPorts). The build went fine, but only 21% of the tests were passed with make test. The error was

Re: [Discuss-gnuradio] Runtime error from boost 1.52 issue on OSX

Hi Michael - Quite interesting. I wonder if the Boost folks know about this issue; I doubt it was introduced by MacPorts since mostly they just replicate the project's functionality. I had seen some issues recently, and had wondered about them; I'll definitely check into this. Thanks! - MLD

Re: [Discuss-gnuradio] Runtime error from boost 1.52 issue on OSX

After a bit of sleuthing, it turns out that this was a general Boost issue, not just on OSX, discussed on their email list here http://boost.2283326.n4.nabble.com/thread-thread-join-throws-in-1-52-0-td4638380.html , in their tickets here https://svn.boost.org/trac/boost/ticket/7669 , and

Re: [Discuss-gnuradio] Runtime error from boost 1.52 issue on OSX

On Sat, Dec 29, 2012 at 11:22 AM, Michael Dickens m...@alum.mit.edu wrote: After a bit of sleuthing, it turns out that this was a general Boost issue, not just on OSX, discussed on their email list here http://boost.2283326.n4.nabble.com/thread-thread-join-throws-in-1-52-0-td4638380.html,