Firas - This is a known bug, but I don't think it ever made it into
the bug tracker. See the threads from http://lists.gnu.org/archive/html/discuss-gnuradio/2007-10/msg00159.html
. If you have time (I don't for a few weeks), could you please
enter it in as a new bug ticket? Try out the
Hi Michael,
Michael Dickens-2 Wrote :
If you have time (I don't for a few weeks), could you please
enter it in as a new bug ticket? Try out the script from the link,
and see if it doesn't work for you.
I used your code http://www.nabble.com/file/p15502528/test.py test.py and
On 2/15/08, Kshitij Kumar Singh [EMAIL PROTECTED] wrote:
For an application I needed to import some data into my module
and then packetize it. The data
being quite large, comes from a file. My problem is that multiple
instances of top_block aren't allowed,
so once I have imported
Aadil Volkwin wrote:
Hi,
I would like to measure the actual signal that is output from the
module and subsequently input into the ADC.
After looking through the module Datasheet im still not entirely sure
which pins I ought to probe in order to extract this measurement.
I think it may be
On Fri, Feb 15, 2008 at 12:24:41PM -0500, Kshitij Kumar Singh wrote:
Hi,
For an application I needed to import some data into my module
and then packetize it. The data
being quite large, comes from a file. My problem is that multiple
instances of top_block aren't allowed,
so once I
Eric, thanks for the quick reply. The file 'transmit.dat' is a binary
file of
unsigned chars created using gr.vector_sink_b, so when importing it in
this manner, all i get to see is gibberish on the screen...
Johnathan, scoping out the first script works just fine. .. thanks.
Regards,
Kshitij
Nick Stephens wrote:
Hello Everyone - I am doing my best to understand how the TVRx board
works. I have Rev. 3 of the TV board, with MicroTuner module with IF of
~44 MHz.
(Preface - Thanks for your patience, as I am relatively new to GNU radio
and the USRP!)
In my experiment, I have an 80 MHz
On Fri, Feb 15, 2008 at 01:56:50PM -0500, Kshitij Kumar Singh wrote:
Eric, thanks for the quick reply. The file 'transmit.dat' is a binary
file of
unsigned chars created using gr.vector_sink_b, so when importing it in
this manner, all i get to see is gibberish on the screen...
If you don't
Hi,
For an application I needed to import some data into my module
and then packetize it. The data
being quite large, comes from a file. My problem is that multiple
instances of top_block aren't allowed,
so once I have imported my data, I can't run my program. Even if I nest
this inside a
On Fri, Feb 15, 2008 at 03:23:27PM -0700, rick zhang wrote:
Hello folks,
I want to try some working transmitter and receiver GSR package. It seems
most emails in the archive are talking about receiving while I'm interested
in both transmitting and receiving. I prefer to have a system
Hello folks,
I want to try some working transmitter and receiver GSR package. It seems
most emails in the archive are talking about receiving while I'm interested
in both transmitting and receiving. I prefer to have a system with a
bandwidth of 8 MHz, but I'm willing to settle for 6 MHz if
Michael Dickens has implemented some changes to the build system which
have recently been merged into the GNU Radio trunk. These changes
allow finer control over the build; specifically, they allow compiling
and testing individual components of the GNU Radio source tree while
using already
rereading, I see this:
--with-omnithread Use package omnithread if installed in
$prefix/lib/pkgconfig; otherwise revert back to
--enable-omnithread
--with-gnuradio-coreUse package gnuradio-core if installed in
I'm trying to do a build of all the pieces separately, to mimic what
pkgsrc would do. Here's my script, which seems to build omnithread N
times. I'm a bit tired so may be overlooking something obvious:
The bug seems to be that I'm not specifying where omnithread comes from
during the core
14 matches
Mail list logo
