Re: [Discuss-gnuradio] ZMQ REQ / REP naming Swap?

2016-07-28 Thread Francisco Albani
Michael, I found the need to do the same for some applications. I also needed to choose between bind and connect (I made this a parameter of my block). Wouldn't be better to have just one sink and one source with selectable options, like: * socket_type: REP/REQ/SUB/PUB/PUSH/PULL * method: bind /

Re: [Discuss-gnuradio] ZMQ REQ / REP naming Swap?

2016-07-28 Thread Michael Dickens
On Thu, Jul 28, 2016, at 06:44 PM, Johnathan Corgan wrote: > The ZMQ REQ/REP dataflow has the receiving end REQuest data from the > sending end when needed, which REPlies with a packet. It's a form of > flow control. > > From the GNU Radio perspective, streams flow into GNU Radio sinks to > exit

[Discuss-gnuradio] gr-radar make issue

2016-07-28 Thread Abhinav Jadon
Hi , I use an Ubuntu 14.04 machine. 64 bit processor. UHD version 003.010 | QWT version 6.0.0 | Boost version 1.54 When i run the cmake command, everything gets built just fine (no errors). But when I open the flowgraphs in the examples folder, there are some gr-radar blocks that are not

[Discuss-gnuradio] setter of the OOT module parameters cannot access from the top block

2016-07-28 Thread Damindra Bandara
Hi, I am trying to create an OOT module using gr_modtools. I followed the gnuradio tutorials and gr_modtool guidelines and the basic functionality of the block work fine. I need to change a variable of the OOT module from the top block. To do it I added a setter function. I modified the impl.cc

Re: [Discuss-gnuradio] ZMQ REQ / REP naming Swap?

2016-07-28 Thread Johnathan Corgan
On Thu, Jul 28, 2016 at 12:20 PM, Michael Dickens wrote: > OK. I think the issue is that's not how ZMQ is designed to work with > respect to REQ/REP. I think it's designed to do "sink -> REQ -> ZMQ -> > REP -> source", so that the REQ is a sink & REP is a source. In

[Discuss-gnuradio] OFDM sync word generator

2016-07-28 Thread Suman Bhunia
Hi! I was wondering if there is any code block available to generate suitable sync words for OFDM transceivers. I want to use 512, 1024 and 2048 as FFT length for OFDM. Any help is much appreciated. == Thanks and Regards, Suman Bhunia PhD candidate in CSE University of

Re: [Discuss-gnuradio] Questions on StackOverflow

2016-07-28 Thread Martin Braun
Let me emphasize this. The mailing list is terrible for searching, and stack overflow is highly optimized to show the correct results, *if* we have enough Q's and A's on there. This is also about the efficiency of this list. The aforementioned bad indexing means we'll get a lot of repeated

Re: [Discuss-gnuradio] ZMQ REQ / REP naming Swap?

2016-07-28 Thread Michael Dickens
On Thu, Jul 28, 2016, at 03:11 PM, Sylvain Munaut wrote: > > But this model doesn't work for the REP / REQ in Figure 2 > > "Request-Reply". I would expect the ZMQ REQ to be a GR sink but instead > > if is a source; likewise, I'd expect the ZMQ REP to be a GR source & it > > is instead a sink. > >

Re: [Discuss-gnuradio] ZMQ REQ / REP naming Swap?

2016-07-28 Thread Sylvain Munaut
> But this model doesn't work for the REP / REQ in Figure 2 > "Request-Reply". I would expect the ZMQ REQ to be a GR sink but instead > if is a source; likewise, I'd expect the ZMQ REP to be a GR source & it > is instead a sink. > > The internal coding is consistent with the external naming; I

[Discuss-gnuradio] ZMQ REQ / REP naming Swap?

2016-07-28 Thread Michael Dickens
I'm trying to work with the ZQM REQ / REP message blocks while learning about ZMQ. From their overview guide < http://zguide.zeromq.org/page:all >, they define various graphs where the interconnects are the ZMQ connections. Thus, for example, in Figure 4 "Publish-Subscribe", the PUB would be GR

[Discuss-gnuradio] SWIG std::vector issue

2016-07-28 Thread Dave NotTelling
I have a utility lib in C++ created with 'gr_modtool add noblock' that has a function that returns a vector of pmt::pmt_t values. I need to then be able to access the elements of that vector via Python. Right now I get the following error when using a for loop to iterate over the vector: