Hi,
> (Bipolar: a signal swings between +A volts (or amperes) and -A volts;
> Ethernet, USB, Wi-Fi, ... are using bipolar signals,
> Unipolar: a signal swings between +A volts and 0 volts)
There is no difference ... "0 volt" is just an arbitrary reference point.
0 <-> +A swing is the same as
-A/
Hello,
well after a lot of digging in the mailing list I added this into my swig.i
file:
%include "gnuradio/blocks/file_sink_base.h"
and I also added this into my CMakeLists.txt:
set(GR_REQUIRED_COMPONENTS BLOCKS)
It turned out that only first change is required.
Best and hope that this will
Hi all (again),
is there any way to catch that my flowgraph has finished execution, to
reconfigure it after that and to be able to watch signals in GUI?
In my application I I would like to set some start and end values and to
press some kind of start button. After that flowgraph runs for the firs
Hi Nemanja,
typically, clicking your "start" button would spawn a new thread, in
which you top_block.start(), .stop() and .wait(); after wait returns,
you would then use whatever multithreading framework you're using to
notify the threads that need to know.
GNU Radio is not very callback-oriented,
Is there a tutorial module installed to
/usr/local/lib/python2.7/dist-packages?
M
On 04.05.2015 20:57, Peter Mathys wrote:
> I have downloaded the most recent version of the gr-tutorial from github
> and installed it using
> cd gr-tutorial
> mkdir build
> cd build
> cmake ..
> make
> sudo make ins
I had a similar problem recently. My solution was to subclass the
flowgraph adding the required functionality. Check out the
_top_block_waiter class in top_block.py. You can reimplement that logic
to e.g. add a time-out the the wait() call on the event or have a
callback executed.
Sebastian
On 0
Hi,
Thank you very much for the help! Now it works, for some reason the
solution to the first problem also solved the second or something else did.
Best regards,
Carl
On 3 May 2015 at 23:03, Richard Bell wrote:
> Add that source command to your .bashrc file which is located in your home
> dir
No sorry It doesn't work yet.. I have a HackRF, and before I reinstalled
gnuradio I found out that if I use an Osmocom source I get an error saying
no supported device found. But if I started gnuradio with the command “sudo
gnuradio-companion” then it all worked. However now when I do “sudo
gnuradi
While I have been talking around it for a while, I wanted to better
publicize our work on GNU Radio for Android. We can now build applications
that run GNU Radio flowgraphs on Android (>= 5.0). We build the flowgraph
in C++ and link it through to a Java app for the user interface using the
JNI. I h
Hi Guys,
Thanks for the help. I can build the kernel and run it on a Zedboard using the
dizzy branch exclusively. The additional step of using the
zynq-gnuradio-manifest repo to try to include the FIR example is what broke
things. That repo manifest replaces the meta-xilinx layer with an older
Looking inside gnuradio,I've found blocks like divide_XX where relative
files have an extension .t (like divide_XX_impl.cc.t )..in this way,is
possible to manage different types for the same block.
How is posssible to create blocks like them? is necessary to use particular
parameters in gr_modtools
I did actually find a tutorial.py file in /gr-tutorial/python (I
expected it to be there yesterday, but must have overlooked it) and
copied it to /usr/local/lib/python2.7/dist-packages. Now the error
message that I get is
ImportError: No module named _tutorial_swig
If I search for _tutorial_s
Hi Marco,
.t is for template, and at build time, the full implementations of these
blocks are generated, and then compiled.
gr_modtool doesn't support that. However, the magic involved is not
really of the overly complex kind:
* CMake writes a python program to do the substitutions
* In the CMake
13 matches
Mail list logo