[Discuss-gnuradio] polar code example in GRC

2016-12-06 Thread JX
Hi, In GRC, I cann't run the polar code example. I found when I double click the block of polar code (any block of polar code), it just do nothing and then I can't run GRC. My GRC works well when I use the other modules. In another computer with the different version of GNU Radio, I have the

Re: [Discuss-gnuradio] Bug in GPS time reported by the USRP

2016-12-06 Thread Dan CaJacob
Hi Eugene, Please check that time stamp here: http://www.unixtimestamp.com/index.php It looks alright to me. It *is* reporting the correct time in a unix timestamp format. Maybe you are making a more subtle point about nomenclature? As in the GPS epoch is not the same as the Unix timestamp

Re: [Discuss-gnuradio] OS X Sierra complete build

2016-12-06 Thread Michael Dickens
Hi Greg - What usually works is the following: {{{ sudo port clean doxygen sudo port install doxygen sudo port clean gnuradio sudo port install gnuradio }}} If that fails, email me off-list & I'll help debug. - MLD On Tue, Dec 6, 2016, at 01:43 PM, Gregory Ratcliff wrote: > Just

[Discuss-gnuradio] Bug in GPS time reported by the USRP

2016-12-06 Thread Eugene Grayver
This is being posted to both GR and Ettus forums because both groups should be aware. The value returned by USRP.get_mboard_sensor('gps_time') is incorrect. It is NOT the GPS epoch, but is time relative to the UNIX epoch. Only off by a decade or so... 'GPS epoch time: 1481073287 seconds'

[Discuss-gnuradio] OS X Sierra complete build

2016-12-06 Thread Gregory Ratcliff
Just following instructions here: http://gnuradio.org/redmine/projects/gnuradio/wiki/MacInstall precisely for the first time with a new Mac. Xcode went well XQuartz went well Command line tools went well sudo port install

[Discuss-gnuradio] Decoding speed of the FECs in GR

2016-12-06 Thread hanwen
Dear all, I just want to know is there any benchmark results of the decoding speed of the various FEC decoder in GR: CC, turbo, LDPC and polar. How much Mbps can be achieved for these FECs respectively. Thanks in advance. Br, Hanwen ___

Re: [Discuss-gnuradio] Replacement for packet encoder/decoder

2016-12-06 Thread Damindra Bandara
Dear Marcus, Sorry, but for some reason I did not received this message from Tom and also missed it in the GNURadio thread. I will check it and see whether it will solve my problem. Thanks, Damindra On Tue, Dec 6, 2016 at 6:08 PM, Marcus Müller wrote: > Hi Damindra,

Re: [Discuss-gnuradio] Replacement for packet encoder/decoder

2016-12-06 Thread Marcus Müller
Hi Damindra, I'm a bit confused; you asked exactly this question[1] a while back and got this answer: > Please see this page: > > http://gnuradio.org/doc/doxygen/page_packet_data.html > > Tom > Now, we know that this is an important topic and that there's loads of stuff to do about the

[Discuss-gnuradio] Replacement for packet encoder/decoder

2016-12-06 Thread Damindra Bandara
Hi, I have noticed that packet encoder and decoder blocks are deprecated in latest GNURadio version. I appreciate if someone could let me know what are the replacement blocks for them. Thank you, Damindra -- Damindra Savithri Bandara, Ph.D. in Information Technology (Candidate) George Mason

Re: [Discuss-gnuradio] Add RFNoC FIFO

2016-12-06 Thread Marcus Müller
A NoC block should, as far as I can tell, always start with noc_block_. Best regards, Marcus On 12/06/2016 10:37 PM, Vishwesh Rege wrote: > Hi, > > What are the list of blocks that I can add? > > For example, > Looking at the list of blocks in usrp3_rfnoc/lib/rfnoc/Makefile.srcs > > From

Re: [Discuss-gnuradio] Add RFNoC FIFO

2016-12-06 Thread Vishwesh Rege
Hi, What are the list of blocks that I can add? For example, Looking at the list of blocks in usrp3_rfnoc/lib/rfnoc/Makefile.srcs >From these I could add noc_block_digital_gain (built successfully) but couldn't add chdr_fifo_large (running make X310_RFNOC_HLS_HG gave an error) How do I know

Re: [Discuss-gnuradio] Frequency multiplexing at baseband -filters introduce 'DDDDDDDDDDD'

2016-12-06 Thread Marcus Müller
Hi Damindra, basically, you'll have to parameterize the PFB channelizer with a prototype filter – imagine you had just one channel centered at 0 Hz in your input band, and design a low-pass filter that would select that. To illustrate: You've got something like ^S - |

Re: [Discuss-gnuradio] Segfault with volk_32fc_32f_dot_prod_32fc_a_avx

2016-12-06 Thread Marcus Müller
Hi, hm, you're right, the only way that can happen is if either the input or the tap pointers are invalid; strange. Since the line in question, 465 out[i+d_out_idx] = d_filters[d_filtnum]->filter([count+d_out_idx]); in pfb_clock_sync_ccf.cc isn't all that suspicious, let's harass GDB

Re: [Discuss-gnuradio] Segfault with volk_32fc_32f_dot_prod_32fc_a_avx

