Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
Do you have an oscilloscope? Is the transmitter actually transmitting? -William On Sun, Nov 7, 2010 at 2:00 PM, alexander levedahl alexanderleved...@gmail.com wrote: 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 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
On Mon, Nov 08, 2010 at 03:18:53PM -0500, Marcus D. Leech wrote: On 11/08/2010 03:10 PM, Eric Blossom wrote: I'm guessing that the Fedora 14 package is OK too :-) 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. Thanks! Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
On 11/08/2010 03:10 PM, Eric Blossom wrote: I'm guessing that the Fedora 14 package is OK too :-) 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 http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] 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
#!/usr/bin/env python
from gnuradio import gr
from gnuradio import usrp2
from gnuradio import audio
from gnuradio import eng_notation
from gnuradio.eng_option import eng_option
from optparse import OptionParser
import math
def build_graph(options, args):
#These are set to 440 and 350
freq0 = options.waveform_freq
freq1 = options.waveform2_freq
#This is the USRP2
sink1 = usrp2.sink_32fc(options.interface,options.mac_addr)
DACRate = sink1.dac_rate()
interp = options.interp
amp = .5
scRate = 50e3
cFreq = 1/16*scRate
tWidt = 1/16*scRate
tFreq = 2.6e9
#Sets the tranmsmit center frequency
tx = sink1.set_center_freq(tFreq)
print tx
g = sink1.set_gain(1)
print g
fg = gr.top_block()
ethRate = DACRate/interp
#Frequency generators
src0 = gr.sig_source_f(scRate,gr.GR_SIN_WAVE,int(freq0),amp)
src1 = gr.sig_source_f(scRate,gr.GR_SIN_WAVE,int(freq1),amp)
add0 = gr.add_ff()
#Converts the input samples to complex to transmit to USRP2
f2c = gr.float_to_complex()
#Creates filter for interpolator
chanCoeffs = gr.firdes.low_pass(1.0, scRate, 1000, 3000, gr.firdes.WIN_HAMMING)
print ethRate/scRate
print DACRate
#Upsamples the input stream to transmit to the USRP2
interp = gr.interp_fir_filter_ccf(int(ethRate/scRate),chanCoeffs)
#Plays the two tones over speakers
sink0 = audio.sink(int(scRate))
fg.connect((src0, 0), (add0, 0))
fg.connect((src1, 0), (add0, 1))
fg.connect(add0, sink0)
fg.connect(add0, f2c)
fg.connect(f2c, interp)
fg.connect(interp, sink1)
return fg
def get_options():
usage=%prog: [options]
parser = OptionParser(option_class=eng_option, usage=usage)
parser.add_option(-e, --interface, type=string, default=eth0,
help=Use specified Ethernet interface [default=%default])
parser.add_option(-m, --mac-addr, type=string, default=,
help=Use USRP2 at specified MAC address [default=None])
parser.add_option(-i, --interp, type=int, default=16, metavar=INTERP,
help=Set FPGA interpolation rate of INTERP [default=%default])
parser.add_option(-f, --tx-freq, type=eng_float, default=None,
help=Set carrier frequency to FREQ [default=mid-point], metavar=FREQ)
parser.add_option(--lo-offset, type=eng_float, default=None,
help=set daughterboard LO offset to OFFSET [default=hw default])
parser.add_option(-g, --gain, type=eng_float, default=None,
help=Set TX gain to GAIN [default=mid-point])
parser.add_option(-w, --waveform-freq, type=eng_float, default=440,
help=Set baseband waveform frequency to FREQ [default=%default])
parser.add_option(-x, --waveform2-freq, type=eng_float, default=350,
help=Set 2nd waveform frequency to FREQ [default=%default])
parser.add_option(--sine, dest=type, action=store_const, const=gr.GR_SIN_WAVE,
help=Generate a carrier modulated by a complex sine wave, default=gr.GR_SIN_WAVE)
parser.add_option(--const, dest=type, action=store_const, const=gr.GR_CONST_WAVE,
help=Generate a constant carrier)
parser.add_option(--offset, type=eng_float, default=0,
help=Set waveform phase offset to OFFSET [default=%default])
parser.add_option(--gaussian, dest=type, action=store_const, const=gr.GR_GAUSSIAN,
help=Generate Gaussian random output)
parser.add_option(--uniform, dest=type, action=store_const, const=gr.GR_UNIFORM,
help=Generate Uniform random output)
parser.add_option(--2tone, dest=type, action=store_const, const=2tone,
help=Generate Two Tone signal for IMD testing)
parser.add_option(--sweep, dest=type, action=store_const, const=sweep,
help=Generate a swept sine wave)
parser.add_option(-a, --amplitude, type=eng_float, default=0.1,
help=Set output amplitude to AMPL (0.0-1.0) [default=%default], metavar=AMPL)
parser.add_option(-v, --verbose, action=store_true, default=False,
help=Use verbose console output [default=%default])
(options, args) = parser.parse_args()
return (options, args)
if __name__==__main__:
(options, args) = get_options()
fg = build_graph(options, args)
fg.start()
raw_input('Press enter to quit: ')
fg.stop()
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
On 11/07/2010 02:00 PM, alexander levedahl wrote: 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 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 http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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 Sun, Nov 7, 2010 at 2:05 PM, Marcus D. Leech mle...@ripnet.com wrote: On 11/07/2010 02:00 PM, alexander levedahl wrote: 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 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 http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
On 11/07/2010 02:00 PM, alexander levedahl wrote: 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 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 http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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 http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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 alexanderleved...@gmail.com wrote: 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. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
On 11/07/2010 06:59 PM, alexander levedahl wrote: 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 i386 http://download.fedoraproject.org/pub/fedora/linux/releases/10/Everything/i386/os/sdcc-2.8.0-2.fc10.i386.rpm and x86_64 http://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 here http://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 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
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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. 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. I have knowledge of DSP, programming
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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 On Sun, Nov 7, 2010 at 9:54 PM, Josh Blum j...@joshknows.com wrote: 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 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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 instructions on the gnuradio website for a more recent version. Alex On Sun, Nov 7, 2010 at 9:54 PM, Josh Blumj...@joshknows.com wrote: 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 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
On 11/07/2010 09:38 PM, alexander levedahl wrote: 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 linuxhttp://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. 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
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Basic analog USRP2 transmitter
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 http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
