[Discuss-gnuradio] Approaches for cross-spectra

[Marcus D. Leech]

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 advantage of that for producing spectral estimates 
that have channel-electronics-induced-spurs reduced in magnitude,
  and the spectral components that are common to the two antennas 
enhanced.  I've tried various approaches:


o Add the magnitudes of the FFTs for two antennae, low pass filter that

  This produces a *composite* spectral estimate, including the 
components due to independent spurs on the two channels.


o Complex multiply the two FFT outputs, then compute the magnitude, 
low-pass filter that


   This seems to produce some suppression of distinct components 
that aren't common to the two sides
   The absolute magnitudes of non-suppressed components are 
obviously larger, due to the multiply.


The second approach seems very similar to what ALMA is doing for their 
FX correlators.


Any words of wisdom/advice?

--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Configuring the slave for MIMO cable

[wes.rumble]

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 on? 
Thanks,
Wes

Josh Blum-3 wrote:
> 
> 
> 
> I'm not sure what you are asking. If you make a quick flow graph in grc
> and set the reference source to "mimo cable", generate the code, you can
> inspect the code for how to do it in python.
> 
> -josh
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Configuring-the-slave-for-MIMO-cable-tp32235863p32236023.html
Sent from the GnuRadio mailing list archive at Nabble.com.


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Configuring the slave for MIMO cable

[Josh Blum]

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.ref_source = uhd::clock_config_t::REF_MIMO;
> clock_config.pps_source = uhd::clock_config_t::PPS_MIMO;
> usrp->set_clock_config(clock_config, slave_index);
> 
> My question is, where do I make these changes exactly?  I found a clock
> config file that has syntax similar to this but nothing that matches it and
> I don't want to mess anything up.  Any help is greatly appreciated, thanks!

I'm not sure what you are asking. If you make a quick flow graph in grc
and set the reference source to "mimo cable", generate the code, you can
inspect the code for how to do it in python.

-josh

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] USRP2 and UHD

[Brenden Smith]

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,
> >
> > 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 the
> 'uhd_find_devices' command the orange light on the Ethernet port (on the
> USRP2) lights up briefly and then nothing happens. When I boot up the device
> I get a sequence of three LEDs lighting up then a flash and the right bottom
> two light remain lit. Any help with this matter would be appreciated.
> >
> > Thank you,
> > Brenden
>
> Your SD card seems to boot ok. The problem may be the network settings at
> the host.
> The old version used raw ethernet frames, so only the correct network
> device ethX was required. However, the new version uses standard IP, so you
> have to set the network parameters correctly, as described in
> http://www.ettus.com/uhd_docs/manual/html/usrp2.html#setup-networking
> You need to be in the right network (192.168.10.0/24) to find the USRP2.
>
> Regards,
> Matthias
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Configuring the slave for MIMO cable

[Wes Rumble]

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.pps_source = uhd::clock_config_t::PPS_MIMO;
usrp->set_clock_config(clock_config, slave_index);

My question is, where do I make these changes exactly?  I found a clock
config file that has syntax similar to this but nothing that matches it and
I don't want to mess anything up.  Any help is greatly appreciated, thanks!
Wes


-- 
Wes Rumble
Graduate Research Assistant
219 Engineering Research BuildingWVU CSEE

wes.rum...@gmail.com
wrum...@mix.wvu.edu
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] USRP2 and UHD

[Matthias Wilhelm]

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 
> find the USRP2 by using the 'find_usrps' command. When I use the 
> 'uhd_find_devices' command the orange light on the Ethernet port (on the 
> USRP2) lights up briefly and then nothing happens. When I boot up the device 
> I get a sequence of three LEDs lighting up then a flash and the right bottom 
> two light remain lit. Any help with this matter would be appreciated.
> 
> Thank you,
> Brenden

Your SD card seems to boot ok. The problem may be the network settings at the 
host. 
The old version used raw ethernet frames, so only the correct network device 
ethX was required. However, the new version uses standard IP, so you have to 
set the network parameters correctly, as described in 
http://www.ettus.com/uhd_docs/manual/html/usrp2.html#setup-networking
You need to be in the right network (192.168.10.0/24) to find the USRP2. 

