Re: [Discuss-gnuradio] Hardware for MIMO & Beamforming Experiment

2019-06-13 Thread Kyeong Su Shin
Hello Evariste: If 2 channels are sufficient, you can probably get away with USRP B210s (which is expensive but superior) or LimeSDRs. You can also use a MIMO cable to pair up two USRP N210s together. If you need more channels, things get a bit expensive. You will need to consider USRP N3xx

Re: [Discuss-gnuradio] Hardware for MIMO & Beamforming Experiment

2019-06-13 Thread Ali Dormiani
Our lab is using USRP N310's with an external frequency synth ($500), a TI dev board splitting chip ($200?) and an external 10 MHz selenium clock ($2k). The set up is very very good but extremely expensive as well. After paying for RF cables and a host server, we are roughly getting 1 channel per

Re: [Discuss-gnuradio] Calling a function after every N samples

2019-06-13 Thread Michael Dickens
Hi Kevin - Maybe use the tagged_stream or a PDU or vectorized data? There are various ways to do what you want that will guarantee N samples that you could then trigger a function call on. The better one to use really depends on what you actually want to do once you have your N samples. - MLD O

[Discuss-gnuradio] Hardware for MIMO & Beamforming Experiment

2019-06-13 Thread eva some
Hi dear community members! I want to run experiments using MIMO and/or beamforming techniques with open source. However, I am getting stuck with hardware. Traditionally, I used USRPs N210 for experiments. I have only two. Is there any cheap hardware that can support MIMO & beamforming application

[Discuss-gnuradio] Calling a function after every N samples

2019-06-13 Thread Kevin Lee
Hello all, I'm working on a project that requires that I synchronously issue a command to the sink I wrote after processing every "N" samples. In my reading, I came to the understanding that a good way to do this would be to use tagged streams or PDUs with message passing. I've read through the Gu

Re: [Discuss-gnuradio] Live fm detection gr-inspector

2019-06-13 Thread Sebastian Müller
I just noticed something else: The USRP sample rate is set to 500kHz, not 20MHz. So you are only looking at 2.5 % of the target spectrum! It is also possible, that there are just no signals in that particular section. Best, Sebastian Müller gse...@gmail.com PGP ID DC2AA3EE Am 13. Juni 2019 um 20

Re: [Discuss-gnuradio] Live fm detection gr-inspector

2019-06-13 Thread Sebastian Müller
Hi Daniel, from what you tell us, I conclude this is not an issue with gr-inspector but rather with generally receiving signals. If you use the QT GUI Sink for instance instead, you will see the same (empty) spectrum. I would recommend to try and get better reception, until you can distinguish sig

Re: [Discuss-gnuradio] Gnuradio life cycle

2019-06-13 Thread Daniel Andres Palacios
thank you, that definitely helps On Tue, Jun 11, 2019 at 12:46 PM Müller, Marcus (CEL) wrote: > Hi Daniel, > > no, that's not right. > > In your program, whatever that is, if it wants to use GNU Radio: > > You set up a bunch of blocks – to even instantiate them, their > constructors must return

Re: [Discuss-gnuradio] Store in a variable the output of the grinspector's blocks.

2019-06-13 Thread Daniel Andres Palacios
Thank you. I tried, and it worked Cheers On Wed, Jun 12, 2019 at 11:48 AM Müller, Marcus (CEL) wrote: > Oh, or try > > from pmt.pmt_to_python import pmt_to_python as p2p > > vector = p2p(message) > for elem in vector: > do_stuff_with_elem > > > On Wed, 2019-06-12 at 10:56 -0500, Daniel Andr

Re: [Discuss-gnuradio] RTTY receiver

2019-06-13 Thread Ron Economos
Just FYI, the pulseaudio_pa_sink block is part of: https://github.com/bitglue/gr-pulseaudio Ron W6RZ On 6/12/19 03:59, ba...@dcsmail.net wrote: 3) When I loaded 'examples/rtty_demod.grc', there was a missing block 'pulseaudio_pa_sink'. Where is it, and what does it do? Since it didn't seem di

Re: [Discuss-gnuradio] RTTY receiver

2019-06-13 Thread Barry Duggan
Hi Kyeong and all the others who helped me on this issue! Ron Economos identified the basic problem: it depends on how gnu radio was loaded as to whether to use '/usr/local' or '/usr'. So I tried 'cmake -DCMAKE_INSTALL_PREFIX=/usr ../' and it works :) Also, per your suggestion, I rebuilt witho

Re: [Discuss-gnuradio] Serial to parallel conversion

2019-06-13 Thread rear1019
On Thu, 13 Jun 2019 at 09:22:21 +0200, Sneha vasan wrote: > Yes I am implementing the OFDM receiver. > > So the idea is to do the serial to parallel conversion of the received > signal at USRP source, So my question was, in order to do so can I use > vector to streams block?? . As per the above sug

Re: [Discuss-gnuradio] RTTY receiver

2019-06-13 Thread CEL
On Wed, 2019-06-12 at 16:26 -0400, Barry Duggan wrote: > Hi Marcus, > > I wasn't careful in getting the filenames right, but the intent and the > execution were there :) > > If you look at bitglue/gr-radioteletype/lib/baudot_encode_bb_impl.h, the > tables have a '-1' to indicate characters whic

Re: [Discuss-gnuradio] Serial to parallel conversion

2019-06-13 Thread Sneha vasan
Thank you so much for the response. Yes I am implementing the OFDM receiver. So the idea is to do the serial to parallel conversion of the received signal at USRP source, So my question was, in order to do so can I use vector to streams block?? . As per the above suggestion the block does not rea