Re: [Discuss-gnuradio] scalar and vector streams
thanks Josh, it worked fine! vincenzo PS to obtain an ifft instead of a fft,i should use gr.fft_vcc with the boolean argument "forward" set to false, right? PS2 is there any other paper available describing the gnuradio blocks, apart from DaweiShen's tutorial 9? 2007/2/18, Josh Blum <[EMAIL PROTECTED]>: you should use gr.stream_to_vector(nbytes, fft_size)-->fft-->gr.vector_to_stream(nbytes, fft_size) nbytes will be 8 for complex data input/output -Josh Vincenzo Pellegrini wrote: > hello, > first of all thanks to everybody in the list for the huge amount of > suggestions about hard-disk reading speeds I was provided with a few > days ago. :) > > then another question: which is the wisest way to convert a scalar > stream to a vector stream and then back to a scalar stream within a > python flow graph.. if there is one, of course! > > what I'm trying to do is: > > source_c--->gr.fft_vcc--->rest_of_the_flow_graph_c > > is this reasonable? > > > best regards > vincenzo > > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > -- Vincenzo Pellegrini ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] scalar and vector streams
On 2/19/07, Vincenzo Pellegrini <[EMAIL PROTECTED]> wrote: PS2 is there any other paper available describing the gnuradio blocks, apart from DaweiShen's tutorial 9? There is a gr-howto-write-a-block module within SVN that shows how to write a block and has an XML document describing what is going on. http://gnuradio.org/trac/browser/gnuradio/trunk/gr-howto-write-a-block Brian ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] AD9862 Functionality
I am trying to figure out how the AD9862 MxFE is setup and I had a few questions for anyone who may be able to answer them. RX 1. Is the internal DLL used to sample faster than 64MSPS? If so, what is the DLL rate? Is it possible this would ever want to be used? 2. Is the Hilbert Filter ever used? TX 1. Is the Hilbert Filter ever used? 2. Is the NCO ever used? 3. Is the interpolation filter ever used? 4. Is the fixed [Fs/4,Fs/8] selectable mixer ever used? 5. Is the TX data ever sent as real-only instead of I/Q from the FPGA when it is actually a complex signal? Aux 1. Are any of the auxiliary ADC/DACs used for AGC/VCO setting? Thanks, Brian ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] scalar and vector streams
thanks Josh, (yes.. I'm trying to move as near as possible to ofdm on the python level) before diving into c++ block designing. I usually watch the doxygen.. but the point is: how can I be sure.. and learn details about the usage... eg. the question about gr_fft you've just kindly asked.. .. shall I just guess and then bother some experienced guy on the list? :) for example @ the moment I'm looking for a block that can map bytes to symbols.. but how can I learn if gr.chunks_to_symbols can be a candidate.. and how to use it? I mean: tutorial 9 is fine for the blocks it covers.. but for the others? best regards vincenzo On Mon, 2007-02-19 at 09:59 -0500, Josh Blum wrote: > Yes, change the boolean value to false for an ifft (sounds like ofdm). > > The best thing describing the gnu radio blocks is the class list > http://gnuradio.org/doc/doxygen/ > > The documentation is poor but it will tell you what blocks exist in > the project. > > -Josh > > On 2/19/07, Vincenzo Pellegrini <[EMAIL PROTECTED]> wrote: > > thanks Josh, > it worked fine! > > vincenzo > > PS > to obtain an ifft instead of a fft,i should use gr.fft_vcc > with the boolean argument "forward" set to false, right? > > PS2 > is there any other paper available describing the gnuradio > blocks, apart from DaweiShen's tutorial 9? > > 2007/2/18, Josh Blum <[EMAIL PROTECTED]>: > you should use gr.stream_to_vector(nbytes, > fft_size)-->fft-->gr.vector_to_stream(nbytes, > fft_size) > > nbytes will be 8 for complex data input/output > > -Josh > > Vincenzo Pellegrini wrote: > > hello, > > first of all thanks to everybody in the list for the > huge amount of > > suggestions about hard-disk reading speeds I was > provided with a few > > days ago. :) > > > > then another question: which is the wisest way to > convert a scalar > > stream to a vector stream and then back to a scalar > stream within a > > python flow graph.. if there is one, of course! > > > > what I'm trying to do is: > > > > source_c---> > gr.fft_vcc--->rest_of_the_flow_graph_c > > > > is this reasonable? > > > > > > best regards > > vincenzo > > > > > > > > ___ > > Discuss-gnuradio mailing list > > Discuss-gnuradio@gnu.org > > > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > > > > -- > Vincenzo Pellegrini > ___ > 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
[Discuss-gnuradio] [EMAIL PROTECTED] Open Source track during Symposium
Please forward this to other appropriate lists. Thanks, Philip 2007 Virginia Tech Symposium on Wireless Personal Communications http://wireless.vt.edu/symposium.htm June 6-8, 2007 Special Track for Open Source Software Defined Radio. For the 16th annual Wireless Symposium, [EMAIL PROTECTED] will host a special track focused on Open Source Software Defined Radio. [EMAIL PROTECTED] invites presentations related to Open Source SDR based on projects such as; GNU Radio , High Performance Software Defined Radio (HPSDR), SDR-1000 , SCARI Open , and [EMAIL PROTECTED]'s own OSSIE . If interested, please submit a 500 word abstract, to [EMAIL PROTECTED], that describes the planned presentation. Please use "Open SDR abstract" in the subject line. Presentations should address the following subjects, and how open source software radio helped researchers achieve their goals. Presentation length is thirty minutes. Software Radio Frameworks - GNU Radio - Software Communication Architecture Applications of Open Source SDR - Modulation/Demodulation - MANET's - Spectrum Access - Cognitive and Adaptive Radios - Networking Benefits of Open Source SDR Hardware for Open Source SDR Basically, if you have benefited from Open Source SDR, tell us about it! ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] trellis imported on GRC
Josh,
I think the "trellis" part of GRC is ready for prime time.
All my tests work so far and produce the expected results.
I am attaching the following files:
trellis.py (all grc trellis defs)
__init__.py
Conversion.py (I spoted a bug in the chunks_to_symbols block and I
corrected it)
Sinks.py (I added the "numerical display block that Martin Dvh
developed--is currently part of the grnuradio trunk")
also attached find an example graph with corresponding help files
that tests a simple convolutionally encoded QPSK system.
Let me also take a minute and thank you for your contribution. I believe
is very important especially for those of us who need to educate
students: with GRC a student can start using gnuradio in less than a
week! I am definately planning to test this hypothesis over the summer
with a group of undergrads.
My wish list for GRC at this point includes:
1) A way to build hierarhical block diagrams, ie, group a bunch
of blocks together and define a new block so I can reuse it within GRC.
2) global variables of type string and vector
(so that I can define globally some filenames and some constellations
that are used in multiple blocks).
Thanks
Achilleas
"""
GNU Radio Companion is a graphical interface into the GNU Radio project.
Copyright (C) 2007 Josh Blum
GNU Radio Companion is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
GNU Radio Companion is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
"""
"""
Trellis/Misc.py
Josh Blum
"""
from DataType import *
from gnuradio import gr
from SignalBlockDefs import *
def Encoder(sb):
import Constants
from gnuradio import trellis
type = Enum([('Byte-->Byte', (trellis.encoder_bb, Byte(),Byte())),
('Byte-->Short', (trellis.encoder_bs, Byte(),Short())),
('Byte-->Int', (trellis.encoder_bi, Byte(),Int())),
('Short-->Short', (trellis.encoder_ss, Short(),Short())),
('Short-->Int', (trellis.encoder_si, Short(),Int())),
('Int-->Int', (trellis.encoder_ii, Int(),Int())),
],3)
sb.add_input_socket('in', Variable(type, index=1))
sb.add_output_socket('out', Variable(type, index=2))
sb.add_param('Type', type, False, type=True)
sb.add_param('File Path', FileOpen(Constants.DEFAULT_FILE_PATH))
sb.add_param('Initial State', Int())
sb.set_docs('''Trellis Encoder. For the time being the underlying FSM
can only be read from a file...''')
def make(fg, type, filename, s0):
fsm=trellis.fsm(filename.parse())
block = type.parse()[0](fsm, s0.parse())
return block
return sb, make
def Metrics(sb):
from gnuradio import trellis
type = Enum([('Complex', (trellis.metrics_c,
Complex(),ComplexVector())),
('Float', (trellis.metrics_f, Float(),FloatVector())),
('Int', (trellis.metrics_i, Int(),IntVector())),
('Short', (trellis.metrics_s, Short(),ShortVector())),],1)
sb.add_input_socket('in', Variable(type, index=1))
sb.add_output_socket('out', Float())
sb.add_param('Type', type, False, type=True)
sb.add_param('Output cardinality', Int())
sb.add_param('Dimensionality', Int())
sb.add_param('Constellation', Variable(type, index=2))
sb.add_param('Metric Type',
Enum([('Euclidean', trellis.TRELLIS_EUCLIDEAN),
('Hard Symbol', trellis.TRELLIS_HARD_SYMBOL),
('Hard Bit', trellis.TRELLIS_HARD_BIT)],0))
sb.set_docs('''Generate metrics required for Viterbi or SISO
algorithms.''')
def make(fg, type, O, D, Con, MetrType):
block = type.parse()[0](O.parse(), D.parse(), Con.parse(),
MetrType.parse())
return block
return sb, make
def Viterbi(sb):
import Constants
from gnuradio import trellis
type = Enum([('Byte', (trellis.viterbi_b, Byte())),
('Short', (trellis.viterbi_s, Short())),
('Int', (trellis.viterbi_i, Int())),
],1)
sb.add_input_socket('in', Float())
sb.add_output_socket('out', Variable(type, index=1))
sb.add_param('Type', type, False, type=True)
sb.add_param('File Path', FileOpen(Constants.DEF
Re: [Discuss-gnuradio] AD9862 Functionality
On Mon, Feb 19, 2007 at 10:11:38AM -0500, Brian Padalino wrote: > I am trying to figure out how the AD9862 MxFE is setup and I had a few > questions for anyone who may be able to answer them. > > RX > 1. Is the internal DLL used to sample faster than 64MSPS? If so, > what is the DLL rate? Is it possible this would ever want to be used? > 2. Is the Hilbert Filter ever used? > > TX > 1. Is the Hilbert Filter ever used? > 2. Is the NCO ever used? > 3. Is the interpolation filter ever used? > 4. Is the fixed [Fs/4,Fs/8] selectable mixer ever used? > 5. Is the TX data ever sent as real-only instead of I/Q from the > FPGA when it is actually a complex signal? > > Aux > 1. Are any of the auxiliary ADC/DACs used for AGC/VCO setting? > > Thanks, > Brian Hi Brian, > RX > 1. Is the internal DLL used to sample faster than 64MSPS? If so, > what is the DLL rate? Is it possible this would ever want to be used? No. IIRC the A/D won't run faster than 64MS/s. > 2. Is the Hilbert Filter ever used? No. > TX > 1. Is the Hilbert Filter ever used? No. > 2. Is the NCO ever used? Yes, all the time (both coarse and fine) > 3. Is the interpolation filter ever used? Yes, always. > 4. Is the fixed [Fs/4,Fs/8] selectable mixer ever used? Yes. > 5. Is the TX data ever sent as real-only instead of I/Q from the > FPGA when it is actually a complex signal? No, we always send I/Q to the 9862. There are a couple of use cases where you might want to send real data, but we don't implement them. > Aux > 1. Are any of the auxiliary ADC/DACs used for AGC/VCO setting? Yes, all of them. Details depend on the specific daughterboard. The PLLs are controlled over SPI or I2C. The code that sets up the AD9862's is contained in usrp_basic.cc and usrp_standard.cc. Most of it is in the constructors. You may also want to take a look at the USRP motherboard schematic to see how everything is wired together. The aux DAC/ADC's are all run to the daughterboards. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] scalar and vector streams
On Mon, Feb 19, 2007 at 04:37:18PM +0100, Vincenzo Pellegrini wrote: > thanks Josh, > > (yes.. I'm trying to move as near as possible to ofdm on the python > level) > before diving into c++ block designing. > > I usually watch the doxygen.. but the point is: > how can I be sure.. and learn details about the usage... eg. the > question about gr_fft you've just kindly asked.. > .. > shall I just guess and then bother some experienced guy on the list? :) > > for example @ the moment I'm looking for a block that can map bytes to > symbols.. but how can I learn if gr.chunks_to_symbols can be a > candidate.. and how to use it? > I mean: tutorial 9 is fine for the blocks it covers.. but for the > others? There are a couple of ways to map bytes to symbols. gr.chunks_to_symbols is the most general. It's usually used with gr.packed_to_unpacked_bb in front of it. That lets you split your byte stream into k-bit chunks for use with gr.chunks_to_symbols. http://gnuradio.org/doc/doxygen/classgr__packed__to__unpacked__bb.html http://gnuradio.org/doc/doxygen/classgr__chunks__to__symbols__bc.html Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: question on GNU Radio
On Mon, Feb 19, 2007 at 12:49:04PM -0800, Candy Yiu wrote: > Hi Eric, > > I never meet you but just have some question which I guess no one can > answer. > We are trying to build a smart antenna using the USRP board. I watched > the video which you guy gave a talk about it and mention it can support > up to 4 tx and 4 rx (there are 4 A/D as well). I was wondering if you > guy have a daughter board which has two tx and rx or any tip to connect > two daughter board? > > thanks a lot, > Candy > > Portland State University To use 4 in's and 4 out's with the USRP you'll need to use two "Basic Rx" and two "Basic Tx" daughterboards. There are two main constraints: FPGA space USB bandwidth (32MB/s total) We provide standard FPGA configurations with: (a) 2 receive paths (with half-band filters) and 2 transmit paths. or (b) 4 receive paths (no half-band filters) and 0 transmit paths. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] smart antenna idea
Hi everyone, I have some question on the possibility of making a smart antenna using USRP board. Before I really go into the sea (I don't want to drain), I want like to get some help see if it is even possible. It operates at 2.4GHz. We already have the 2.4GHz daughterboards. But I was wondering if we want to do 4 elements (4tx and 4rx at the same time). Can we use two USRP board and somehow combine the signal somewhere (may be using another FPGA or laptop) to beamform? any idea would help. Thanks, Candy Yiu ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Block inspection for GRC
Hello! I'm trying to find a way to avoid writing some wrapper or description for every block to be used in GRC. I know there are some properties that can be found out, like the number of inputs and outputs, the names of functions of an object (find all setters). I had a look at the inspection module, and pyalamode form wx is really nice doing what I want. Still, I want to make the Companion do this things. Questions: * details is commented as "really only for internal use". Is any information in details that cannot be found in the signatures or elsewhere? I tried to access members of details and my python shell crashed. * I once read about the connection magic, like connecting to an audio sink connects to left and right channel if not stated otherwise. I read gnuradio-core/src/python/gnuradio/basic_flowgraph.py but I cannot find the responsible code. Any hint? I'd like to make audio sources connectible per channel or as a single sink. * Which properties are not visible/inspectable from python and need extra information? I guess some blocks need a priori assumptions, which would have to be hinted to find all properties. Of course grouping has to be done, but idealy some information about what kind of block it is will be some day inspectable. * Any nice way to find out what can be imported from the gnuradio module? * How can I find out which sample rates are supported by a block, especially audio blocks? I'd like to have the Companion search the gnuradio module for blocks, examine the blocks, like finding i/o signatures and types, readable properties, access functions (setters), and automagically group them. When a new block is contributed to gnuradio, the Companion gets its properties and the block is usable by simply restarting the Companion. Patrick -- Engineers motto: cheap, good, fast: choose any two Patrick Strasser Student of Telematik, Techn. University Graz, Austria ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] OFDM
In the n4hy developers branch, we spent today adding some new code and cleaning up a huge mess. The old temporary mess (ofdm2) is gone and ofdm has replaced it. This was current with the trunk this after and has the ofdm code. We transmitted with this in the lab today. My apologies for the svn confusion. We have achieved svn stability and are working on code. This will not be kept current with the trunk now until we are done with round one and ready to send and receive data and to give a compact description of the signaling to be used on the channel. Bob -- AMSAT Director and VP Engineering. Member: ARRL, AMSAT-DL, TAPR, Packrats, NJQRP, QRP ARCI, QCWA, FRC. ARRL SDR WG Chair "Taking fun as simply fun and earnestness in earnest shows how thoroughly thou none of the two discernest." - Piet Hine ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] OFDM
Robert McGwier wrote: In the n4hy developers branch, we spent today adding some new code and Congratulations on the cleanup! What is ofdm? What is n4hy? Chris ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] OFDM
On Mon, Feb 19, 2007 at 05:13:28PM -0800, Chris Stankevitz wrote: > Robert McGwier wrote: > >In the n4hy developers branch, we spent today adding some new code and > > Congratulations on the cleanup! > > What is ofdm? > http://en.wikipedia.org/wiki/Orthogonal_frequency-division_multiplexing > What is n4hy? Bob's amateur radio call sign. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USB interface
Dear All As i have mentioned before i'm trying to program the USRP using Simulink. Is there any files should i run first to program the USB interface Thanks - Ask a question on any topic and get answers from real people. Go to Yahoo! Answers. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
