Basic analog USRP2 transmitter

I have tried transmitting an analog signal from one USRP2 to another,
but
when I run usrp2_fft.py on the rx computer, there is no receive signal.
The
analog signal is supposed to be two tones at 350 and 440 HZ transmitted
at
2.6GHz. Can anyone help me figure out what I am doing wrong?

I have tried using GRC, but at the most up to date version does not work
with Fedora, which is the OS that I have to use, this is for a research
project with a professor at my university, and the mandate is to use
Fedora,
this does not look like it will change in the near future.

Alex

On 11/07/2010 02:00 PM, alexander levedahl wrote:

future.

Alex

I use GRC on Fedora all the time. I have Fedora 11,12 and 13 on my
machines, and I use
GRC on them all the time.

If you installed from a recent GIT source, GRC installs as
“gnuradio-companion” to not conflict
with another piece of software called grc.


Principal Investigator
Shirleys Bay Radio Astronomy Consortium

Let me rephrase this. I CANNOT USE GRC. The latest version does not
work
with the OS that I have, and nobody here has any idea about how to
follow
the instructions to compile from source files. So using GRC IS NOT AN
OPTION. We have to program in GNU radio using python scripts, NOT GRC.

Alex

On 11/07/2010 04:29 PM, alexander levedahl wrote:

Let me rephrase this. I CANNOT USE GRC. The latest version does not
work with the OS that I have, and nobody here has any idea about how
to follow the instructions to compile from source files. So using GRC
IS NOT AN OPTION. We have to program in GNU radio using python
scripts, NOT GRC.

Alex
So nobody there, including yourself apparently, has enough clue to
rebuild Gnu Radio from source.
I wonder, out loud, how you’re going to be able to engage in any kind
of serious development if
a simple task (and believe me, it is relatively simple) like
building from the latest GIT source
on a well-supported platform like Fedora is a serious stumbling block.

The fact is, that most people on here are pretty busy folks, and if
we’re going to help debug stuff
for people, having the flow-graphs in a form that is less
time-consuming, both for the developer,
and the folks who are donating their time to help you debug, just
makes a lot of sense.

It’s vastly easier to spot obvious errors quickly in a GRC flow-graph
than to delve into someones
Python code. GRC is a great prototyping tool, and it’s totally
worth the effort to get it
going. Some initial pain perhaps (although, really, doing a
build/install from GIT for all recent
Fedora instantiations is very straightforward–use the BuildGuide
that’s on the gnuradio website).


Principal Investigator
Shirleys Bay Radio Astronomy Consortium

On 11/07/2010 02:00 PM, alexander levedahl wrote:

future.

Alex

You haven’t mentioned which daugtercard(s) you’re using on the TX and RX
sides.

Also, your tones are going to be offset from the center frequency by
less than 1KHz, so they’ll
be hard to see in the DC-offset removal process.

Try tuning your receiver up or down a couple of KHz and see if your
tones show up in
the FFT.


Principal Investigator
Shirleys Bay Radio Astronomy Consortium

Looking through those instructions I realized why Microsoft makes so
much
money, when you install programs on a windows machine the OS does it for
you, whereas with linux it requires knowing what a tarball is, what
cloning
a repository means, what a git viewer is, what this sentence means “It
will
show you all of the branching and merging, diffs, etc.”, comprehending
“./bootstrap”, and whether or not you need to run that command,
comprehending “./configure”, comprehending “make”, knowing what to do if
when you try and run “sudo” that fails, and how to give an account sudo
privelege, comprehending “git clean -d -x -f”, comprehending “yum
install
qt4-devel qwt-devel qwtplot3d-qt4-devel PyQt4-devel”, knowing what
bootstrap, configure, make means. When I clicked on the “Fedora
installation instructions” page it gets even worse:

yum install gnuradio usrp
Some one who doesn’t know that installing stuff for USRP does not
install it
for USRP2 will run this and then become confused.

$ yum groupinstall “Engineering and Scientific” “Development Tools”
$ yum install fftw-devel cppunit-devel wxPython-devel libusb-devel
guile boost-devel alsa-lib-devel numpy gsl-devel python-devel pygsl
python-cheetah python-lxml PyOpenGL
$ yum install PyQt4-devel qwt-devel qwtplot3d-qt4-devel (The pkg names
depend on the version of Fedora. These work for 12)

WTF?

And then there is a set of instructions on what to do for the USRP but
not
the USRP2, for someone NOT familiar with linux, they will get lost at
this
point. But lets say that we have USRP,

