Dear Johnathan and Alexandru Csete,
Because there are many errors so I reinstall fresh ubuntu linux 9.04
(Jaunty) again.
Then I installed gnu radio following instruction from
http://gnuradio.org/redmine/wiki/gnuradio/DebianPackages.
1. Firstly I open Synaptic Package Manager. Then click *S*etting
Thank you Jason, I could able to see the exact waveform of the samples
from One USRP2 to another USRP2. But i found the scaling of the
amplitude when I see from usrp2_fft.py and attaching a Scope Sink (like
oscilloscope scope sink), there is much variance, which usrp2_fft.py is
showing much amp
On 01/27/2010 11:53 PM, Philip Balister wrote:
In a fit of madness, I decided to build gnuradio on the beagleboard.
My current issue is ths error. Does anyone have any thoughts on what
might cause this?
Ignore this. I think the problem was failure to aggressively clean the
source tree I copie
Hi Johnathan,
I'm doing something similar as you did in gr-sounder project, sending a code
modulated as BPSK with the suppplied center frequency, but different code
(which contains 1 and -1 also), and bandwith for the code, which is 32kHz
instead of 32MHz. I used the clk_divider block to down
http://www.twitpic.com/105rzu
I wonder why it disappeared? Maybe coincidence. This was mentioned at
the recent SDR Forum technical conference. SDR Forum has become the
newest buzz word in town, Wireless Innovation Forum (you have to stay
relevant right? You cannot believe how many times
Under usrp/firmware/src I see a directory called "usrp2". This is the
Cypress firmware for USRP2? (while usrp2/firmware is firmware for the
microblaze?)
Is the Cypress USRP1 firmware still kicking around anywhere?
On Wed, Jan 27, 2010 at 2:27 PM, Johnathan Corgan
wrote:
> On Wed, Jan 27, 2010 at
On Thu, 2010-01-28 at 10:45 -0500, Bob McGwier wrote:
> http://www.twitpic.com/105rzu
>
> I wonder why it disappeared? Maybe coincidence. This was mentioned at
> the recent SDR Forum technical conference. SDR Forum has become the
> newest buzz word in town, Wireless Innovation Forum (you ha
> Hi,
> I recall seeing code a while ago for allowing the GNU Radio to do
> Bluetooth sniffing. Any idea on where this is?
>
>
http://sourceforge.net/projects/gr-bluetooth/
Jordan
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lis
On Thu, Jan 28, 2010 at 11:33:55AM -0500, Catalin Patulea wrote:
> Under usrp/firmware/src I see a directory called "usrp2". This is the
> Cypress firmware for USRP2? (while usrp2/firmware is firmware for the
> microblaze?)
Long, long ago, there was a prototype for the USRP, and that ran code
that
On Thu, Jan 28, 2010 at 2:09 PM, Eric Blossom wrote:
> usrp2 is the directory for the second architectural rev of the USRP1
> (Note that when these directories were created, the USRP2 was years
> in the future.) Sorry for any confusion this may have caused.
Thanks for the clarification!
> The US
Hello,
I am installing GNURadio code from the trunk using git on a laptop
running Ubuntu 8.04 and have some build problems.
I follow the instruction for installing the code given in the wiki.
i.e installing the required software using sudo apt-get, installing
boost_1_37.
Then I do ./boot
On Thu, Jan 28, 2010 at 4:05 AM, Makmur Hidayat wrote:
>
> This is the errors:
>
> W: Failed to fetch
> http://au.archive.ubuntu.com/ubuntu/dists/jaunty/Release.gpg Could not
> connect to au.archive.ubuntu.com:80 (91.189.88.46), connection timed out
> [IP: 91.189.88.46 80]
Proxy? Are you behind
Congratulations to the GNU developers !!
http://www.army.mil/-news/2010/01/27/33577-no-knob-radio-the-future-of-warfighter-communications/
"No-knob" radio: the future of Warfighter communications?
Jan 27, 2010
By Sharon Rushen, CERDEC Public Affairs
FORT MONMOUTH, N.J. - U.S. Army engineer
On Wed, Jan 27, 2010 at 8:52 PM, Ian Holland
wrote:
Hi All
I have been trying to set the Tx and Rx frequencies when using an
XCVR2450 with a USRP2, but it seems these keep failing. A snippet of my
source code is below for setting the Tx frequency.
The output of this portion of code is "Failed to
Actually no...its always returning false...
when I use usrp2_fft.py with -f 1000 then output does come but still it is
unable to set the initial frequency though it did receive.
I am still trying to figure out the problem...
On Thu, Jan 28, 2010 at 3:43 PM, Ian Holland wrote:
> On Wed, Jan 27, 2
The -f argument to usrp2_fft.py is the frequency. By putting "-f 1000"
you are telling the system to try to tune the xcvr2450 to 1 kHz. The
specified range is 2.4-2.5 GHz and 4.9 to 5.9 GHz. 1 kHz is WAY outside
of that range. I would suggest you try something like:
usrp2_fft.py -f 5.7G
Ya..i know...but if i put a legal value..its saying cannot receive on
channel 0..its strainge..but dont know what is happening...
can somebody please help...
its happening with all the example programs...I have also now modified quite
a few example scripts which are for usrp older version to work w
Hi Matt
I have tried usrp2_fft.py -f 2.4G and also usrp2_fft.py -f 5.7G as you
suggest below. In both cases, the fft window opens but no trace is
displayed, and I see the following output in the terminal:
usrp2: channel 0 not receiving
usrp2::rx_sample() failed
I only recently received my USRP2s
Your firmware and fpga images on the sd card are probably out of sync.
You can find images here: http://gnuradio.org/releases/usrp2-bin/trunk/
and here are instructions on how to burn:
http://gnuradio.org/redmine/wiki/gnuradio/USRP2UserFAQ
-Josh
On 01/28/2010 06:14 PM, Ian Holland wrote:
Hi
Dear all,
My USRP has been working great until recently. Today, I tried testing with
usrp_benchmark.py and got this, but not always. I tested it with gnuradio 3.1.3
and gnuradio 3.2.2 and got the same results.
Testing 2MB/sec... usrp_open_interface:usb_set_alt_interface: failed
could not set alt
I forgot one thing I observed too:
sometimes I get uUuU when I execute usrp_benchmark.py, but it freezes on the
line "Testing 2MB/sec..." and I have to killed it.
--
Reynaldo
> Dear all,
>
> My USRP has been working great until recently. Today, I tried testing with
> usrp_benchmark.py and got
Thanks Josh
This partially fixed the problem, in the sense that samples are now
displayed on the fft window when running usrp2_fft.py, and it no longer
says "channel 0 not receiving". However, it still fails to set the
frequency of the receiver. Also, when I run usrp_siggen.py, I still get
the sam
On 01/28/2010 09:17 PM, Ian Holland wrote:
Thanks Josh
This partially fixed the problem, in the sense that samples are now
displayed on the fft window when running usrp2_fft.py, and it no longer
says "channel 0 not receiving". However, it still fails to set the
frequency of the receiver. Also,
Hi Josh
>The xcvr has a high band and a low band, which means there is a gap in
>the tunable frequency range for the xcvr. Therefore, the
>"auto-calculated mid-point frequency" is an invalid frequency for the
>xcvr. Pick a frequency in the high band or low band range:
>#define LB_FREQ_MIN U2_D
It could be failing to lock. You may want to watch the debug port on the
usrp2. If the lock detect is failing, it will print out on the serial
console. attach a 3.3v level serial port
On 01/28/2010 10:09 PM, Ian Holland wrote:
Hi Josh
The xcvr has a high band and a low band, which means ther
Hey Ian,
How did the problem get fixed? I mean what frequency you are setting with
the "-f" option?
Regards,
Manav
On Thu, Jan 28, 2010 at 10:17 PM, Ian Holland
wrote:
> Thanks Josh
>
> This partially fixed the problem, in the sense that samples are now
> displayed on the fft window when runnin
26 matches
Mail list logo
