Eric Blossom wrote:
Yes. Everything is mblocks and messages. Some of the messages
contain vectors of samples.
Once this is sorted out, embedding a flow graph in an mblock shouldn't
be a big deal.
Perfect, we're on the same track :) I agree with the USRP front end approach
for the final pr
On Thu, Mar 29, 2007 at 01:45:28AM -0400, George Nychis wrote:
>
>
> Eric Blossom wrote:
> > This is probably overkill, but hey, it's only a data structure...
> :D
>
> > For now, ignore the fact that the daemon will be running in another
> > address space. We'll sort that out later. Assume tha
On Thu, Mar 29, 2007 at 02:08:00AM -0400, George Nychis wrote:
>
> George Nychis wrote:
>
> > >
> > >
> > > top-block:
> > >
> > >
> > > application
> > > control block
> > > GUI, whatever
> > >
George Nychis wrote:
>
>
> top-block:
>
>
> application
> control block
> GUI, whatever
> ^
> | cs
> |
>
Eric Blossom wrote:
> This is probably overkill, but hey, it's only a data structure...
:D
> For now, ignore the fact that the daemon will be running in another
> address space. We'll sort that out later. Assume that you've got a
> application (top level mblock) that contains an mblock based
Same loopback code I emailed about earlier; this time I attached the
complete file (modulo some cleanup).
Here's my input file (in stupid x86 short ordering..):
$ hexdump input.txt
000 bbaa ddcc ffee 1100 3322 5544 7766 9988
and then after going through loopback.py and being packed b
On Wed, Mar 28, 2007 at 09:15:17PM -0700, Dan Halperin wrote:
> Eric Blossom wrote:
> >Does either the modulator or demodulator talk to python via messages?
> >
>
> No.
>
> >Can you try this experiment again, using "wait" instead of "stop"?
> >
>
> With either a stop or a wait, there were no
On Wed, Mar 28, 2007 at 08:19:24PM -0400, George Nychis wrote:
>
> Eric Blossom wrote:
> >Hi George,
> >
> >(Yes, I know you're waiting for me... More later on today)
> >
> >On Mon, Mar 26, 2007 at 04:02:48PM -0400, George Nychis wrote:
> >>So from what I understand, a daemon has been suggested f
On Wed, Mar 28, 2007 at 07:37:43PM -0400, George Nychis wrote:
>
>
> Eric Blossom wrote:
> >The basic idea is that there is a small piece of code that knows about
> >both abstractions and how to bridge between them.
> That seems like the best approach.
>
> >Yes. One daemon.
> *clicks the check
On Wed, Mar 28, 2007 at 03:57:14PM -0700, Dan Halperin wrote:
> Hi,
>
> So I made a loopback graph (file source, modulator, demodulator, file
> sink) with a short 1K file in it. The following code works (runs and
> exits without any exceptions):
>
> graph = loopback_graph()
> prin
Hi All,
I was wondering how the amount of "channel width" used can be
controlled and if it is determined by the kind of modulation being
used.
For example, I used tunnel.py (using GMSK modulation) and transmitted
packets using board A and then captured the energy in the air using
usrp_spectrum_s
Eric Blossom wrote:
Hi George,
(Yes, I know you're waiting for me... More later on today)
On Mon, Mar 26, 2007 at 04:02:48PM -0400, George Nychis wrote:
So from what I understand, a daemon has been suggested for inband packet
encoding and decoding that is implemented as an m-block which can
Eric Blossom wrote:
The basic idea is that there is a small piece of code that knows about
both abstractions and how to bridge between them.
That seems like the best approach.
Yes. One daemon.
*clicks the check box*
So this daemon will be allocating the USB channels with the different por
Hi,
So I made a loopback graph (file source, modulator, demodulator, file
sink) with a short 1K file in it. The following code works (runs and
exits without any exceptions):
graph = loopback_graph()
print "starting"
graph.start()
print "started"
print "stop
Hello All--
I am attempting to build a CB radio (26-27 MHz) receiver using the USRP
with the LFRX daughterboard. Currently, a "rubber-ducky" CB antenna is
connected directly to the LFRX and the DDC on the USRP converts the
received signal to baseband.
At the receiver output, I am seeing a roughly
(0) "DarwinPorts-1.0.dmg" is for PPC only and OSX 10.2 and 10.3; it
may or not work on an Intel-Mac or on 10.4; it wasn't designed to
work on an Intel-Mac or 10.4.
(1) The first version that was a universal install (and thus for 10.4
and Intel-Mac) is 1.2.1; start with that or 1.3, or the r
Hi (from a newbie here to Gnu Radio),
Just trying to wet my feet in all this... trying to build the software
on a new Intel Core 2 Duo MacBook with OSX 10.4.9...
Was following the notes from Jon Jacky & Michael Dickens about OSX
installations...
Started the pre-requisites ...
Installed Xcode 2.4
2007/3/27, Trond Danielsen <[EMAIL PROTECTED]>:
2007/3/27, Eric Blossom <[EMAIL PROTECTED]>:
> > Okay, I think I understand. But still, when inspecting the signal with
> > ursp_fft.py, the signal is not at baseband, but offset by approx.
> > 500kHz
>
> 500 kHz seems excessive. Can you post a lin
18 matches
Mail list logo