The version of sdcc packaged for Fedora 11 (2.9.0) does not work with
GNU
Radio 3.2. It is possible to use the version packaged for Fedora 10
(2.8.0)
available for
i386http://download.fedoraproject.org/pub/fedora/linux/releases/10/Everything/i386/os/sdcc-2.8.0-2.fc10.i386.rpmand
x86_64http://download.fedoraproject.org/pub/fedora/linux/releases/10/Everything/x86_64/os/sdcc-2.8.0-2.fc10.x86_64.rpm.
Alternatively sdcc 2.9.0 can be compiled from source available
herehttp://sdcc.sourceforge.net/
.

On earlier versions of Fedora you have to download the _Small Device C
Compiler http://sdcc.sourceforge.net_/, build and install yourself.

will drive anyone NOT FAMILIAR with linux nuts. Windows comes with a
couple
of different versions and does its best to not make the above problems
apparent, such that if I have software that was designed for windows
'98, it
won’t fail for windows '98 version 1.1, and will still work on XP and
possibly Vista and 7.

Based on the linux commands I saw, if one mistake gets made, everything
will
get screwed up and, unless that user has a high degree of familiarity
with
linux, this problem will sit there and never be resolved.

Alex

P.S. You might be able to avoid a lot of these problems if you wrote a
tutorial on how to write a python script that does this instead of an
infinite number of tutorials on how to write a python script that
transmits
350Hz and 440Hz tones over speakers and a grc diagram that transmits the
same tones over the air.

On 11/07/2010 06:59 PM, alexander levedahl wrote:

qwtplot3d-qt4-devel PyQt4-devel", knowing what bootstrap, configure,
python-cheetah python-lxml PyOpenGL
GNU Radio 3.2. It is possible to use the version packaged for Fedora
will drive anyone NOT FAMILIAR with linux nuts. Windows comes with a
Alex

Apples to oranges comparison. Linux distributions have “installers” for
100s and 100s of
of different pre-configured, ready-to-go applications, just like
Windows does. Those installers
take care of any pre-requisites required, typically. There are
pre-packaged versions of Gnu Radio
available for Fedora, including GRC. Those pre-packaged versions are
somewhat out-of-date
with respect to the current development (actually, sometimes really
out-of-date). On Fedora,
Using the “System->Administration->Add/Remove Software” function
allows you to select
from hundreds and hundreds of categorized software and install it over
the net, generally
utterly seamlessly. Try going in there and typing a search term, like
“gnuradio” or
“plotting”, or “scientific” or “engineering”, or “radio”, or
“algebra”, or “simulation”, or
“electronics”. Some of what you find there likely also has versions
for Windows.

It’s up to the maintainers of Linux-distribution-specific “packages” as
to what and when they
“package” tools like Gnu Radio. On Fedora 12, for example, the
version of GRC they package
is horribly out-of-date. The Gnu Radio project can’t “force” Fedora,
Ubuntu, or any other
Linux distribution project to update their packages–it’s not up to
us, it’s not done by us, it’s
outside of the Gnu Radio projects immediately responsibility.

Gnu Radio is an on-going development platform whose intended audience is
engineering and
science folks want to “do stuff” with software defined radio. It’s
still very much a moving target,
and as such, some amount of “pain” involving building from sources is
to be expected.

It is the case that the pre-packaged-for-particular-Linux-distribution
instances of Gnu Radio
are “born obsolete”, since Gnu Radio is an evolving, dynamic thing.
Most of us here on the
list are involved, in one way or another, with the development of that
“ongoing dynamic thing”,
so it’s natural that we’d suggest that people “install from GIT
source”.

It’s rather awkward to in one breath complain that the version of Gnu
Radio that has been
‘packaged’ for your Linux variant isn’t up-to-date, and then complain
when we suggest methods
of becoming up-to-date. It’s simply not practical or possible for the
“pre-packaged” Gnu Radio
environments that are available for various Linux distributions to be
up-to-the-minute with
respect to the development process. Fact of life.

The exact same thing happens with commercial software in the Microsoft
world, except that the
“public” doesn’t get to see the “internal machinations”–they only get
to see the packaged, slick,
“end results”, which are typically released at a fairly slow pace
(although that’s not always true).
In the open source world, the “public” gets “visibility” into the
development process, and if they
want to benefit from incremental functional improvements that haven’t
yet been slickly packaged,
then there is necessarily some pain involved in getting what amounts
to early-access to those
functional improvements, prior to “slick” packaging.

P.S. You might be able to avoid a lot of these problems if you wrote a
tutorial on how to write a python script that does this instead of an
infinite number of tutorials on how to write a python script that
transmits 350Hz and 440Hz tones over speakers and a grc diagram that
transmits the same tones over the air.