2016-12-06 Thread West, Nathan
On Tue, Dec 6, 2016 at 1:24 PM, devin kelly wrote: > I changed my volk_config like so > > volk_32fc_32f_dot_prod_32fc generic generic > > And I still get a segfault: > > gdb python core.8035 > > . > > Program terminated with signal 11, Segmentation fault. > #0

Re: [Discuss-gnuradio] Segfault with volk_32fc_32f_dot_prod_32fc_a_avx

2016-12-06 Thread devin kelly
I changed my volk_config like so volk_32fc_32f_dot_prod_32fc generic generic And I still get a segfault: gdb python core.8035 . Program terminated with signal 11, Segmentation fault. #0 0x7f116379277f in volk_32fc_32f_dot_prod_32fc_generic (result=0x56de260, input=0x7f1126cac680,

Re: [Discuss-gnuradio] Segfault with volk_32fc_32f_dot_prod_32fc_a_avx

2016-12-06 Thread devin kelly
It's a bit of both. The segfault usually happens on packet between packets 2 and 3 (I send one packet per second on my transmitter) but sometimes will happen a few packets later. It also always segfaults, I've gotten it to segfault about 20 times or so. On Tue, Dec 6, 2016 at 12:24 PM, West,

[Discuss-gnuradio] Pybombs problems resolved

2016-12-06 Thread Robert McGwier
Something installed python under a directory called miniconda. I have not yet tracked that down but gnuradio and pybombs now work. Apologies to Martin, et. al. for wasting their time on my silly too complex installation. Bob -- Bob McGwier Founder, Federated Wireless, Inc Founder and

Re: [Discuss-gnuradio] Reg: gr-ieee 802.11 and wireshark settings for commercial NIC

2016-12-06 Thread Sumit Kumar
On Tue, Dec 6, 2016 at 4:58 AM, Bastian Bloessl wrote: > Hi, > > On 5 Dec 2016, at 23:08, sumit kumar wrote: > I mean the wireshark dint detect transmission from gr-ieee 802.11 > transmitter also apart from my custom build

Re: [Discuss-gnuradio] Segfault with volk_32fc_32f_dot_prod_32fc_a_avx

2016-12-06 Thread West, Nathan
Honestly, my money would be on GCC 4.8.5 being less buggy than 6.2, but that's a separate topic. You can configure VOLK to not use this protokernel and there's some documentation on how to do it here: http://gnuradio.org/doc/doxygen/volk_guide.html#volk_tuning This is fairly concerning though...

Re: [Discuss-gnuradio] Segfault with volk_32fc_32f_dot_prod_32fc_a_avx

2016-12-06 Thread devin kelly
OK, I tried a brand new GR/Volk install and still had the same problem. So no problem with re-linking Volk to GR. Could this be an issue with Volk on GCC 4.8.5? The newest GCC is 6.2 so 4.8.5 is pretty old, though the newest for Red Hat 7. Is there any way to reconfigure volk to not use

[Discuss-gnuradio] Max PMT Size

2016-12-06 Thread Dave NotTelling
I seem to remember asking this question once before and being told that the only way to increase the max size of a PMT object is to set a define in a header file before compilation. Is this size limit only applicable to the PDU to Tagged Stream block? Can a PMT output to another PMT input be

Re: [Discuss-gnuradio] rx_time tag after drop

2016-12-06 Thread Meelis Nõmm
> > > I guess this leads to the core question. What does the offset show? > > 1. sample number related to the GnuRadio stream or > > 2. sample number related to the USRP stream? > > There is no offset. The tag is the absolute time of the sample > (rx_time). Ore are we speaking about different

Re: [Discuss-gnuradio] OS X Sierra complete build

2016-12-06 Thread Michael Dickens
Hi Greg - what usually works is the following: {{{ sudo port clean doxygen sudo port install doxygen sudo port clean gnuradio sudo port install gnuradio }}} If that fails, email me off-list & I'll help debug. - MLD > On Dec 6, 2016, at 7:08 AM, Gregory Ratcliff wrote: > > Just

[Discuss-gnuradio] OS X Sierra complete build

2016-12-06 Thread Gregory Ratcliff
Just following instructions here: http://gnuradio.org/redmine/projects/gnuradio/wiki/MacInstall precisely for the first time with a new Mac. Xcode went well XQuartz went well Command line tools went well sudo port install

Re: [Discuss-gnuradio] gr-ieee 802.11 and integration with linux stack (wpa_supplicant)

2016-12-06 Thread Bastian Bloessl
Hi, On 12/06/2016 12:35 PM, Manolis Surligas wrote: Hi all, we have done it two years ago as part of my master thesis and it works like a charm! The SDR IEEE 802.11 implementation can be configured as AP using hostapd or adhoc via the network manager. We had some problems making it work as a

Re: [Discuss-gnuradio] gr-ieee 802.11 and integration with linux stack (wpa_supplicant)

2016-12-06 Thread Manolis Surligas
Hi all, we have done it two years ago as part of my master thesis and it works like a charm! The SDR IEEE 802.11 implementation can be configured as AP using hostapd or adhoc via the network manager. We had some problems making it work as a normal client however. Our approach has a kernel