[Discuss-gnuradio] Using PyBOMBS to install gnuradio

Hi, Today I tried to install gnuradio in my Raspberry Pi. I encountered the following problems: A. In https://github.com/gnuradio/gnuradio/README.md, PyBOMBS with support of python 3.x: 1. Change the PYTHONPATH line in setup_env.sh, to just 3.x paths. *** Where is 'setup_env.sh'? I can't fi

[Discuss-gnuradio] Project Call Tomorrow!

Hi all, there'll be another project call tomorrow, at 10 AM Pacific, 19:00 CEST. Join us in IRC or Slack for the call link, or wait until we post the YouTube link for live streaming, or for watching later! -- Martin ___ Discuss-gnuradio mailing list Di

[Discuss-gnuradio] [announcement] GNU Radio 3.8 Release Candidate 1

Dear GNU Radio Community, tonight, we're releasing the first release candidate for the GNU Radio 3.8.0.0 release. You can find it on https://github.com/gnuradio/gnuradio/releases/tag/v3.8.0.0-rc1 and soon as a tarball on https://www.gnuradio.org/releases/gnuradio/ This is really a major step.

Re: [Discuss-gnuradio] USRP GNU radio receiver

To whom it may concern: I think there has been some miscommunications or misunderstandings here: the 'Offset' argument for the 'Signal Source' block is for the 'amplitude offset' of the signal, while what Marcus probably meant in his previous e-mail is the 'frequency offset' (you can use USRP'

Re: [Discuss-gnuradio] GRC/python to C transfer of cf information, frequency hopping with fosphor display and changing frequency extent

Hello Arthur: For the inter-process communication, maybe you can try using ZMQ sources/sinks (see: http://zeromq.org ). GNU Radio has dedicated blocks for that. I haven't used that for transferring pmt messages, but they should be able to do that. One question, though: is it necessary to use

Re: [Discuss-gnuradio] Calling general_work when one of the inputs are available

Hey folk, I can implement my purpose, when my block is called so frequenctly. It is called in every 5 ms in average. Log: time_span: 0.075296 ms, noutput_items: 4096 time_span: 0.017153 ms, noutput_items: 4096 time_span: 0.008007 ms, noutput_items: 4096 time_span: 0.008484 ms, noutput_items: 4

Re: [Discuss-gnuradio] USRP GNU radio receiver

Thank you very much! I sent the screenshot because in the oscilloscope there is not the offset. Instead, I would like to detect that. Thank you in advance. Simona Il giorno mer 17 lug 2019 alle ore 15:22 Müller, Marcus (CEL) < muel...@kit.edu> ha scritto: > 1. Never use a throttle with a hardwar

Re: [Discuss-gnuradio] USRP GNU radio receiver

1. Never use a throttle with a hardware block. GRC's log will actually shout at you that you shouldn't be doing that! 2. I must admit this is about as good as I'd expect. I of course can't infer temporal behaviour from screenshots. Best regards, Marcus On Wed, 2019-07-17 at 14:18 +0100, Simona Si

Re: [Discuss-gnuradio] OsmoSDR suddenly throwing List Contains Invalid Format after GR Update

FYI if anyone else runs into the same issue. Ended up blowing out the install prefix and rebuilding GNU Radio as a fresh install. Seems to have fixed the issue. On Tue, Jul 16, 2019 at 7:26 PM Michael Piscopo wrote: > Hi folks, > > Has anyone else started getting an error like this off of ma

Re: [Discuss-gnuradio] GNURadio File meta Sink performance.

That might very well be the case: 20 MS/s of 32bit float complex would amount to 1.280 Gb/s writing speed. Best regards, Marcus On Wed, 2019-07-17 at 10:35 +0530, SG wrote: > Hi all, > > I have been trying to capture data as well as meta data in file meta > sink in GNURadio. When I run my gr-

[Discuss-gnuradio] European GNU Radio Days videos

The videos of the European GNU Radio Days oral presentations and tutorials are now available online: Marcus' keynote presentation: https://mediacenter.ens2m.fr/videos/?video=MEDIA190710141050023 First day oral presentations (morning): https://mediacenter.ens2m.fr/videos/?video=MEDIA19071014294008