> I had the exactly this problem. To solve it, I download source code from
> git, to apply the path and before this I install from the source code
> (./configure, make, etc.). As the final observation I must run sudo
> ./ldconfig after installation and before to use gnuradio,
>
> Edmar
>
>
Thanks E
I think that many RF and wireless designers make a lot of assumptions as
well and never admit to the horror of the mobile channel. LTE is not
really realizing the needed increase in capacity to justify the rollout cost
of all of the needed infrastructure in my opinion but now everyone is "all
in"
I get the following error when attempting to run my own block in GNU Radio:
"thread[thread-per-block[1]: ]: Invalid input"
..and any ideas how to resolve it?
___
Discuss-gnuradio mailing list
Discuss-gnuradio@g
Thank you very much for your reply! I'll write a GNURadio module for our
DB-SDR-Hardware to use it together with the UCLA ZigBee implementation.
As a reference system and maybe for future work we want to buy an
USRP/USRP2. Which version do you propose? The ZigBee code seems to
have been written
Am 10.08.2011 um 16:12 schrieb Martin Flasskamp:
> Thank you very much for your reply! I'll write a GNURadio module for our
> DB-SDR-Hardware to use it together with the UCLA ZigBee implementation.
>
> As a reference system and maybe for future work we want to buy an
> USRP/USRP2. Which version
Hello list,
I just burned the latest UHD firmware onto the SD card I am using with my
USRP2, and when I use the "uhd_find_devices" command I am told that no
devices are found. Previously I had been using the stock firmware and I
could find the USRP2 by using the 'find_usrps' command. When I use th
For anyone else suffering with this, I fixed this:
Needed to use -R flags as well as -L..
Everything builds now, but the block doesn't seem to do anything. The problem
is that I don't even get an error message. So I have no idea where to start
debugging..
From: ogl...@hotmail.com
To: discuss-
On 08/10/2011 09:13 AM, Brenden Smith wrote:
> Hello list,
>
> I just burned the latest UHD firmware onto the SD card I am using with my
> USRP2, and when I use the "uhd_find_devices" command I am told that no
> devices are found. Previously I had been using the stock firmware and I
> could find
Am 10.08.2011 um 18:13 schrieb Brenden Smith:
> Hello list,
>
> I just burned the latest UHD firmware onto the SD card I am using with my
> USRP2, and when I use the "uhd_find_devices" command I am told that no
> devices are found. Previously I had been using the stock firmware and I could
> f
Hello,
I'm trying to configure the slave device so I can use a MIMO cable with 2 of
my USRP N210's. I see the application notes for the N210 where it says you
need to configure the slave with:
uhd::clock_config_t clock_config;
clock_config.ref_source = uhd::clock_config_t::REF_MIMO;
clock_config.
Thank you two for the prompt reply. I had forgotten to set the static IP
address and once I did the problem resolved. Thank you again
Brenden
On Wed, Aug 10, 2011 at 11:54 AM, Matthias Wilhelm <
wilh...@informatik.uni-kl.de> wrote:
> Am 10.08.2011 um 18:13 schrieb Brenden Smith:
>
> > Hello list,
On 08/10/2011 09:57 AM, Wes Rumble wrote:
> Hello,
> I'm trying to configure the slave device so I can use a MIMO cable with 2 of
> my USRP N210's. I see the application notes for the N210 where it says you
> need to configure the slave with:
>
> uhd::clock_config_t clock_config;
> clock_config
I'm sorry I wasn't clear. I thought before I could do anything MIMO in the
GRC I had to change some configuration files because of that block I quoted
from the N210 Application notes on the Ettus site. Are you saying I don't
need to change anything, I can just set the reference to MIMO and move
I'm working on a continuum interferometer project (actually resurrecting
one that has been dormant for several years). I'm currently
playing with approaches for spectral estimating with a two-antenna
interferometer system. I think, ideally, since you have two antennae,
you'd like to take ad
14 matches
Mail list logo