I’m trying to parse that sentence, and coming up blank. Want to try
again? :slight_smile:

Alex,
I know you’re frustrated. But, let me make a few points:

  1. As with a lot of things that seems complicated at first, some basic
    knowledge helps simplify things greatly. I’d suggest checking out a
    basic
    linux book at your library. Perhpas some others on the list can suggest
    some.
  2. Linux isn’t that scary, and most problems you encounter can be fixed
    up
    with a bit of googling.
  3. GNU Radio + USRP isn’t an easy thing. It requires knowledge of
    programming, DSP, digital communications, and maybe even some basic
    electronics/circuits. If you already have that knowledge, why not take a
    bit
    more time and get some linux knowledge under your belt. The two (at this
    point) really go hand-in-hand.

Don’t be discouraged. Also, civility, humility, and pleasantness will
help
you greatly in getting help from this list of folks like me - spending a
Sunday evening with my 1 year-old on my lap, writing an email to a
stranger
who’s having a problem with GNU Radio.
-William

On Sun, Nov 7, 2010 at 6:59 PM, alexander levedahl <

This is the third time I have asked for help, each time I have tried to
be
civil, but I get responses back telling me to learn linux, not help with
GNU-Radio/USRP2. Or if they are help with GNURadio/USRP2, it is with
GRC,
which doesn’t work with whatever version of Fedora I happen to have.

My initial request for help was a couple of weeks ago and was this:

I just started using the USRP2 with GNURadio. I have made a script that
uses the gnuradio library, but it does not try and interface with the
USRP2.

How do you do this? Or alternatively is there a list of gnuradio
functions
that I can look at that has how to set this up? I have tried doing a
google
search for this, but it turns up nothing that I have found to be
helpful.

Thanks
Alex

The response was for GRC, which doesn’t work with whatever version of
Fedora
I have; however, by looking through the examples I tried to scrape
together
something, that didn’t work.

My second request for help was this:

I have tried transmitting an analog signal from one USRP2 to another,
but
when I run usrp2_fft.py on the rx computer, there is no receive signal.
The
analog signal is supposed to be two tones at 350 and 440 HZ transmitted
at
2.6GHz. Can anyone help me figure out what I am doing wrong?

This included the python script that I had written; I did not get any
responses.

My third request:

I have tried transmitting an analog signal from one USRP2 to another,
but
when I run usrp2_fft.py on the rx computer, there is no receive signal.
The
analog signal is supposed to be two tones at 350 and 440 HZ transmitted
at
2.6GHz. Can anyone help me figure out what I am doing wrong?

I have tried using GRC, but at the most up to date version does not work
with Fedora, which is the OS that I have to use, this is for a research
project with a professor at my university, and the mandate is to use
Fedora,
this does not look like it will change in the near future.

Again the response was to use GRC, which does not work with the version
of
Fedora that I have.

Fedora 11 is old and no longer updated. Upgrade your fedora.

As I mentioned in my initial request for help, I cannot change the
version
of Fedora that I have. It is mandated by a person who at the beginning
of
this semester made the decision to use this specific OS and it cannot be
changed because of a large amount of software that would have to be
reinstalled. This ordinarily would not be a problem, except for the
fact
that the software has to be installed in a specific manner depending on
the
specific version of the OS and the OS itself. I do not use that
software,
but that is the reason I was given. This again would not be a problem
since
I have a laptop that I can do whatever with, but that doesn’t solve the
problem for everyone else on the project, somewhere between 15 and 25
people. And I have Fedora 13, my inclusion of the statement about
Fedora 11
was to illustrate a point about how confusing the instructions are.

If you make a mistake installing software, its not a big deal, just
google
around, and if you need help, ask for help, polietly and someone will
help. Complaining is not gonna fix anything.

I did ask for help; however, I did not get it, I got people telling me
to
use GRC, which doesn’t work with whatever version of Fedora I happen to
have.

Assuming you actually need to Install sdcc from source, it is no
different
then installing gnuradio from source. 7 simple steps here is the link
from
my google search “sdcc install linux”
http://sdcc.sourceforge.net/doc/sdccman.html/node15.html#sub:Building-SDCC-on-Linux

And what if I don’t understand 75% of phrases in these 7 “simple” steps?

I use Linux, and almost every program i use is a single click install
from
the software center and its free. Your comparing installing binaris in
windows to installing bleeding endge source code in linux. Not a valid
comparision.

