[Discuss-gnuradio] Project Status: GSoC 2013

2013-07-15 Thread Shashank Gaur
Hello All, I already sent this email twice over weekend, I am not sure if its getting delivered. Apologies if I spam the list/your inbox. I am Shashank, one of the GSoC students this year. My project proposal was to work on IEEE 802.11 receiver developed by Bastian Bloessl at University of

Re: [Discuss-gnuradio] calibrating USRP

2013-07-15 Thread Nemanja Savic
I think this should be the last question in this thread. Which input signal levels should I stick? OIP3 at the first LNA MGA-62563 is 23 dBm. Since the gain is arround 22 dB, is it ok to stay below -20dBm? Best, Nemanja On Wed, Jul 10, 2013 at 2:33 PM, Marcus D. Leech mle...@ripnet.com wrote:

Re: [Discuss-gnuradio] calibrating USRP

2013-07-15 Thread Marcus D. Leech
On 07/15/2013 08:55 AM, Nemanja Savic wrote: I think this should be the last question in this thread. Which input signal levels should I stick? OIP3 at the first LNA MGA-62563 is 23 dBm. Since the gain is arround 22 dB, is it ok to stay below -20dBm? Best, Nemanja Yes, signals below -20dBm

Re: [Discuss-gnuradio] AttributeError: 'function' object has no attribute 'to_basic_block' ? (GR 3.7.0)

2013-07-15 Thread Monahan-Mitchell, Tim
One of my OOT blocks is a function that takes in shorts and outputs shorts (a 1-to-2 interpolator). I have a simple flowgraph created in GRC: File Source - My block - File sync . GRC is happy until I run the flowgraph, and I get this: Executing: /top_block.py Traceback (most

[Discuss-gnuradio] Scheduler Issues with Branch Prediction

2013-07-15 Thread Ron Sadlier
Hello everyone, I've been having the same issue with the scheduler for the past 2 months or so and I'm starting to unravel what I believe is occurring. Let me describe my flowgraph first, then describe what's happening when I run the flow graph, and then describe some REALLY interesting things

[Discuss-gnuradio] decode problem in benchmark

2013-07-15 Thread yeran
Hi everyone, I have a question about benchmark decoding. I'm using bpsk mod and demod. In order to understand what's happening in the demodulation process, I added a file sink after time_recov block and after unpack block respectively. According to my understanding, the receiver block does the

Re: [Discuss-gnuradio] AttributeError: 'function' object has no attribute 'to_basic_block' ? (GR 3.7.0)

2013-07-15 Thread Monahan-Mitchell, Tim
One of my OOT blocks is a function that takes in shorts and outputs shorts (a 1-to-2 interpolator). I have a simple flowgraph created in GRC: File Source - My block - File sync . GRC is happy until I run the flowgraph, and I get this: Executing: /top_block.py Traceback (most

Re: [Discuss-gnuradio] Does GRAS support setting max noutput_items?

2013-07-15 Thread devin . butterfield
Hi Josh, Thanks for the quick work on this. Setting max noutputitems from grc works fine now. -- Regards, Devin - Reply message - From: Josh Blum j...@joshknows.com To: discuss-gnuradio@gnu.org Cc: devin.butterfi...@gmail.com Subject: [Discuss-gnuradio] Does GRAS support setting max

[Discuss-gnuradio] GRAS flow control from work function

2013-07-15 Thread devin . butterfield
Hi, I'm using gras for my application and my custom block needs to be able to do a blocking read to get data from an external source. With the standard scheduler I used a non blocking read in a polling loop with an interruptable sleep and this worked Ok. Do I need to do it this way with gras

Re: [Discuss-gnuradio] GRAS flow control from work function

2013-07-15 Thread Josh Blum
On 07/15/2013 05:43 PM, devin.butterfi...@gmail.com wrote: Hi, I'm using gras for my application and my custom block needs to be able to do a blocking read to get data from an external source. With the standard scheduler I used a non blocking read in a polling loop with an interruptable

Re: [Discuss-gnuradio] problem with clock_recovery_mm on low data rates

2013-07-15 Thread Nemanja Savic
I would be also happy if somebody would answer you, but from my past experience, nobody talks much about clock recovery MM, and I am quite sure that setting up values are not well explained. Nemanja On Mon, Jul 15, 2013 at 10:56 AM, Niaz Ahmed niaz.ah...@nu.edu.pk wrote: Hi all, I am

Re: [Discuss-gnuradio] Mistake in fmdet_cf_impl.cc:109?

2013-07-15 Thread Johnathan Corgan
On Thu, Jul 11, 2013 at 3:37 AM, Perper per...@o2.pl wrote: I was reading the c++ code of FM demodulators in gnuradio and I encountered this in fmdet_cf_impl.cc:109: - Sdot = d_scl * (-S0+d_8*S1-d_8*S1+S4); -

Re: [Discuss-gnuradio] ATSC fixups

2013-07-15 Thread Johnathan Corgan
On Sun, Jul 14, 2013 at 12:03 PM, Andrew Davis glneolistm...@gmail.comwrote: I have been working on getting gr-atsc running again, I have found a few speedups and some bugs that prevented ATSC decoding from working with new versions of GNURadio. I have put these fixes into a branch that can

Re: [Discuss-gnuradio] ATSC fixups

2013-07-15 Thread Andrew Davis
Sure: - first the description is correct and not just copied from interp_short.py - removed the writing to 'atsc_complex.data' as this uses a lot of space and seems to have no meaning outside of debugging - I use interleave_short_to_complex instead of s2s - s2f - f2c chain - lp_coeffs and

Re: [Discuss-gnuradio] ATSC fixups

2013-07-15 Thread Johnathan Corgan
On 07/15/2013 07:01 PM, Andrew Davis wrote: After this stuff and the reorganization a simple diff would not have saved much, also i'm working on 'atsc_tx.py',so 'all_atsc.py' would be confusing, hence the name change. First, let me say that I'm very happy this code is getting some attention.