Zohair,
Glad to hear that things are working! (though not perfectly)
I intend to duplicate a 4X setup to verify what you are seeing. In the
meantime I have a few things you can try:
1)
edit gr-uhd/lib/uhd_mimo_source.h and change the time in the following
line to something larger, say 50 ms:
Hello,
I've got another short question.Up til now, I used the 3.2.2 release of
Gnuradio, but now I've updates it to the latest git version 3.3.1.
I wanted to check if my already written code still works, but I didn't even
recognize my USRP2. So my question is, do I have to update my USRP2 firmwa
On 07/26/2010 06:05 PM, Marc Epard wrote:
> On Jul 26, 2010, at 4:56 PM, Marcus D. Leech wrote:
>
>> Something that would be useful would be a place for people to pick up
>> the necessary burn_dbsrx_eeprom.bin
>> without having to compile the C code. Just sayin'
>
> I found it at
> http://code.et
On Mon, Jul 26, 2010 at 1:39 AM, Craig Tong wrote:
> Hi
>
> bcdDevice is 0.00 for the verbose lsusb output. Also there doesn't seem to a
> be a burn-usrp4-eeprom anymore but there is a burn-db-eeprom, unless I'm
> missing something.
The script you need to run can be found in the built source.
u
The transmission line can act as a phase shifter depending upon how
long it is and how the GPS signal is being split.
~Jeff
On 7/26/2010 5:54 PM, Marcus D. Leech wrote:
On 07/26/2010 04:00 PM, Matt Ettus wrote:
Even if you lock the USRP2 to an external reference, there will still
be drift re
Hi All,
By adding a config.conf and the two lines solved the segfault
(dis)Enable the GL Sinks¶
Rather than modifying existing programs, the GL sinks can be enabled via a
configuration file.
To enable the GL sinks, edit or create ~/.gnuradio/config.conf and add the
following lines:
[wxgui]
s
On 07/26/2010 03:26 PM, senlin peng wrote:
Hi Matt
Even if you lock the USRP2 to an external reference, there will still be
drift relative to other things not connected to the same reference.
Can you give me an example? The PLL on the daughter board is also
connected with the reference cloc
Hi Matt
> Even if you lock the USRP2 to an external reference, there will still be
> drift relative to other things not connected to the same reference.
Can you give me an example? The PLL on the daughter board is also
connected with the reference clock. I hope to know which part is not
connec
On Jul 26, 2010, at 4:56 PM, Marcus D. Leech wrote:
> Something that would be useful would be a place for people to pick up
> the necessary burn_dbsrx_eeprom.bin
> without having to compile the C code. Just sayin'
I found it at
http://code.ettus.com/redmine/ettus/projects/public/wiki/U2binari
On 07/26/2010 03:20 PM, Marc Epard wrote:
> On Jul 26, 2010, at 11:29 AM, Marcus D. Leech wrote:
>> Did you do the conversion steps necessary to get a DBS_RX to work
>> with the USRP2?
>
> On Jul 26, 2010, at 11:24 AM, Josh Blum wrote:
>
>> Did you do the hardware mod where you move the resistor?
>
On 07/26/2010 04:00 PM, Matt Ettus wrote:
>
> Even if you lock the USRP2 to an external reference, there will still
> be drift relative to other things not connected to the same
> reference. The function generator has its own clock, as does GPS.
>
> Matt
>
>
Somewhat disturbingly, I've also observ
On 07/26/2010 11:22 AM, senlin peng wrote:
I still get phase drift even with atomic external clock connected and
configured in software with config_mimo(MC_WE_LOCK_TO_SMA).
I tried with GPS signals and a sinusoid from the function generator as
the inputs. There is phase drift in both cases. The
On Jul 26, 2010, at 11:29 AM, Marcus D. Leech wrote:
> Did you do the conversion steps necessary to get a DBS_RX to work with the
> USRP2?
On Jul 26, 2010, at 11:24 AM, Josh Blum wrote:
> Did you do the hardware mod where you move the resistor?
>
> http://gnuradio.org/redmine/wiki/gnuradio/USRP
I still get phase drift even with atomic external clock connected and
configured in software with config_mimo(MC_WE_LOCK_TO_SMA).
I tried with GPS signals and a sinusoid from the function generator as
the inputs. There is phase drift in both cases. The attachment shows a
picture of the phase error
On Fri, Jul 23, 2010 at 6:52 PM, rui qian wrote:
> Hi all,
> I want to use tunnel.py with usrp1+xcvr2450 to create a network
> interface, and I set the frequent to 5.0G.
> The tx is ok, but it can't receive anything.
> I google the reason about it, someone say that the gnuradio_r10853
> can fix th
On 07/18/2010 12:55 PM, Matthias Schäfer wrote:
Hi list,
I want to send data direct from the firmware without host. I looked at
the tx_standalone.c and there came up some questions:
If you are going to do something completely standalone, there is no need
to use ethernet. Just send packets to
An extra peice of information is that the block is instable even with 2 and
three USRP2. This means sometimes it works and sometimes it producs no
output.
Zohair wrote:
>
> Dear Josh,
>
> I have sorted out the PPS signal problem. It was the splitter that has the
> problem and now I am able to
> You should treat each block as a black box, unrelated to the blocks
> upstream or downstream from it. If you're thinking that they are
> related, or are trying to second guess the scheduler wrt noutput_items
> or the amount of input available when your general_work function is
> called, you're h
On 07/23/2010 09:38 AM, George Nychis wrote:
One last question still, do you know where I am missing a factor of two
here:
1) My calculation of the bandwidth of the 100 active bins, and the
actual bandwidth, is off by a factor of two:
(((100 MHz) / 32) / 1024) * 100 = 305.175781 kilohertz, wher
On 07/26/2010 11:58 AM, Marc Epard wrote:
> We're new to gnuradio and have a shiny USRP2 with a DBSRX
> daughterboard. More details are below.
>
> The system is kind of working, but usrp2_fft.py reports Failed (or
> Invalid if there's a typo) for every frequency we enter regardless of
> whether it'
We're new to gnuradio and have a shiny USRP2 with a DBSRX daughterboard. More
details are below.
The system is kind of working, but usrp2_fft.py reports Failed (or Invalid if
there's a typo) for every frequency we enter regardless of whether it's in the
supported range or not. Oddly, the entere
Hello,
I've got another short question.Up til now, I used the 3.2.2 release of
Gnuradio, but now I've updates it to the latest git version 3.3.1.
I wanted to check if my already written code still works, but I didn't even
recognize my USRP2. So my question is, do I have to update my USRP2 firmwa
Hi,
Sorry for my unclear suggestion before.
In the "fm_tx_2_daughterboards.py" code, just refer to the code of USRP
setting and make the same change for benchmark_tx.py.
The code start from
#
# Set up USRP to transmit on both daug
Hi,
Thank you for your advice.
>It seems you have two daughterboards on one USRP1, and you want to
communicate with these two daughterboards.
Yes, that's right.
I want to use my dual-db program in /usr/share/example/digital.
I saw "fm_tx_2_daughterboards.py", but that program isn't use digita
Has anyone tried using the fpga code developed under gr-bluetooth to allow
aliasing (i.e. u2_rev3_alias.bin)? I've tried running it on my USRP2 and
cannot get usrp2_probe to find the attached USRP2. I believe I am using the
u2_flash_tool correctly, as I can reflash the sd card with the original
Hi,
It seems you have two daughterboards on one USRP1, and you want to
communicate with these two daughterboards.
Maybe you could take a look at fm_tx_2_daughterboards.py first(in
/gnuradio-examples/python/usrp/.).
>From your code, I think you didn't modify the USRP setting that causes your
code
Dear Josh,
I have sorted out the PPS signal problem. It was the splitter that has the
problem and now I am able to output 5v signal from it.
I tried to use an array of 2 and 3 usrp2 and it worked fine. However, the
block still doesn't work for my 4 USRP2. I see this error when I use them
all:
*
Hi
bcdDevice is 0.00 for the verbose lsusb output. Also there doesn't seem
to a be a burn-usrp4-eeprom anymore but there is a burn-db-eeprom,
unless I'm missing something.
Craig Tong
Radar Remote Sensing Group
University of Cape Town
On 23/07/2010 19:49, Thomas Tsou wrote:
On Fri, Jul 23,
28 matches
Mail list logo
