Re: [Discuss-gnuradio] GCN Development GNURadio Win64 Binary (v3.7.9.2/v1.1.1) UDP source connection Problem

2016-05-17 Thread Geof Nieboer
That's a new one, I will see what I can do to repro. So the 3.6.4.1 was working on the same OS (2008) that 3.7.9.2 is not? On Tue, May 17, 2016 at 4:24 PM, Abdil Burak BAŞLI wrote: > Hi all, > > > > I successfully installed GCN Development GNURadio Win64 Binary >

[Discuss-gnuradio] Upcoming gcc6 problems

2016-05-17 Thread Stefan Wunsch
Hey all, gcc6 uses std=gnu++14 as default (compared to std=gnu++98 up to gcc5.3) [0]. This causes a lot of warnings during building gnuradio due to the deprecated auto_ptr (unique_ptr is the way to go now) and gr-zeromq fails building completely. Probably the used c++ standard should be set in

Re: [Discuss-gnuradio] run a loop within GR

2016-05-17 Thread madengr
I have a drive test app here which polls the B200 GPS every second while running the GR flow: https://github.com/madengr/drive_test/blob/master/apps/drive.py Lou Jason Matusiak wrote > I have a python script I built up for GR that runs on my E310. As part > of the startup, it checks for a

Re: [Discuss-gnuradio] VOLK division between complexes

2016-05-17 Thread Federico Larroca
Hello again, Thank you Marcus por looking through my code (and the positive comments). I have several things to report: - Pulling from your repo and using volk_32fc_x2_divide_32fc worked perfectly, and gr-isdbt kept operating as usual. - Substituting yours with my AVX proto-kernel (plus the

[Discuss-gnuradio] run a loop within GR

2016-05-17 Thread Jason Matusiak
I have a python script I built up for GR that runs on my E310. As part of the startup, it checks for a GPS fix and waits until it gets one before moving on. My question is how I can have my script running, yet occasionally check for GPS lock so I can do something with knowledge (like output

Re: [Discuss-gnuradio] [PyBOMBS] Need your help!

2016-05-17 Thread Andy Walls
On Tue, 2016-05-17 at 12:44 -0400, discuss-gnuradio-requ...@gnu.org wrote: > Date: Mon, 16 May 2016 22:51:45 +0200 > From: Marcus M?ller > To: discuss-gnuradio@gnu.org > > Hi Martin, > > first of all: thanks for jumping through all these hoops to push > PyBOMBS! > > So, trying to make things

[Discuss-gnuradio] List Maintenance - May 17 at 3pm EDT

2016-05-17 Thread Ben Hilburn
Hi all - Just a heads-up: the FSF is doing some maintenance on the GNU mailing lists, so `discuss-gnuradio` will be down for 1-2 hours this afternoon. You can see the official notice, below. Cheers, Ben -- Forwarded message -- From: Ruben Rodriguez Date: Mon, May

[Discuss-gnuradio] GCN Development GNURadio Win64 Binary (v3.7.9.2/v1.1.1) UDP source connection Problem

2016-05-17 Thread Abdil Burak BAŞLI
Hi all, I successfully installed GCN Development GNURadio Win64 Binary (v3.7.9.2/v1.1.1) on to the windows host machine (Windows Storage Server 2012 R2 standard, as you know It is the server version of Windows 8). However while communicating SDR via GNURadio, UDP source gives an following

Re: [Discuss-gnuradio] grc probe broken after commit c85984f105106ff0a7e3b387d680e0f2f5884d55

2016-05-17 Thread Koslowski, Sebastian (CEL)
Thanks for reporting this. My commit is indeed responsible for this. Fixed one bug, but added a new one... The expression splitting code seems to be very fragile =) Please check out this branch that contains an updated fix https://github.com/skoslowski/gnuradio-wg-grc/tree/callback_fix_doover

Re: [Discuss-gnuradio] Fwd: Questions on rx_ofdm example in GR 3.7.1

2016-05-17 Thread hgajiayou
Hey Marcus: Yes,I mean ofdm_frame_equalizer_vcvc, sorry for this typos. I'm using USRPs(sync through MIMO cable) to build a 2*2 OFDM-MIMO system. Now, my work is focus on estimating CSI. In my system, fft_len=64, occupied_carriers=24{range(-26,-21)+range(-20,-7)+range(-6,0) for

Re: [Discuss-gnuradio] Fwd: Questions on rx_ofdm example in GR 3.7.1

2016-05-17 Thread Marcus Müller
Hi Han, You replied to a thread from September 2013 – which is totally OK, but many of us don't have the original mail in their archives, so here it is: > Hi Tim. > > The solution I found was to set the Fixed Frame Length parameter to 1 > on the OFDM Frame Equalizer block of the "Header Stream".