Re: [Discuss-gnuradio] usrp_n200_r3_fpga.bin build error

2013-05-01 Thread Rahman, Muhammad Mahboob Ur
Hi Ian, USRP specific questions (especially FPGA/Hardware) are best directed at the USRP mailing list, rather than the GNURadio one. You are right in your suggestion :) It's hard to say exactly what has caused this error, but basically it;s failing to identify the module name that is the

Re: [Discuss-gnuradio] usrp_n200_r3_fpga.bin build error

2013-05-01 Thread Rahman, Muhammad Mahboob Ur
usrp_n200_fpga_r3.bin file. Right? Thanks, Mahboob From: Ian Buckley [i...@ionconcepts.com] Sent: 01 May 2013 11:01 To: Rahman, Muhammad Mahboob Ur Cc: Ian Buckley; usrp-us...@lists.ettus.com forum; discuss-gnuradio@gnu.org list Subject: Re: [Discuss-gnuradio

[Discuss-gnuradio] usrp_n200_r3_fpga.bin build error

2013-04-30 Thread Rahman, Muhammad Mahboob Ur
All, I am trying to modify the USRP N200 FPGA so as to mute the ADC when TX section is enabled inside my flow graph. However, when I try to build the usrp_n200_r3_fpga.bin file, I get below error message which I don't understand: l-ece109:N2x0$ make -f Makefile.N200R3 bin python

Re: [Discuss-gnuradio] transmitter receiving its own packet

2013-04-09 Thread Rahman, Muhammad Mahboob Ur
Hi Josh, So it would be possible to mute the ADC samples when the device is transmitting. However, that might only be desirable in a couple of use cases, and there are probably a dozen ways to solve this from all the way down at the physical layer up the the MAC layer: * mute the RX ADC when

Re: [Discuss-gnuradio] USRP N200 not being identified by the host running Suse

2013-02-04 Thread Rahman, Muhammad Mahboob Ur
Hi Marcus, I assume you are talking about the green LED on the top left of Ethernet port on USRP N200. If so, then it remains On. However, I don't see any yellow activity light at all. Furthermore, only LED D and F are On. Thanks, Mahboob From:

Re: [Discuss-gnuradio] USRP N200 not being identified by the host running Suse

2013-02-04 Thread Rahman, Muhammad Mahboob Ur
February 2013 10:43 To: Rahman, Muhammad Mahboob Ur Subject: RE: [Discuss-gnuradio] USRP N200 not being identified by the host running Suse You might want to try using usrp2_recovery.py you'll have to run it as root, and it will attempt to restore to the default address. I suspect that your device

[Discuss-gnuradio] USRP N200 not being identified by the host running Suse

2013-02-01 Thread Rahman, Muhammad Mahboob Ur
All, When I connect my USRP N200 to a PC running Suse, run ifconfig eth0 192.168.10.1 command, and then run command uhd_usrp_probe --args=addr=192.168.10.2, I see the famous error message: LookupError: KeyError: No devices found for - Empty Device Address The weird fact is that I have 9

Re: [Discuss-gnuradio] using general_work when output rate is not fixed

2012-09-25 Thread Rahman, Muhammad Mahboob Ur
Hi Tom All, I am now doing consume_each(noutput_items) but my problem is not solved yet. I have also made sure that my code effectively sends one sob tag and one eob tag per burst of samples. Questions about new experiment: Now, I have created yet another simple experiment whose flow-graph is

[Discuss-gnuradio] using general_work when output rate is not fixed

2012-09-09 Thread Rahman, Muhammad Mahboob Ur
All, I have made a simple custom block (derived from gr_block class) whose general_work() function is given below: int howto_my_custom_blk::general_work (int noutput_items, gr_vector_int ninput_items, gr_vector_const_void_star input_items, gr_vector_void_star output_items){ const gr_complex

[Discuss-gnuradio] import error:undefined symbol

2010-08-14 Thread Rahman, Muhammad Mahboob Ur
Hi all, I want to make a simple hard limiter block (hlimit_ff()) which works as follows: if input0 output=-1 else if input0 output=1 else output=0 So, in essence, I have downloaded the tar ball gr-how-to-write-a-block-3.2.tar.gz and replaced 'square' with 'hlimit' in the howto_square_ff.h,

[Discuss-gnuradio] RE: $ make gives error

2010-08-04 Thread Rahman, Muhammad Mahboob Ur
line 990: g++: command not found make[4]: *** [_howto_la-howto.lo] Error 1 make[4]: Leaving directory `/home/mahboob/Desktop/myblocks/src/lib' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/mahboob/Desktop/myblocks/src/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving

[Discuss-gnuradio] $ make gives error

2010-08-03 Thread Rahman, Muhammad Mahboob Ur
Hi all, I am trying to run the examples given in tutorial, how-to-write-a-signal-processing-block. The $ ./configure is fine but $ make yields the error below. mahb...@ubuntu:~/Desktop/myblocks$ make make all-recursive make[1]: Entering directory `/home/mahboob/Desktop/myblocks' Making all

RE: [Discuss-gnuradio] PLL and VCO questions

2010-08-02 Thread Rahman, Muhammad Mahboob Ur
Wilson [johnmwilso...@gmail.com] Sent: 02 August 2010 02:33 To: Rahman, Muhammad Mahboob Ur Cc: discuss-gnuradio Subject: Re: [Discuss-gnuradio] PLL and VCO questions Hey, You can't make a feedback system in the Python flowgraph. You can, however use feedback in an individual signal processing block

[Discuss-gnuradio] transceiving a sinusoid using usrp's

2010-07-12 Thread Rahman, Muhammad Mahboob Ur
Hi, I am trying to send, then receive and finally display a sinusoid of arbitrary frequency say 128KHz using two usrp's and two computers. I have used grc on both computers to do so. On tx computer, the flow graph of grc is: signal source -- usrp sink In signal source, I set the frequency of

RE: [Discuss-gnuradio] transceiving a sinusoid using usrp's

2010-07-12 Thread Rahman, Muhammad Mahboob Ur
. From: Alexandru Csete [oz9...@googlemail.com] Sent: 12 July 2010 11:13 To: Rahman, Muhammad Mahboob Ur Cc: discuss-gnuradio Subject: Re: [Discuss-gnuradio] transceiving a sinusoid using usrp's On 12 July 2010 15:52, Rahman, Muhammad Mahboob Ur mahboob-rah