[Discuss-gnuradio] hier_blocks2 error

2015-08-12 Thread bob wole
I am using gnruadio 3.7.8. I have a module (python) which is working well for version 3.6.3. In made necessary changes so that it can work with gnuradio 3.7.8. However I am getting following error File "/usr/local/lib/python2.7/dist-packages/gnuradio/gr/hier_block2.py", line 92, in __getattr__

Re: [Discuss-gnuradio] FFT Scaling

2015-08-12 Thread West, Nathan
On Wed, Aug 12, 2015 at 12:31 PM, West, Nathan wrote: > On Wed, Aug 12, 2015 at 10:51 AM, Gerome Jan L > wrote: > >> There is an internal scaling effect of fftlen (the length of your FFT) >> in the FFT block. How do I unscale or remove the scaling factor in the >> python generated by thr GRC? I

Re: [Discuss-gnuradio] error with running wifi_loopback.grc from gr-ieee802-11

2015-08-12 Thread Paul Garver
Tian, Disable logging and debug in the GRC flowgraph. See if this solves the problem. For reference, see [1]. [1] https://lists.gnu.org/archive/html/discuss-gnuradio/2015-07/msg00289.html On 08/12/2015 01:23 PM, discuss-gnuradio-requ...@gnu.org wrote: Send Discuss-gnuradio mailing list s

Re: [Discuss-gnuradio] FFT Scaling

2015-08-12 Thread West, Nathan
On Wed, Aug 12, 2015 at 10:51 AM, Gerome Jan L wrote: > There is an internal scaling effect of fftlen (the length of your FFT) in > the FFT block. How do I unscale or remove the scaling factor in the python > generated by thr GRC? I tried the one suggested in the faq, > > ... forward FFT --> mult

Re: [Discuss-gnuradio] mirrored spectrum around tuning freq

2015-08-12 Thread Luca Pascale
Hi Marcus, in the picture you see the power output of the signal generator is -30 dBm. Changing it to -90 dBm does not produce any change in the received signal except a (obvious) lower level. There is not other amplifier between signal generator output and N200 input. Luca -- Ing. Luca Pascal

Re: [Discuss-gnuradio] No revision detected MB EEPROM must be reprogrammed!

2015-08-12 Thread Julian Arnold
Hi Matija, thank you for your information. Just to get it right, did you run the command usrp_burn_mb_eeprom --values="revision=6" with your corrupted USRP and after that the error still persists? Cheers, Julian On Tue, Aug 11, 2015 at 5:20 PM, Matija Ciganovic wrote: > However note: it doe