Martin,
I've been searching through the mailing list for more information
about synchronizing two USRP boards to create the transmitter for a
4x4 MIMO node. From what I've found, it seems that this is not
currently implemented (see links below for relevant threads). What is
the current status of
Hi everybody,
where can I find on the basic tx the I and Q channel outputs ?
thanks
vincenzo
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
It seems that this change has broken GRC (complains about non-existent
gr.runtime).
Josh, is there an ETA on a fix for this? Any short-term work-arounds in the
meantime?
-Steven
On 8/27/07, Johnathan Corgan [EMAIL PROTECTED] wrote:
I have recently checked in the updates to the hierarchical
Ketan Mandke wrote:
I am part of the Hydra group at UT Austin
(http://hydra.ece.utexas.edu). We have developed a MIMO prototype
utilizing GNU Radio the USRP board. The physical layer for our
design is based on the draft standard for IEEE 802.11n. Our current
system is designed to support 2
I've always wondered why GNU Radio didn't use C++ templates for gr-
blocks (see e.g. the 'gengen' subdirectory in gnuradio-core), since
they generally result in much less written code. Might partly be
that SWIG only recently (as of 1.3.12 or so) added C++ templates to
its bag of tricks?
On Wed, Aug 29, 2007 at 09:40:58PM -0500, Ketan Mandke wrote:
Martin,
Thanks for your response. It is disappointing to hear that the MIMO
support for 4 antennas will not be available for some time.
Addressing your disappointment: This is a free software project.
Code gets written because
On Wed, Aug 29, 2007 at 10:48:07PM -0400, Michael Dickens wrote:
I've always wondered why GNU Radio didn't use C++ templates for gr-
blocks (see e.g. the 'gengen' subdirectory in gnuradio-core), since
they generally result in much less written code. Might partly be
that SWIG only
Another point: Each template type must be individually instantiated
in the code. This is not automated in any way except for the SWIG
MAGIC stuff, but some parts of it probably could be automated via
#define's or something like that. All of this means that instead of
defining some code