Interesting, the one time I actually need to use linux, it is not a
“single
click install.” Someone gave a bash script that installed GNU-Radio,
and
that works as long as I restrict myself to using the sample scripts that
come with GNU Radio, which again is not useful.

  1. As with a lot of things that seems complicated at first, some basic
    knowledge helps simplify things greatly. I’d suggest checking out a
    basic
    linux book at your library. Perhpas some others on the list can suggest
    some.
  2. Linux isn’t that scary, and most problems you encounter can be fixed
    up
    with a bit of googling.

Or perhaps you could suggest some? I also tried googling for help with
USRP2, but got back links for a program I can’t use or links that don’t
help.

  1. GNU Radio + USRP isn’t an easy thing. It requires knowledge of
    programming, DSP, digital communications, and maybe even some basic
    electronics/circuits. If you already have that knowledge, why not take a
    bit
    more time and get some linux knowledge under your belt. The two (at this
    point) really go hand-in-hand.

I have knowledge of DSP, programming (however, I had to start learning
python), digital communications and circuits and electronics. I do not
know
linux. My objective is to learn how to use a USRP2 and I do not have
the
time to also learn linux.

Apples to oranges comparison. Linux distributions have “installers” for
100s and 100s of
of different pre-configured, ready-to-go applications, just like
Windows
does. Those installers
take care of any pre-requisites required, typically. There are
pre-packaged versions of Gnu Radio
available for Fedora, including GRC. Those pre-packaged versions are
somewhat out-of-date
with respect to the current development (actually, sometimes really
out-of-date). On Fedora,
Using the “System->Administration->Add/Remove Software” function
allows
you to select
from hundreds and hundreds of categorized software and install it over
the
net, generally
utterly seamlessly. Try going in there and typing a search term, like
“gnuradio” or
“plotting”, or “scientific” or “engineering”, or “radio”, or
“algebra”, or
“simulation”, or
“electronics”. Some of what you find there likely also has versions
for
Windows.

When I do System-Administration-Add/Remove Software and then search for
grc
I get grc-0.70-6.fc12, which I already have ( or at least am assuming by
the
checkmark next to the little open package box).

P.S. You might be able to avoid a lot of these problems if you wrote a
tutorial on how to write a python script that does this instead of an
infinite number of tutorials on how to write a python script that
transmits
350Hz and 440Hz tones over speakers and a grc diagram that transmits the
same tones over the air.

This sentence was supposed to mean that a tutorial on how to do simple
transmission with USRP2 in python (and not in GRC due to issues
installing
it across different operating systems) would be helpful. I am sorry
that
the meaning was not clear.

I have gone back through the build guide for fedora that is located on
the
GNU radio website, and it does not help with upgrading GRC. GNU radio
is
working fine, but GRC is not.

Alex

I might have made an error here by assuming that since the latest
version of
grc doesn’t come with the build for Fedora 13, it doesn’t work with
Fedora
13. When I have used the add/remove software tool, it tells me that
0.70-6.fc12 is the most up to date version around, and I can’t find
instructions on the gnuradio website for a more recent version.

Alex

I have tried using GRC, but at the most up to date version does not work
with Fedora, which is the OS that I have to use, this is for a research
project with a professor at my university, and the mandate is to use Fedora,
this does not look like it will change in the near future.

Whats the error?

-Josh

On 11/07/2010 07:06 PM, alexander levedahl wrote:

I might have made an error here by assuming that since the latest version of
grc doesn’t come with the build for Fedora 13, it doesn’t work with Fedora
13. When I have used the add/remove software tool, it tells me that
0.70-6.fc12 is the most up to date version around, and I can’t find

oh ah haha. It never dies… Thats an ancient version of GRC before it
became integrated with gnuradio. It probably wont work with a recent
version of gnuradio anyway. I think the gnuradio Fedora package is an
all in one, so if you install that, you get grc. -Josh

On 11/07/2010 09:38 PM, alexander levedahl wrote:

the USRP2.
Fedora I have; however, by looking through the examples I tried to
This included the python script that I had written; I did not get any
I have tried using GRC, but at the most up to date version does not
As I mentioned in my initial request for help, I cannot change the
Fedora 13, my inclusion of the statement about Fedora 11 was to
Assuming you actually need to Install sdcc from source, it is no

fixed up with a bit of googling.

take care of any pre-requisites required, typically. There are
like “gnuradio” or
“plotting”, or “scientific” or “engineering”, or “radio”, or
“algebra”, or “simulation”, or
“electronics”. Some of what you find there likely also has
versions for Windows.

