On 05/26/2011 09:14 PM, Brett L. Trotter wrote:
On 05/26/2011 08:06 PM, Nick Foster wrote:
On Thu, 2011-05-26 at 19:29 -0500, Brett L. Trotter wrote:
USRP1:
- When we have a very simple flowgraph with a USRP1 sink connected to a
signal source and a USRP1 source connected to a WX scope- trying
So after discovering that while I had libusb-devel-0.1 and
libusb1-devel-1.0.3 installed on my RHEL-6 machine here (and ubuntu),
gnuradio compiled against 0.1 despite 0.1 being ancient and
unsupported. I then removed libusb-devel and gnuradio fails to configure.
[root@aurora gnuradio]# ls -lad
Hi, i have trouble with FM demodulators in the gnuradio companion libraries.
Why the baseband modulated signal has sometimes some phase change?
Do the blocks work well?
Thanks!
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
Hello Alex,
What documentation was possible to find? Was this part of it:
http://gnuradio.org/redmine/wiki/gnuradio/TutorialsWritePythonApplications#Controlling-flow-graphs
In this document disconnect is not mentioned at all.
Your example and another example from the mailing list helped me to
I did some more research on the topic to get some ideas.
Now it seems there are two possibilities to send control signals
between the blocks:
1. Use a message queue and a watcher thread like in the digital example pkt.py
2. Use a probe block like gr.probe_avg_mag_sqrd and an endless while
loop
So after discovering that while I had libusb-devel-0.1 and
libusb1-devel-1.0.3 installed on my RHEL-6 machine here (and ubuntu),
gnuradio compiled against 0.1 despite 0.1 being ancient and
unsupported. I then removed libusb-devel and gnuradio fails to configure.
I believe that Gnu Radio
Hi,
The way I do it is with infinite while loop, and a state machine. Once I
get to certain state, I lock the top-block and reconfigure it.
This works well during testing. Once you get some kind of protocol or
some series of steps that you want to do, you can just test a flag, and
whenever
I have never seen any issues regarding libusb and gnuradio.
GNURadio compliled using F9-14 without any probs (no uhd)
Mostlikely your machine is faulty?
Patrik
- Original Message -
From: Marcus D. Leech mle...@ripnet.com
To: discuss-gnuradio@gnu.org
Sent: Friday, May 27, 2011 14:41
Hi Scott,
This works well during testing. Once you get some kind of protocol or some
series of steps that you want to do, you can just test a flag, and whenever
your block finishes set it to true, then reconfigure.
What do you mean with your block finishes ? How do you implement this flags?
I am getting this error:
fusb: (rd status -2) No such file or directory
What does it mean and what can I do to solve this.
Crazy thing is it doesn't happen every time I call my rx script.
I tried to pull usrp power plug and usb plug but it did not help.
Johannes
So you have to reach some state that makes you want to reconfigure, e.g.
you finished scanning some particular band or some time limit is
reached. Whenever you reach the point that you want to reconfigure, set
a flag, then check for the flag in your main application.
My typical program flow
I made a simple example to show how it happens.
It is a problem of lock/unlock in combination with usrp.
Like this the lock unlock disconnect seems to absolutely unusable :(
-
#!/usr/bin/env python
from gnuradio import gr
from gnuradio import usrp
from time
On Fri, May 27, 2011 at 1:08 AM, Brett L. Trotter br...@webtrotter.com wrote:
So after discovering that while I had libusb-devel-0.1 and
libusb1-devel-1.0.3 installed on my RHEL-6 machine here (and ubuntu),
gnuradio compiled against 0.1 despite 0.1 being ancient and
unsupported. I then removed
nick@smidgen:~/Desktop$ geany wat.pl
nick@smidgen:~/Desktop$ chmod u+x wat.pl
nick@smidgen:~/Desktop$ ./wat.pl
start
lock
unlock
reconfigured
now stopping
stopped
nick@smidgen:~/Desktop$
The gr-usrp component has been around, and essentially unchanged, for
some years now, and it's been used
On Fri, May 27, 2011 at 7:28 AM, Johannes Schmitz jsem...@gmx.de wrote:
I am getting this error:
fusb: (rd status -2) No such file or directory
What does it mean and what can I do to solve this.
Crazy thing is it doesn't happen every time I call my rx script.
I tried to pull usrp power plug
We are running Ubuntu 10.10, I can not look up the kernel version
because I am at home right now but it should be 2.6.35-28.
Do you need further details?
Johannes
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
This is precisely the problem I'm seeing that kills my USB. I have to
ctrl+c to keep that from happening.
On 05/27/2011 12:05 PM, Johannes Schmitz wrote:
I made a simple example to show how it happens.
It is a problem of lock/unlock in combination with usrp.
Like this the lock unlock
The issue isn't duration- its when the flowgraph shuts down- as the
other thread from someone else is experiencing- it seems to be when the
flowgraph calls lock()/unlock() and stop(). It also only occurs on
bi-directional flowgraphs. But I do agree that there's an improper
shutdown- though I
Marcus-
Alexander is asking excellent questions and I'm surprised at the tepid
response -- he's got like 4 replies so far? He's the prototype GNU
radio user who needs to maintain his group's IP, he should be
receiving how to's, not INALs. -Jeff
Actually, IANAL is a perfectly-valid response.
On Fri, May 27, 2011 at 2:31 PM, Jeff Brower jbro...@signalogic.com wrote:
Marcus-
Alexander is asking excellent questions and I'm surprised at the tepid
response -- he's got like 4 replies so far? He's the prototype GNU
radio user who needs to maintain his group's IP, he should be
receiving
How do the companies write closed-source drivers for the Linux Kernel
without running into GPL2 issues? I can only recall that there is a
user-land and a kernel-land driver, where the kernel-land is the
only part that is open source. Is this correct?
Perhaps that method could work well?
I
Dear all,
I have been trying using the usrp_sounder.py script for measuring the
channel impulse response (CIR), but without success.
Q: - Have anyone succeeded? Does the FPGA-based script work as advertised?
Here is what I got:
Firstly, making a loopback test worked great
usrp_sounder.py -g
Isn't the main difference between v2 and v3 the Tivo Exception as
the call it? Not sure.
I guess I should add IANAL. TINLA.
:P
On Fri, May 27, 2011 at 3:32 PM, Marcus D. Leech mle...@ripnet.com wrote:
How do the companies write closed-source drivers for the Linux Kernel
without running into
Hi All,
Recently, I've gone down the road of timing synchronization and ended
up learning basics for PLLs and such. So far in GNURadio, it seems
that the loop filters used in the existing GNURadio synch blocks are
only first order. From what I understand, increasing the filter order
of the PLL
Colby-
How do the companies write closed-source drivers for the Linux Kernel
without running into GPL2 issues? I can only recall that there is a
user-land and a kernel-land driver, where the kernel-land is the
only part that is open source. Is this correct?
Perhaps that method could work
25 matches
Mail list logo
