On Fri, Nov 18, 2005 at 10:20:46PM -0500, Michael Dickens wrote:
> On Mon, 12 Sep 2005 20:18:35 -0700, Eric Blossom wrote:
> >All of these are solvable, and it would be great to have some OS/X
> >hackers help out on this. I have a good idea of the general strategy
> >to make the fast USB stuff wor
On Fri, Nov 18, 2005 at 09:12:04PM -0500, Chuck Swiger wrote:
> At 02:21 PM 11/18/2005 -0800, you wrote:
>
> >One of the changes altered how we deal with the history mechanism.
> >This is mostly transparent, but filters now get a zero initialized
> >delay line, and produce N outputs when N inputs
Jon - Do I take it that you're compiling from source, not using Fink
or DarwinPorts (DP)? If that's the case, mucho respect for you ... I
tried that and gave up on wxPython - just never got the correct
configurations to make things work.
USRP should compile without issue once you've gotten
At 02:21 PM 11/18/2005 -0800, you wrote:
I've recently checked in a bunch of changes, some of which were to
gr_block.h, which everything depends on.
One of the changes altered how we deal with the history mechanism.
This is mostly transparent, but filters now get a zero initialized
delay line,
On Sat, Nov 19, 2005 at 11:02:24AM +1030, Berndt Josef Wulf wrote:
> On Sat, 19 Nov 2005 09:45, Eric Blossom wrote:
> > On Sat, Nov 19, 2005 at 10:39:17AM +1030, Berndt Josef Wulf wrote:
> > > > Regarding 2.6: I still need to clean up the boost autoconf code and
> > > > confirm that "make distchec
On Sat, 19 Nov 2005 09:45, Eric Blossom wrote:
> On Sat, Nov 19, 2005 at 10:39:17AM +1030, Berndt Josef Wulf wrote:
> > > Regarding 2.6: I still need to clean up the boost autoconf code and
> > > confirm that "make distcheck" works on our favorite platforms. Other
> > > than that, we're good to g
On Sat, 19 Nov 2005 10:39, Berndt Josef Wulf wrote:
> > Regarding 2.6: I still need to clean up the boost autoconf code and
> > confirm that "make distcheck" works on our favorite platforms. Other
> > than that, we're good to go.
>
> I'm now getting following error message when attempting to run
On Sat, Nov 19, 2005 at 10:39:17AM +1030, Berndt Josef Wulf wrote:
> > Regarding 2.6: I still need to clean up the boost autoconf code and
> > confirm that "make distcheck" works on our favorite platforms. Other
> > than that, we're good to go.
>
> I'm now getting following error message when at
On Sat, 19 Nov 2005 08:51, Eric Blossom wrote:
> Hi folks,
>
> I've recently checked in a bunch of changes, some of which were to
> gr_block.h, which everything depends on.
>
> As a result, if you are tracking CVS, you will need to update and
> rebuild *everything*.
>
> One of the changes altered h
Hi folks,
I've recently checked in a bunch of changes, some of which were to
gr_block.h, which everything depends on.
As a result, if you are tracking CVS, you will need to update and
rebuild *everything*.
One of the changes altered how we deal with the history mechanism.
This is mostly transpar
I, too, am running Gnu Radio on Mac OS X Tiger. I've got versions of all
the gr-wxgui programs working, but it took a few tweaks and code changes.
These have been described in my earlier messages to discuss-gnuradio, but
I'm just now trying the new versions of scopesink and fftsink, so maybe m
Quoting Matt Ettus ([EMAIL PROTECTED]):
> Joshua Lackey wrote:
> > We should keep the code there. FSK is used enough that someone will
> > eventually fix it to use the new clock recovery method. Perhaps just
> > put a comment in the source saying something like "don't use this unless
> > you fix
I'm a grad student at Notre Dame working on software defined radio
projects. My current task is to get GNU Radio and the USRP hardware
working under MacOS X 10.4. I thought I'd write to see if anyone
ever got it to "work", and if so, what tricks were used beyond those
already in the Wiki.
On Fri, Nov 18, 2005 at 11:21:56AM -0500, [EMAIL PROTECTED] wrote:
>
> On Thu, 17 Nov 2005 15:41:15 -0800, Eric Blossom [EMAIL PROTECTED]
>
> > The new code is much cleaner and faster, and since it tracks symbol
> > timing, works for long packets.
>
> > As Bob pointed out, the so called GMSK rec
On Fri, Nov 18, 2005 at 05:04:51PM +0530, Arora_Amit wrote:
>
> Hi,
>
> we are workin on GNU-Radio.
> we have installed gnuradio-core, but while running howto_qa.py example in
> gr-how-to-write-a-signal-processing block, we are having the below mentioned
> error.
> kindly help us.
>
>
> [EMAI
Hi,
I made the change but I get the following error when
I run usrp_oscope.py.
.
.
.
File
"/usr/local/lib/python2.3/site-packages/gnuradio/usrp1.py",
line 27, in _swig_getattr
raise AttributeError,name
AttributeError: set_dc_offset_cl_enable
Regards
Sudhindra
--- "[EMAIL PROTECTED]"
<[EMAI
On Thu, 17 Nov 2005 15:41:15 -0800, Eric Blossom [EMAIL PROTECTED]
>>On Thu, Nov 17, 2005 at 04:16:55PM -0500, [EMAIL PROTECTED]
wrote:
>> I am also in the process of studying this part of the software to see if
I
>> can use it to recreate my data from the demodulated signal.
> Let me start by
I have been able to view square waves down to 1 KHz with the usrp_oscope.
I do not use a daughterboard and I turned off the automatic DC offset. I
input the signal into pins 62 and 60 of connector J666, of the USRP, with
the use of appropriate coupling capacitor. I disabled the automatic DC
offs
Title: Import error : No module named howto
Hi,
we are workin on GNU-Radio.
we have installed gnuradio-core, but while running howto_qa.py example in gr-how-to-write-a-signal-processing block, we are having the below mentioned error.
kindly help us.
[EMAIL PROTECTED] python]# ./qa_howto.p
19 matches
Mail list logo