When I do System-Administration-Add/Remove Software and then search
for grc I get grc-0.70-6.fc12, which I already have ( or at least am
assuming by the checkmark next to the little open package box).
See my comment about how packagers for various distributions cannot be
forced to package
newer versions of things (in this case, GRC). No amount of
complaining to this forum can
change that. You can complain to Ford all you want about a GM vehicle
that happens to use
an older part that was originally made by Ford, but really, GM are the
right people to gripe at,
not Ford. I’ll observe that even Fedora 14, which was released only
last week, still bundles
GRC 0.7, rather than a newer version. Nothing that this forum can
do about that.

So, the “fix” is to do an install from source, which as you’ve
discovered, isn’t “one click install”.
That’s rather the nature of the beast.

It’s like the difference between trading in your older and rather less
functional vehicle on a
new one, which only requires that you be able to handle sufficient
amounts of cash, and
deciding to “dive in” and repair the engine, transmission, and
suspension yourself. One of
them is going to, necessarily, require that you learn something about
engines,
transmissions, suspensions, and the appropriate tools for repairing
them.
One of them requires only a suitably-large bank account.

Let’s use another analogy, because, hey, I’m full of them. You buy a
computer from Dell, which
sports a fancy “Intel Inside” sticker. Only you discover that they’re
using a CPU that’s at least
two generations out of date. So you call up the Intel help desk and
berate them for hours about
how your computer is using a two-generations out-of-date CPU, and what
the steaming heck is
Intel going to do for you? Intel will quite-rightly tell you to
complain to Dell, since Intel has been
making much-better CPUs for two years, it’s not Intel’s fault that
Dell are using somewhat-lesser
CPUs in the machines they sell to customers.

So you decide to upgrade your Dell machine yourself, and start bitching
and griping at Intel
and all their friends about how hard it is to upgrade a machine. You
have to know something
about screwdrivers, and anti-static wrist bands, and heatsinks, and
heatsink compound, and
oh crap, you just cut yourself on the sheet metal. You cuss and swear
and say things like
“you see how hard all you engineers at Intel have made my life!, you
see!!!”

am sorry that the meaning was not clear.

I have gone back through the build guide for fedora that is located on
the GNU radio website, and it does not help with upgrading GRC. GNU
radio is working fine, but GRC is not.

Alex

A volunteer group of folks will generally work on that which “turns
their crank”. If that means
that some of the “useful” examples are done in GRC, rather than in
“raw” Python, then so be it.
You’re free to, once you’ve done the necessary learning, put together
examples and tutortials
yourself and submit them to the project. Nobody is going to stop you.

On 11/07/2010 10:16 PM, alexander levedahl wrote:

The person who installed the package on my computer said that he
followed whatever instructions came on the website, so I assume he
installed whatever is the most recent.

Alex

One of the problems is that support for Fedora 11 was dropped quite some
time ago (last year?).
So no further updates will ever be available for Fedora 11. Fedora
12 is about to enter that
state as well, with the release of Fedora 14.

Which means that if you want to do updates, and keep the same basic
Fedora 11 platform, you
have do install from source, and deal with whatever that entails.

That’s annoying, to be sure, but it’s a problem that’s squarely outside
the purview of this
particular forum.


Principal Investigator
Shirleys Bay Radio Astronomy Consortium

Do you have an oscilloscope? Is the transmitter actually transmitting?
-William

On Sun, Nov 7, 2010 at 2:00 PM, alexander levedahl <

On Sun, Nov 07, 2010 at 10:06:13PM -0500, alexander levedahl wrote:

I might have made an error here by assuming that since the latest version of
grc doesn’t come with the build for Fedora 13, it doesn’t work with Fedora
13. When I have used the add/remove software tool, it tells me that
0.70-6.fc12 is the most up to date version around, and I can’t find
instructions on the gnuradio website for a more recent version.

I can’t speak about the Fedora packages, but when building from source
GNU Radio builds and runs fine under Fedora 13, both 32 and 64-bit.

Eric

The person who installed the package on my computer said that he
followed
whatever instructions came on the website, so I assume he installed
whatever
is the most recent.

Alex

On 11/08/2010 03:10 PM, Eric B. wrote:

I’m guessing that the Fedora 14 package is OK too :slight_smile:

Eric

I’ll let you know sometime near the end of this week. My main 'pooter
in the house has quit,
so I’m replacing the mobo and disk drive, and I plan to upgrade to F14
at the same time.

Replacing a Pentium D dual-core with a Phenom II X3.


Principal Investigator
Shirleys Bay Radio Astronomy Consortium

On Mon, Nov 08, 2010 at 03:18:53PM -0500, Marcus D. Leech wrote:

so I’m replacing the mobo and disk drive, and I plan to upgrade to F14
at the same time.

Replacing a Pentium D dual-core with a Phenom II X3.

Thanks!
Eric