Re: [Discuss-gnuradio] Calculating additive noise power for known signal

In a real system the signal would be a preamble, which would normally be used for synchronization purposes at the receiver end (For example PLC system). "I'm not quite sure what you mean by "cyclic noise", but the example you give is 50 Hz (or 60 Hz) hum, so a narrowband interference." Cyclic

[Discuss-gnuradio] Transmit and Receive hopping Sequence in FHSS (using gr-spread module) mismtach

HI All, I am using gr-spread module to transmit a signal using FHSS. When I receive the FHSS signal, the received signal has a completely different hopping sequence as from the transmitted one. I am using USRP N210 for transmission and

Re: [Discuss-gnuradio] Calculating additive noise power for known signal

Great answer. I wish I could upvote it! There should be a GNU Radio Stack Exchange type thing. Rich On Tue, Aug 23, 2016 at 3:07 PM, Andy Walls wrote: > On Tue, 2016-08-23 at 12:00 -0400, discuss-gnuradio-requ...@gnu.org > wrote: > > Message: 7 > > Date: Mon, 22

Re: [Discuss-gnuradio] Calculating additive noise power for known signal

On Tue, 2016-08-23 at 12:00 -0400, discuss-gnuradio-requ...@gnu.org wrote: > Message: 7 > Date: Mon, 22 Aug 2016 18:14:29 -0700 (MST) > From: Paul Creaser > > I've just started studying methods used to detect and then filter out/remove > cyclic noise from known signals.

Re: [Discuss-gnuradio] [GSoC] gr-inspector update / ask for feedback

Hi Sebastian - Thanks for putting together this final blog post, and the promo video is great. It's great to hear that you hit all of your milestones, and I'm very happy to see a successful v1.0.0 release in CGRAN. Excellent work! Nice work putting together a good selection of example flowgraphs

Re: [Discuss-gnuradio] git fetch failing

Thanks, Ron. I repointed origin to github, and reset the branches to origin/, then it updated just fine. Appears the content on github works fine, and something fishy with the content on gnuradio.org -- Tom, N5EG On Tue, Aug 23, 2016 at 3:52 AM, Ron Economos wrote: > This

Re: [Discuss-gnuradio] pybombs gnuradio vs gnuradio-default

I think a more appropriate solution might be to allow re-running `pybombs prefix init`, and have that continue where it stopped. I agree, that would make the most sense from my end. Andrej, can you submit an issue for this on github? Thanks so much!

[Discuss-gnuradio] GSoC '16 - Improve/Integrate PyBOMBS & CGRAN - Final submission

Hi all, I have summarized my work during the GSoC program at [1]. Watch out for release announcements soon. Cheers, Ravi Sharan B A G [1] - http://ninjacomics.github.io/radioblogr/2016/08/gsoc_final_eval.html ___ Discuss-gnuradio mailing list

Re: [Discuss-gnuradio] Attribute error: and support with external class and header files

I've had bad luck just putting my own headers in OOT modules. The way I do things now is to use gr_modtool add and select 'noblock'. Then just remove the grc XML file created. Seems that YourModuleName_API is needed before structs and classes or it doesn't get seen by Swig. Could be wrong

Re: [Discuss-gnuradio] pybombs gnuradio vs gnuradio-default

On 08/23/2016 05:56 AM, Andrej Rode wrote: > Hello Jason, > >> Why is there two different installs? > > Basically gnuradio is the correct install for a pure gnuradio install. > gnuradio-default is more or less a meta-package installing gnuradio and > gr-osmosdr. This is most convenient if you

Re: [Discuss-gnuradio] Discuss-gnuradio Digest, Vol 165, Issue 24

he length of the string we got from IOHIDDeviceGetProperty(). > range.length > has to be the length of that source string, not that of the destination > buffer.? > > Might anyone be able to help? > > Thank you in advance for any help. > > > > Kind regards, > >

Re: [Discuss-gnuradio] Microwave Link Demodulation

Right, I should have mentioned that high rates are very CPU-intense. In fact, it's not seldom that getting 50MS/s into a PC and processed occupies a single CPU core completely. After all, we're talking about 1.6 Gb/s in pure samples, before they're even converted to what likely is floating point,

Re: [Discuss-gnuradio] Microwave Link Demodulation

Agree with all of Marcus' comments. However, the 150 to 326 Mbps requirement may be quite difficult. To put things in perspective, my run of the mill 3 GHz E5-1607 Xeon x86 processor can just barely decode 16QAM DVB-T at 16 Mbps. You'll probably need a high-end CPU with as many cores as you

Re: [Discuss-gnuradio] Microwave Link Demodulation

Hi Ihab, > 1) Frequency range: 1.5 - 38 GHz since the B205 mini only goes up to 6 GHz, you're bound to use an external mixer. The device you chose for that will completely depend on your specific application's needs. Also note that finding something that works as well at 1.5 GHz as it does on 38

Re: [Discuss-gnuradio] Microwave Link Demodulation

Hi Ron, 1) Frequency range: 1.5 - 38 GHz 2) Bandwidth range : 2 - 56 MHz 3) Modulation : Qpsk - 256 QAM 4) Data rate range : 150Mbit/s - 326Mbit/s. 5) Error correction method : i thinks it is FEC. Ihab On 22 August 2016 at 12:33, Ihab Zine wrote: > Hi All, > > I'm

Re: [Discuss-gnuradio] pybombs gnuradio vs gnuradio-default

Hello Jason, > Why is there two different installs? Basically gnuradio is the correct install for a pure gnuradio install. gnuradio-default is more or less a meta-package installing gnuradio and gr-osmosdr. This is most convenient if you want to use gnuradio with a hardware device not supported

[Discuss-gnuradio] pybombs gnuradio vs gnuradio-default

What is the difference between the two? I seem to only be able to install gnuradio-default when I am starting from scratch ( pybombs prefix ~pybombs -a myprefix -R gnuradio-default). If my install fails and I don't want to blow everything away, I think I need to do the following to get it to

Re: [Discuss-gnuradio] git fetch failing

This is just a personal preference, but I always use Github instead of gnuradio.org. Github saturates my 188 Mbps Internet connection, and a git clone from gnuradio only takes a few moments. git clone --recursive https://github.com/gnuradio/gnuradio.git Ron On 08/22/2016 06:57 PM, Tom

[Discuss-gnuradio] Attribute error: and support with external class and header files

Hello all, I have written a c++ code and I wish to implement as a block in GNURadio. I created a module (named "newblocks") and a block (named "my_client) and made appropriate changes. The thing is, I have many class and header files for my c++ code, for eg. Protobuf. I put those files in a

Re: [Discuss-gnuradio] Funcube Dongle Broken in GUN Radio?

Hi Sean, could you tell us your GNU Radio version? Best regards, Marcus On 23.08.2016 11:24, Sean Sharkey wrote: > Morning Everyone. > > > I’m having trouble getting the original Funcube Dongle recognised in > GNU Radio and GNU Radio Companion. > > For example when I run Companion and try to

[Discuss-gnuradio] Funcube Dongle Broken in GUN Radio?

Morning Everyone. I’m having trouble getting the original Funcube Dongle recognised in GNU Radio and GNU Radio Companion. For example when I run Companion and try to select FCD as the source I get an error saying that the “Port is not connected.” My computer recognises the FCD and any number