t;> Running until enter is pressed: my_sink: work: 32768
>>> my_sink: work: 32767
>>> my_sink: work: 32768
>>> my_sink: work: 32767
>>> my_sink: work: 32768
>>> my_sink: work: 32767
>>> my_sink: work: 32768
>>> my_sink: work: 32767
>>
I can't get dynamic reconfiguration to work when my flow graph has a
sync_block implemented in Python. If I lock() and then disconnect() and
connect() other blocks, my program always hangs on the unlock(). It won't
even stop when I hit ctrl-c. Superficial debugging shows that a thread is
stuck o
Quoting Philip Balister (phi...@balister.org):
[...]
> >Alternatively, you can force the use of Posix shared memory and see if
> >that works for kalibrate on your platform. (The easiest thing to do
> >would be to look for D_HOST_OSX and make sure those #ifdef's are the
> >ones that gets compiled.)
Quoting Philip Balister (phi...@balister.org):
> >On Wed, Oct 20, 2010 at 01:02:15PM -0400, Philip Balister wrote:
> >>On 10/19/2010 10:51 PM, Eric Blossom wrote:
> >>OK, it looks like x86 sets SHMLBA to PAGE_SIZE and arm uses 4 *
> >>PAGE_SIZE. Need to puzzle through this a little more. This is th
Kalibrate is a program I wrote that scans GSM frequency bands and looks
for base stations. It also caculates the offset between your local
oscillator and a GSM base station's oscillator. (Kalibrate was
originally just designed to calculate the oscillator offset. It's just
convenient for kal to a
Quoting George Nychis (gnyc...@cmu.edu):
[...]
> It would be great to get Eric S's code merged in to git somewhere
> which fixes the timestamp jump and then move the code in to a
> mainstream location.
What very interesting timing. (Ugh, pun not intended.)
Last night at about 11PM I was
Kalibrate, or kal, is a program I wrote to help calibrate external
clocks for the USRP. This version will also scan the GSM bands looking
for base stations in your area.
This latest version is much more accurate than previous versions. I
urge anyone using kal to upgrade.
I'd also like to thank
And leveraging the work from the osmocombb project
(http://bb.osmocom.org/trac/) will get you a far ways towards the goal.
Quoting John Gilmore (g...@toad.com):
> > Dear All,
> >
> > Do we think it is possible to create a software mobile phone using the
> > USRP, with the OpenBTS code or somet
is use.
> My first thought is that my computer is to slow to manage the packets sent on
> the USB.
> I will try to test it on new computer and let you know once done.
> But if someone knows the problem, pelase help me.
> Thks
> Sylvain
>
> --- On Tue, 11/3/09, Joshua
Sylvain,
Truthfully, that project is very old and I'm not surprised that you're
having issues with it. I only keep the page up for reference purposes.
I recommend you check out the airprobe project.
( https://svn.berlin.ccc.de/projects/airprobe .) This project is being
actively supported and sh
Back in 2007 there was a discussion about using the newer RFX (mimo B)
boards with a Rev3 USRP.
It's pretty clear that the below applies to Rev2 boards as well but I
thought I would ask before I fire-up the old soldering iron.
Thanks!
On Wed, 07 Feb 2007 17:27:18 -0800 Matt Ettus wrote:
> All R
(Moving discuss-gnuradio to bcc.)
You can tell when it's working because of all the error messages you
get.
[EMAIL PROTECTED]:~/src/gsm/gssm-v0.1/src/python$ ./file_gssm.py
~/src/gsm/signal/signal.data
>>> gr_fir_fff: using SSE
error: PCH, AGCH (0, 36)
error: SAC
GSM Scanner Project, http://wiki.thc.org.
--
Joshua Lackey, Ph.D. ([EMAIL PROTECTED])
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
scuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
can think of is kinda obvious. You realize that 0x65
is side B, right? Do you have something on side B? (If not, slap self
on forehead and then try the constant 0x67.)
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
___
Discuss-gnuradio mailing list
D
capacitor, programmed to be an RFX1800
nothing gets through, burns out tx amplifier.
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
s getting nothing when it
> wants something (e.g. when 'sync'ing on incoming symbols and no
> packet found); (2) sending exactly the packet data, not truncated,
> between block modules.
>
> Any advice, thoughts, comments? Has anyone done this?
cuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
eply. Unfortunately, the code already takes care
> of using a 64k granularity. Could it be some bigger granularity
> is needed?
>
> --
> Stephane
>
> On Thu, Jan 12, 2006 at 05:05:50PM -0800, Joshua Lackey wrote:
> > I don't have the GNU Radio code in front of
e
> familiar with Windows support forums be keen to ask why MapViewOfFileEx
> does not work as expected, and what alternative we have?
>
> --
> Stephane
>
>
>
>
> _______
> Discuss-gnuradio mailing list
> Discuss-gnuradio
Haha. Nevermind.
I had: '%include "gnuradio.i"' rather than '%import "gnuradio.i"' in my
.i file...
Makes a big difference. :)
Quoting Joshua Lackey ([EMAIL PROTECTED]):
> I'm not sure if this is common but I'm trying to track this down
oscope things in my module. (Moreover
these things do not appear in howto.py.)
It won't be much work for me to re-construct my project to (try and) fix
this, but I'm hoping that it is just some obvious argument somewhere
that I'm mi
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
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 it first"?
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
___
Discuss-gnuradio mailing
Quoting LRK ([EMAIL PROTECTED]):
[...]
>
> Start reading up on Argentina folks. It's your future.
>
What about New Zealand?
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED], [EMAIL PROTECTED]
___
Discuss-gnuradio mailing list
Discuss-gn
help with the noise.
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
elect number of bits per symbol.
o Should be able to select mapping between bits and symbol.
(E.g., can do 8PSK or pi/4-QPSK depending on option you
select.)
I should probably create a wiki page to discuss this as well.
Josh
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
__
)
done
--- 29,37
(
cd $dir
aclocal -I config
libtoolize --automake
automake --add-missing
+ autoconf
+ autoheader
)
done
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
ile.in
> failure always in the gsm vocoder directory. On those directories,
> if I went into the directory and did touch configure.ac and then
> used ../buildit, it always worked! Single exception: gr-usrp.
> There I had to do touch configure.ac and ../buildit 3 times and
> then it fina
a stuff.
>
> Good luck,
>
> Ilia Mirkin
> [EMAIL PROTECTED]
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
errors on both of them. I'm afraid
I've got some sort of hardware problem but I'm not exactly sure where to
go from here. I thought I would post for some ideas and then sleep on
it.
Thanks!
Josh.
--
Joshua Lackey, PhD. -- [EMAIL PROTECTED]
_
31 matches
Mail list logo