Regards,
Matthias


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] USRP2 and UHD

[Josh Blum]

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 the USRP2 by using the 'find_usrps' command. When I use the
> 'uhd_find_devices' command the orange light on the Ethernet port (on the
> USRP2) lights up briefly and then nothing happens. When I boot up the device
> I get a sequence of three LEDs lighting up then a flash and the right bottom
> two light remain lit. Any help with this matter would be appreciated.
> 

http://www.ettus.com/uhd_docs/manual/html/usrp2.html#setup-networking

http://www.ettus.com/uhd_docs/manual/html/usrp2.html#communication-problems

http://www.youtube.com/watch?v=REDK7M-83WQ

-josh

> Thank you,
> Brenden
> 
> 
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Creating a new GNU Block

[OG LESS]

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-gnuradio@gnu.org
Subject: Creating a new GNU Block
Date: Mon, 8 Aug 2011 21:01:13 +0100








Hello All,

I am trying to make a new block for GNU Radio, which uses MATLAB (MCR).

When I get to the 'sudo make check' stage, it gives me the following error:

"/usr/bin/isn/lib/.libs/lt-test_all: error while loading shared libraries: 
libmwmclmcr.so: cannot open shared object file: No such file or directory"

"libmwmclmcr.so" is located in "/usr/local/matlab/r2010b/bin/glnxa64", and I 
_have_ included this in the Makefile.am as follows:

MATLAB_ROOT = /usr/local/matlab/r2010b

MY_LIB_ROOT=$(HOME)/homedir/gnuradio/Blocks/MI

LD_LIBRARY_PATH=$(MATLAB_ROOT)/bin/glnxa64:/usr/lib64:$(MATLAB_ROOT)/runtime/glnxa64:$(MATLAB_ROOT)/bin/glnxa64:$(MATLAB_ROOT)/sys/os/glnxa64:$(MATLAB_ROOT)/sys/java/jre/glnxa64/jre/libamd64/native_threads:$(MATLAB_ROOT)/sys/java/jre/glnxa64/jre/lib/amd64/server:$(MATLAB_ROOT)/sys/java/jre/glnxa64/jre/lib/amd64:$(MY_LIB_ROOT)

It is also in my ~/.bashrc file.

I can get past this error by copying the libmwmclmcr.so to the folder 
/usr/lib64/, and then I can get through the entire 
'boostrap/configure/make/install' procedure successfully without any errors, 
but then the actual block does nothing!

Could anyone help me out with this please? I have tried everything I could 
possibly think of..

Thanks,
OGLES

  ___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] USRP2 and UHD

[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 find the USRP2 by using the 'find_usrps' command. When I use the
'uhd_find_devices' command the orange light on the Ethernet port (on the
USRP2) lights up briefly and then nothing happens. When I boot up the device
I get a sequence of three LEDs lighting up then a flash and the right bottom
two light remain lit. Any help with this matter would be appreciated.

Thank you,
Brenden
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] GNURadio on custom SDR platform / UCLA Zigbee PHY

[Matthias Wilhelm]

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 do you propose?  The ZigBee code seems to
> have been written for the USRP, but how difficult is it porting it to USRP2?
> 
> The Zigbee poject page ( https://www.cgran.org/wiki/UCLAZigBee ) says
> the code needs GNURadio v3.2. Is it better to use that old version or to
> port it to the current GNUradio v3.3.0? Or does anybody still working on
> it and maybe sharing the code somewhere else besides CGRAN?
> 
> Regards,
> Martin

We used the UCLA code together with the USRP2, it is easy to port. The C++ 
blocks and packet handling in python can be reused completely, changes are 
necessary in the src/example scripts that set up the flow graphs. Basically, 
you have to exchange the source/sink blocks with a USRP2/UHD version, correct 
the sampling rate, and remove/adapt some USRP1 specialties such as choosing a 
subdev (there is only one on the USRP2) or setting the PGA (the functions are 
renamed a bit, e.g., its now called u.set_gain(gain) in UHD). In the same way 
you can integrate the code with your hardware later.

We have only USRP2s, the only reason to go for the USRP1 I can think of is that 
you need two boards simultaneously, e.g., when you want to send and receive at 
the same time and still hope to receive something. I think the RFID code on 
CGRAN still needs the USRP1.  This was also the case with the OpenBTS project 
that implements the GSM air interface, but it seems that it works now for both 
platforms. 

Regarding the GNU Radio version, I just tried to compile the UCLA code and it 
completes with the latest git head, I don't think they the code is depending on 
features of a specific version, it seems more like a "guaranteed to work with 
v3.2" statement. I think we used it with a different version than specified 
some time ago, and it successfully  sent and received 15.4 packets. In any 
case, the effort of porting is to tweak the Makefiles rather than change large 
parts of the code. 

Regards,
Matthias
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] GNURadio on custom SDR platform / UCLA Zigbee PHY

