On Wed, 2006-06-14 at 22:09 -0700, Eric Blossom wrote:
> On Thu, Jun 15, 2006 at 12:35:50AM -0400, Ilia Mirkin wrote:
> > Quoting Michael Ford <[EMAIL PROTECTED]>:
> >
> >
> > A somewhat more generic answer than Eric's:
>
> Thanks Ilia.
>
>
Quoting Michael Ford <[EMAIL PROTECTED]>:
Up until now, all of my networking projects have been in C/C++, and I'd like
to think that I'm pretty good with threading in those languages. As with the
previous projects, I feel like threading will be a must. It's true that with
wireless nodes, I won't
On Mon, 2006-05-29 at 04:09 -0700, seph 004 wrote:
> Secondly, I suppose this is a more general question about the vector
> and file source blocks. At what rate are they producing data? For a
> non repeating vector source of n values, how can I detemine the exact
> amount of time it takes for all t
Quoting al davis <[EMAIL PROTECTED]>:
On Friday 12 May 2006 18:24, Ilia Mirkin wrote:
Also, when you do
vector x;
x[0] = 5;
keep in mind that internally it instantiates a new int
object, and then calls operator= on it. The compiler might
optimize this to a certain extent, but certain
nt, but
certainly not to the level of simplicity of a single memory access/write. Note
that the gnuradio interface for, e.g. (general_)work uses these primitive
pointers (i.e. a vector<> of simple arrays). There doesn't really seem to be a
good reason for you to be using vector<> in your c
Would you care to share your C++ implementation (e.g. post a link) so that it
might be critiqued rather than say things like "C++ is slower than C"?
-Ilia
Quoting Achilleas Anastasopoulos <[EMAIL PROTECTED]>:
I have some new data on this.
Going from ANSI-C to C++ (NO Gnuradio) using
STL vecto
Quoting Michael Milner <[EMAIL PROTECTED]>:
Hello,
I was just wondering if anyone has used GNURadio for any non-radio
applications, specifically phone line modulation/demodulation.
It shouldn't be too difficult to design a daughter board for the USRP to
sample phone line voltage (with an appro
Quoting Charles Swiger <[EMAIL PROTECTED]>:
On Mon, 2006-05-01 at 10:38 -0700, Eric Blossom wrote:
On Mon, May 01, 2006 at 12:08:57PM -0400, Chuck Swiger wrote:
> Any general clues what would be causing:
>
> python: ./gr_buffer.h:96: unsigned int gr_buffer::index_add(unsigned
> int, unsigned in
Usually when something like this happens, you have some versioning problems
between interfaces. And indeed your files reveal this:
.h:
atsc_fpll_sptr atsc_make_fpll();
.cc:
atsc_fpll_sptr atsc_make_fpll(double a_initial_freq) { ... }
You need to figure out which interface is the right one, an
Quoting Charles Swiger <[EMAIL PROTECTED]>:
On Wed, 2006-04-26 at 17:53 -0700, Eric Blossom wrote:
Hi Ilia,
Thanks for diving in.
Chuck,
After taking a look at the 0.9 code (atsc_rx.cc), it looks like we were
instantiating atsci_equalizer_lms.
atsci_equalizer_lms uses a single FIR filter.
Quoting Charles Swiger <[EMAIL PROTECTED]>:
On Wed, 2006-04-26 at 17:09 -0400, Ilia Mirkin wrote:
Quoting Charles Swiger <[EMAIL PROTECTED]>:
> ./atsc_equalizer.h:41: error: cannot declare field
> `atsc_equalizer::d_equalizer' to be of type `atsci_equalizer'
&g
Quoting Charles Swiger <[EMAIL PROTECTED]>:
./atsc_equalizer.h:41: error: cannot declare field
`atsc_equalizer::d_equalizer' to be of type `atsci_equalizer'
./atsc_equalizer.h:41: error: because the following virtual functions
are abstract:
./atsci_equalizer.h:159: error: virtual void
atsci_eq
On Thu, 2006-03-16 at 11:10 +0100, EVENNOU Frederic RD-TECH-GRE wrote:
> Hi,
>
> I'm starting to use the GNUradio platform for digital communication
> tests.
> I'm digitizing a radio signal with the GNUradio platform and processing
> it with my computer to extract the I/Q channels (QPSK), but I'm
Sounds like you've recently upgraded from gcc-3.3 to gcc-3.4. The latter
sports a new, incompatible version of libstdc++, which will do bad
things. You need to either recompile cppunit, or compile gnuradio using
the older compiler, taking care that the proper versions of libstdc++
get linked in at
On Wed, 2005-10-26 at 19:15 +, Icsor Onai wrote:
> Hello everybody,
> I tried do a program that use the board mc4020 but
> occured errors when I execute your script.
>
> I would like to know if somebody implemented a fft
> display frequency spotting using the board mc4020.
>
> I find a progra
On Sun, 2005-10-23 at 11:09 -0700, Eric Blossom wrote:
> On Sun, Oct 23, 2005 at 09:35:58AM +0530, Ramakrishnan Muthukrishnan wrote:
> >
> > Folks,
> >
> > I am trying to implement a GUI frontend for the little Softrock40 board
> > from amqrp. I have a very primitive but usable radio up and runni
On Sat, 2005-10-22 at 13:40 -0700, Ges wrote:
> This was compiled as g++
> -I/usr0/local/gr/include/gnuradio test.cc
>
> The gnuradio library path is included in
> LD_LIBRARY_PATH.
gcc doesn't care about your LD_LIBRARY_PATH, only the run-time dynamic
linker does (ld-linux). you need to link in l
On Mon, 2005-10-10 at 15:08 -0400, michael taylor wrote:
> Note: added discuss-gnuradio to cc:
>
> On 10/10/05, Robitaille, Michael <[EMAIL PROTECTED]> wrote:
> > These don't look like to connectors on my USRP.
>
> Doh! Sorry, I leave the daughterboards plugged into my USRP so when
> you asked I
Hi,
I was looking at the USRP wiki page
(http://www.comsec.com/wiki?RfSections4USRP), which says the following:
The connector to use is from MOLEX
* On daughterboards
* Digi-Key PN WM17200-ND
* Datasheet
http://w
I just ran into a project called Comedi (www.comedi.org) which seems to
support, even in RT kernels (or so they claim), a large number of PCI
data acquisition boards (including the Measurement Computing 4020, which
also has a separate driver in gnuradio, but I and at least one other
person I know h
On Sat, 2005-10-01 at 14:57 -0700, William Moerner wrote:
>
> Can anybody help? What is boost??
www.boost.org
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
You simply can't do that. The hardware on the USRP has a DAC capable of
128MS/s (iirc), which means that AT MOST you could get it to put out a
64 MHz signal. If you shift over by 98.7MHz, then that'll be past the
DAC's ability to reproduce an accurate signal (it will in fact fold over
to like 98.7
I wrote something along those lines and sent it to the list, around May
of this year. Search the archives, or see the webpage that describes it:
http://web.mit.edu/imirkin/www/gnuradio/bpsk.html
Note that as is, the code will not allow something like an RRCF filter
due to poor design (first gnurad
On Fri, 2005-05-27 at 04:06 -0700, Eric Blossom wrote:
> There's nothing special about the 20MS/sec. That's just what the
> Measurement Computing PCI DAS 4020/12 A/D board put out. It's what we
> had to work with, so we used it. 16MS/sec real baseband should fine
> with a couple of tweaks.
I ac
On Thu, 2005-05-26 at 21:41 -0700, John E. Don Carlos wrote:
> What is the best way to get hdtv going?
I don't know if anyone's done anything on this topic lately, but this is
what I found from my experience on this:
There is code in gnuradio-0.9 (hint: you don't have to make install
gnuradio-0.9
> > What kernel are you running?
>
> vanilla 2.4.18.
Not sure if this is too relevant, but I remember there was some major
USB reworking around 2.4.22 or so. Before that EHCI didn't really work
very well, IIRC. You may consider upgrading your kernel to something a
little more recent...
-Ilia
As per a previous posting to this list, you have to set the usbfs
filesystem permissions properly. For example, it looks like
none on /proc/bus/usb type usbfs (rw,devmode=0664,devgid=85)
for me. It may be different for you, but this should be enough to
provide the idea. If not, look at the archiv
In my limited experience with this stuff, DO NOT install multiple
versions of wxPython. Just have 2.5.
-Ilia
On Fri, 2005-04-15 at 14:33 -0500, LRK wrote:
> Probably a clue here somewhere.
>
> 'import wx' fails but 'import wxversion' works
>
> Then I can select the version and get a differ
Is there a reason to use bash instead of sh, which is pretty standard
across all UNIX-like systems made in the past 15 years or so...
On Sat, 2005-04-02 at 17:44 -0600, LRK wrote:
> Starting at the top:
>
> FreeBSD does not have bash by default. It gets installed in /usr/local/bin
> so buildit ne
lular CDMA is really
really complicated; I'm just aiming to be able to synchronize and tell a
small handful of codes apart, hopefully in real time.)
Let me know if you have questions, comments, suggestions, etc.
---
Ilia Mirkin
imirkin at mit dot edu
rive the card so as not to get clipping of the
signal/frying of the card, 1V P-P should work OK. Conversely, you only
16 bits of resolution total, so if your signal is smaller, you lose some
of that.
Hope this helps,
Ilia Mirkin
imirkin _at_ mit.edu
_
I'll attach my favorite point script below. I thought it was in the
> source trees, but now I can't find it except on my hard drive.
>
Yeah, the wiki referred to it, but it wasn't in the gnuradio-0.9
tarball.
Thanks for t
Make sure to install the various -dev packages, e.g. python-dev, etc.
I'm not really sure what the exact names are, adjust as appropriate...
This goes for all the libraries that gnuradio requires.
-Ilia
On Sat, 2005-02-26 at 17:08 -0500, John k2ox wrote:
> Hello All,
>
> I need your help. I'
er to get it to work
with the pcHDTV card I need it to be at the lowest setting (but still
turned on), so I am doing the same for the USRP.
---
Ilia Mirkin
[EMAIL PROTECTED]
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
work on
the intel chipset, not sure about nvidia stuff.
Good luck,
Ilia Mirkin
[EMAIL PROTECTED]
On Wed, 2005-02-23 at 22:08 -0800, Joshua Lackey wrote:
> I just received my USRP and I'm having a few issues.
>
> First, some information about my setup. I've got the latest
You know, I had this same problem. Just run bootstrap twice. Not sure
what the problem is though.
-Ilia
On Fri, 2005-02-18 at 23:05 -0800, Matt Ettus wrote:
> >
> >
> > and here is where it loses it:
> >
> > checking boost/shared_ptr.hpp usability... yes
> > checking boost/shared_ptr.hpp presen
rewrite the Makefile.
---
Ilia Mirkin
[EMAIL PROTECTED]
On Thu, 2005-02-10 at 07:17 -0800, mj wrote:
> After changing:
>
> LTASCOMPILE = $(LIBTOOL) --mode=compile $(AS)
> $(AM_ASFLAGS) $(ASFLAGS)
>
> to
>
> LTASCOMPILE = $(LIBTOOL) --mode=compile $(CCAS)
> $(CCASFLAGS) $(
er, if, as Eric notes, the problem is in AM_ASFLAGS not being
expanded properly, you can try just removing that and seeing if it
works. I thought that the problem was the libtool didn't know about "as"
as the compiler, only gcc/derivatives.
---
Ilia Mirkin
[EMAIL PROTECTED]
On Thu,
(CCAS) $(CCASFLAGS)
(basically stick a CC in front of the AS* variables and get rid of the
AM_FLAGS param)
Hope this helps,
Ilia Mirkin
[EMAIL PROTECTED]
On Thu, 2005-02-10 at 04:45 -0800, MJ wrote:
> Hey people,
>
> I wonder if anyone can point me in the right
> direction.I sta
39 matches
Mail list logo
