On Wed, Aug 22, 2007 at 07:31:01PM -0400, Ian Larsen wrote:
> Chris,
>
> This looks great, how does it work out in practice?
> Does simply adding extra buffering in a separate thread eliminate all
> overruns? Do you know the lower limit on how much buffer space you
> need?
>
> If that's the case
On Wed, Aug 22, 2007 at 07:04:29PM -0400, Ed Criscuolo wrote:
> I'm working on a GNU Radio application that demodulates a synchronous
> bitstream from a spacecraft telemetry downlink. Once I have the
> bitstream, I need to get it back onto a wire in order to feed it into
> our existing equipmen
Chris,
This looks great, how does it work out in practice?
Does simply adding extra buffering in a separate thread eliminate all
overruns? Do you know the lower limit on how much buffer space you
need?
If that's the case, it might be possible to implement a Buffer
component that could be used fr
I'm working on a GNU Radio application that demodulates a synchronous
bitstream from a spacecraft telemetry downlink. Once I have the
bitstream, I need to get it back onto a wire in order to feed it into
our existing equipment.
Is it possible to do this by using the ppio_ppdev? I would get t
On Wed, Aug 22, 2007 at 01:46:06PM -0700, Matt Ettus wrote:
> Bahn William L Civ USAFA/DFCS wrote:
> >
> >> That is because the onboard VCO typically won't tune below 2.3 GHz. You
> >> can change line 456 in gr-usrp/src/db_flexrf.py to allow you to try
> >> going lower.
> >>
> >> Matt
> >>
George Nychis wrote:
> There has been some people popping up here and there who are focusing
> working on GNU Radio in C++ only and have re-written some of it. I was
> wondering if anyone has re-written the python RFX daughterboard tuning
> code in C++. If so, I would greatly appreciate it :)
N
Bahn William L Civ USAFA/DFCS wrote:
>
>> That is because the onboard VCO typically won't tune below 2.3 GHz. You
>> can change line 456 in gr-usrp/src/db_flexrf.py to allow you to try
>> going lower.
>>
>> Matt
>>
>
> Is there someplace where the (nominal) tunable ranges of each of the
>
>
> That is because the onboard VCO typically won't tune below 2.3 GHz. You
> can change line 456 in gr-usrp/src/db_flexrf.py to allow you to try
> going lower.
>
> Matt
Is there someplace where the (nominal) tunable ranges of each of the
daughterboards is available?
___
DiX wrote:
> Hi,
>
> I am playing with a program which transmits music with narrow band freq
> modulation between two FLEX2400 broads.
>
> The program works like a charm when I tune to 2.4Ghz with the sentence:
>
> " self.tx.tune(self.subdev._which, self.subdev, freq) ".
>
> But
Hey all,
There has been some people popping up here and there who are focusing
working on GNU Radio in C++ only and have re-written some of it. I was
wondering if anyone has re-written the python RFX daughterboard tuning
code in C++. If so, I would greatly appreciate it :)
- George
_
Hi,
I am playing with a program which transmits music with narrow band freq
modulation between two FLEX2400 broads.
The program works like a charm when I tune to 2.4Ghz with the sentence:
" self.tx.tune(self.subdev._which, self.subdev, freq) ".
But it failed to work if the f
-- Forwarded message --
From: Prasanna Rao <[EMAIL PROTECTED]>
Date: Aug 22, 2007 10:49 PM
Subject: Re: [Discuss-gnuradio] My SRP - Problem deciding on the RF Front
End design.. need help.
To: Chris Albertson <[EMAIL PROTECTED]>
Hello Chris,
Firstly I thank for your sincere adv
On Wed, Aug 22, 2007 at 12:52:02PM +0200, Dominik Auras wrote:
> Hi!
>
> If I were to have an hier-block2 with an infinite number of input and/or
> output streams:
>
> gr.hier_block2.__init__(self, "vma",
> gr.io_signature(1,-1,gr.sizeof_gr_complex*subcarriers),
> gr.io_signature(1,1,gr.size
Hi!
If I were to have an hier-block2 with an infinite number of input and/or
output streams:
gr.hier_block2.__init__(self, "vma",
gr.io_signature(1,-1,gr.sizeof_gr_complex*subcarriers),
gr.io_signature(1,1,gr.sizeof_gr_complex*subcarriers))
# max streams = -1
How would I connect inner basic
14 matches
Mail list logo