[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 do you propose?  The ZigBee code seems to
have been written for the USRP, but how difficult is it porting it to USRP2?

The Zigbee poject page ( https://www.cgran.org/wiki/UCLAZigBee ) says
the code needs GNURadio v3.2. Is it better to use that old version or to
port it to the current GNUradio v3.3.0? Or does anybody still working on
it and maybe sharing the code somewhere else besides CGRAN?

Regards,
Martin


Am 05.08.2011 12:39, schrieb Matthias Wilhelm:
> Hi, 
>
> this sounds like you want to implement the sender/receiver functionality on 
> the host, so why not write a GNU Radio integration module and use existing 
> RX/TX code?
>
> There are already physical layer implementations for ZigBee, 802.11, 
> Bluetooth, Gen2, etc. available (e.g., at 
> https://www.cgran.org/wiki/Projects).
> So you should aim to provide complex samples to GNU Radio as a source/sink 
> block and reuse the existing stuff.
>
> Anyway, for the demonstrator I would choose ZigBee, the physical layer is 
> simple and robust, and the UCLA code works pretty well. 
> It is also likely to work with existing hardware that uses 802.15.4, so you 
> can also send SDR->off-the-shelf hardware (such as sensor motes) without 
> worries.
>
> Regards,
> Matthias
>
> Am 05.08.2011 um 12:03 schrieb Martin Flasskamp:
>
>> Hello all,
>>
>> My name is Martin Flasskamp and I'm currently starting my diploma thesis
>> at Bielefeld University in Germany.
>>
>> My task is to create a wireless demonstration system which enables two
>> nodes to communicate wirelessly using software-defined radio.
>> The platform I'll use is our own modular FPGA-based rapid prototyping
>> system called RAPTOR ( http://www.raptor2000.de/en/home/ ). One of the
>> available daughter boards (called DB-SDR) is compatible to an USRP2 and
>> has a standard XCVR2450 board on top.
>>
>> By integrating our SDR-platform into GNURadio I want to be comparable to
>> USRP and maybe benefit from other GNURadio projects in the future.
>>
>> Now my question:
>> Which wireless standard is the best one to start with as a reference
>> implementation? WiFi/Bluetooth/ZigBee/other?
>>
>> The aim is to have a sender as well as a receiver. Standard conformity
>> would be nice but is not necessarily required.
>>
>> Best regards,
>>
>> Martin



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] What does this error mean?

[OG LESS]

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@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Introducing noise/ considerable BER

[Robert McGwier]

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 am sure Sprint and others are happy LTE and WiMax are both having
lots of problems.

It is truly exceedingly difficult to enable MIMO big gains when lots of
mobile channels, each a horror, need to be managed to achieve any real
advantages.  Welcome to reality!  Verizon can't put a cloud computer at
every cell site to enable the rapid channel inverse caclulations and MIMO
solution per user to optimize the system.

;-)

Bob
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] switching between two flow-graphs / controlling two flow-graphs

[niaz ahmed]

> 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 Edmar for helping me out. I did the same as you told and the problem
is solved.



-- 
*Niaz Ahmed*



“We are always more anxious to be distinguished for a talent which we do not
possess, than to be praised for the fifteen which we do possess”*:  Mark
Twain *

* *
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio