[Discuss-gnuradio] spectrum record

2014-07-27 Thread gsmandvoip
Hi list, I want to record a 5MHz wide bandwidth with usrp1 (equipped with dbsrx1 and modified clock @ 52MHz), can anyone guide me how to do this, I am using usrp_rx_cfile (using gnuradio-3.4.2 for special purpose) with gain =52 decimation= 26 Please do let me know if I need to make any changes in

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Marcus Müller
Having your complete general_work function wouldn't have hurt my understanding much... I really can't make out what you're trying to do without doubt. Anyway, from the code below I think in *must at least* have the same number of entries that your for loop has iterations; did you just try using

Re: [Discuss-gnuradio] spectrum record

2014-07-27 Thread Marcus Müller
Hi gsmandvoip, Your decimation seems about right (oh, I don't miss libusrp). I don't think you need to change the example, but please be aware that libusrp has become so obsolete that I don't even have the source code around anymore. I'm not totally sure you need to use libusrp to have openBTS

[Discuss-gnuradio] Persistence Checkbox of WX GUI Scope Plot

2014-07-27 Thread Activecat
Dear Sir, It is found that in newer version of gnuradio, the WX GUI Scope Sink doesn't have a Persistence checkbox. In this case how to get back the feature ..? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org

Re: [Discuss-gnuradio] New WX GUI Scope Sink

2014-07-27 Thread Tom Rondeau
On Sun, Jul 27, 2014 at 10:36 AM, Activecat active...@gmail.com wrote: Dear Sir, The new WX GUI Scope Sink behaves slightly differently from the previous one. How come it only plots the center part (as circled), how to make it plot the full graph without changing the time/div of x-axis?

Re: [Discuss-gnuradio] Narrowband Tunnel.py Error

2014-07-27 Thread Tom Rondeau
On Fri, Jul 25, 2014 at 4:28 PM, Jonathan Fox 31...@cardinalmail.cua.edu wrote: On Fri, Jul 25, 2014 at 1:13 PM, Tom Rondeau t...@trondeau.com wrote: On Thu, Jul 24, 2014 at 7:42 PM, Jonathan Fox 31...@cardinalmail.cua.edu wrote: Thanks for the response. A colleague of mine recommended

Re: [Discuss-gnuradio] AttributeError: 'module' object has no attribute

2014-07-27 Thread Mike
I followed the tutorial to generate a module and all was well. My square module worked. I then created a new module invert_bb. This also worked. So far so good. Now a few days later on I get AttributeError: 'module' object has no attribute 'invert_bb' and I have no clue as to why. The previous

Re: [Discuss-gnuradio] AttributeError: 'module' object has no attribute

2014-07-27 Thread Marcus Müller
Hi Mike, my first guess if making from scratch didn't help: maybe your module's name is conflicting with an existing module, or there are remnants of a former installation lying around for some reasons. You could try uninstalling your module via make uninstall, and then running a python trying to

Re: [Discuss-gnuradio] [USRP-users] USRP-users Digest, Vol 47, Issue 27

2014-07-27 Thread Marcus Müller
Hi Mike, is it possible that you are responding to my response on gnuradio by replying to the usrp-users digest? I'm a little confused... The stopped working might be explained by the fact that as soon as you update a library (ie. as soon as you update GNU Radio), you need to rebuild all software

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Mostafa Alizadeh
Thank you for your notes Marcus, As you said this is unnecessary process to point to the input_items in a for loop!! However, this is not the problem because I checked that I have the same number of iteration in the for loop as the number of input ports. The problem is somewhere else. *Again I

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Marcus Müller
As I said, you should use the gdb debugging approach to find the mistake. gr_complex **in = (gr_complex) input_items; shouldn't compile, because the types are incompatible. I can't help you any further with the information you're offering. Please share at least your complete general_work method,

Re: [Discuss-gnuradio] gr-fec LDPC comments / questions.

2014-07-27 Thread Perez, Tracie R
Hi Sylvain, Thanks for looking at this code. I really appreciate the feedback. Comments/questions inline below. ~ tracie perez On Jul 25, 2014, at 1:25 PM, Sylvain Munaut wrote: Hi, I've been looking at the LDPC code and I have a few comments / questions : 1) Memory management seems

Re: [Discuss-gnuradio] gr-fec LDPC comments / questions.

2014-07-27 Thread Sylvain Munaut
Hi, For the encoder/decoder, you're totally right. I didn't free any of the temporary matrices. I just updated those classes with gsl_matrix_free calls. Ok good. Whenever we move to a more efficient implementation that doesn't use GSL for GF2 operation, it would probably make sense to have

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Mostafa Alizadeh
Yes you're right about casting between in and input_items, however, I think this problem is somehow related to the large number input ports! I don't why! Here is the whole block: #ifdef HAVE_CONFIG_H #include config.h #endif #include gnuradio/io_signature.h #include phich_grouping_impl.h int

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Mostafa Alizadeh
I forgot to say, I'm using Qtcreator to debug my GNURadio codes I do not need any others! The prgram is terminated at line in which I read from the input for the first time i.e. : y_p[i][k] = 0; for (int j=0; jN_FS_phich(d_normal_cp); j++) {

[Discuss-gnuradio] spectrum record

2014-07-27 Thread gsmandvoip
Hi Marcus, list, Thanks for swift response. You are right about openBTS, but at the same time I am using really old system (12.04) havent formatted for years due to its required installation, which can turn into real time consuming tasks thats why dragging it as long as I can avoid above

Re: [Discuss-gnuradio] Problem with large number of inputs.

2014-07-27 Thread Activecat
Mostafa, I do not think you have truly run the complete codes using Qtcreator, because that doesn't have a gnuradio runtime (the scheduler). At the other hand, your problem sounds more like a c++ coding error rather than gnuradio-specific. The helpful approach is 1). Put up the OOT into github.