[Discuss-gnuradio] Changing data type of custom block

Hello All I have a custom sink block that I want to be able to a vector input of length 1024, however, I can't seem to change the data type of the block. The code I'm using is the following in which the data type is float and I've made the vector length equal to 1024, a parameter. The flow graph

Re: [Discuss-gnuradio] Project Call February this Thursday!

Sorry, forgot the most important info. It's at 10 AM Pacific / 1 PM Eastern / 19:00 CET. -- M On 02/12/2018 12:04 PM, Michael Dickens wrote: > Hi Martin - Some good news there in the agenda; I'm looking forward to > hearing more! > > Is this event starting at 1 PM / US / Eastern, which would

Re: [Discuss-gnuradio] Basic beginner flowgraph with C++ API

Thank you very much Markus for your advice. Best regards, Álvaro 2018-01-24 22:52 GMT+01:00 Ron Economos : > Here's an example. > > https://github.com/csdvb/dvbs2_tx > > Ron > On 01/24/2018 08:16 AM, Álvaro Cebrián Juan wrote: > > Hello everyone, > > I have no prior knowledge

[Discuss-gnuradio] [PyBOMBS] TypeError: cannot use a string pattern on a bytes-like object

Hello everyone, I was following these instructions to install some dependencies using PyBOMBS, but when I add a list of default recipes with the command: $ pybombs recipes add-defaults I get the following error:

[Discuss-gnuradio] [GSOC18] GNU Radio accepted as mentoring organization!

Hi all, we've got great news: GNU Radio got accepted (again) by Google as mentoring organization for this year's Google Summer of Code! So, what's the next step? If you're a student and interested in participating in GSoC, head over to our ideas list [0] and see if there's a project that

Re: [Discuss-gnuradio] Project Call February this Thursday!

Hi Martin - Some good news there in the agenda; I'm looking forward to hearing more! Is this event starting at 1 PM / US / Eastern, which would be 10 AM / US / Pacific? Or is it 2 / 11? I still get them confused ... Cheers! - MLD On Mon, Feb 12, 2018, at 1:34 PM, Martin Braun wrote: > this

[Discuss-gnuradio] Project Call February this Thursday!

Hi all, this Thursday, we'll have our usual monthly project call. We have a lot to talk about, such as the leadership change, and Google Summer of Code. We'll be collecting agenda items here: https://wiki.gnuradio.org/index.php/Call20180215 I'll post the link to call in or just listen here, and

Re: [Discuss-gnuradio] Triggering between two transmitters

This should work: - Provide a common clock and time reference to the B210s (e.g., using an Octoclock, but any other reference might work through a 2-way splitter). - Set your devices to the same time as part of your app initialization. You will need to write custom code for this, basically, you

Re: [Discuss-gnuradio] DTV module support and cross compilation for Ettus E312

Did you only cross-compile GNU Radio, or also UHD? You don't really need to touch the latter, if that's the case. -- M On 02/07/2018 08:54 PM, kailash kumar wrote: > Hi, > > I am trying to compile dtv module for gnuradio on E312 target hardware. > > I am following below grc code for

Re: [Discuss-gnuradio] gr-radar and FMCW radar imlementation for measuring range with high resolution

Tilen, gr-radar is probably still a great starting point. I was playing around with it just recently, and will be contributing some fixes to gr-radar in the next few week. B210 support, I think, is not natively available. I was going to characterize the TX/TX leakage, I'm not entirely sure how

Re: [Discuss-gnuradio] Analog Bandwidth of UHD Block

On 02/09/2018 01:26 PM, Müller, Marcus (CEL) wrote: > To be a bit more explicit: like the product page says, you **cannot** > use the UBX-160 in an N210. You need an X3x0 if you want to use that! Well, you can, but it's not alias-free. -- M > > If you're however interested in smaller bandwidths

Re: [Discuss-gnuradio] Discuss-gnuradio Digest, Vol 184, Issue 11

both simulation and > > currently, I'm testing the block over the air using the N210. The > > block performed correctly in simulation, however, over the air, the > > block gives a response of "no signal present" regardless of the input. > > The error message " python:

Re: [Discuss-gnuradio] Customized Block Giving Incorrect Output

Just another thought: Why convert every single FFT output vector from linear to dB with a logarithm (that's a very complicated function!) just to then compare it to a threshold, if you could also just convert the threshold to linear once? Best regards, Marcus On Mon, 2018-02-12 at 10:21 -0500,

Re: [Discuss-gnuradio] Customized Block Giving Incorrect Output

In GRC, you open the "complex to ||^2" block settings & set the vector length to whatever you want. I'd advise using a variable that's defined in GRC, and then use it for any blocks that require the vector setting; that way you can change the variable value & all blocks are updated with it. Hope

Re: [Discuss-gnuradio] Customized Block Giving Incorrect Output

Michael Thanks for the response. That's exactly what I'm trying to accomplish. You mention the "complex to ||^2 can be vectorized. My question is how exactly do you go about doing that? Tellrell On Mon, Feb 12, 2018 at 9:42 AM, Michael Dickens wrote: > Hi Tellrell -

Re: [Discuss-gnuradio] Customized Block Giving Incorrect Output

Hi Tellrell - So I'm not sure about the non-sim error / issue, but to me the larger question is: what are you really trying to do? If you're trying to detect energy via converting an FFT vector output to dB and thresholding, on a specific number of items per FFT, then why not just use vectors