I'm working on a module in C++ and when a condition happens I want my
work function to signal to the flowgraph to stop.
I saw some references for python to self._top_block but does anyone
have a suggestion on how to do it in C++?
Thanks!
___
Hi,
are you talking about building in-tree modules or OOTs?
On 04/28/2017 11:13 PM, Michael Dickens wrote:
> Hi Eugene - What you write looks to be true about the current GR
> codebase. Bastian Bloessl has a commit that adds in LOG4CPP_INCLUDE_DIR
> & related to those in-tree areas that need it
Hi Eugene - What you write looks to be true about the current GR
codebase. Bastian Bloessl has a commit that adds in LOG4CPP_INCLUDE_DIR
& related to those in-tree areas that need it (branch "ugly_cmake"): <
https://github.com/bastibl/gnuradio/commit/16d8e8cb9bd658991dabbc253c74850248b80f83
>. I
That's fine for low rate stuff, but for Mehmeto's application, he probably
needs to be more coherent. Correlating on a preamble would be a good idea,
I think.
On Fri, Apr 28, 2017 at 9:04 AM Vitt Benv wrote:
> Hi Mehmeto,
> in my opinion and in my experience with LEO sats,
The current GR CMakeFile(s) apparently do not add the include path
LOG4CPP_INCLUDE_DIR to the compile. Can't build w/ log4cpp in non-standard
location.
Eugene Grayver, Ph.D.
Aerospace Corp., Sr. Eng. Spec.
Tel: 310.336.1274
Hi.
I am trying to simulate an image transfer flowgraph in gnu radio.Here is
the link to the GRC file:
https://github.com/sagniknitr/my_GNURadio/tree/master/image%20transfer
The problem is I am always getting 0 bytes in the jpeg file mentioned in
the file sink block.What am I doing wrong here?
This was fixed a while ago. Use VOLK version 1.2.3 or 1.3.
On Fri, Apr 28, 2017 at 8:34 AM, katutxakurra wrote:
> Hi,
> I'm trying to compile gr-burst and I'm getting an error. I've opened an
> issue in Github but I'm hoping to get a wider audience here.
>
Thanks Marucs for pointing it out. Hadn't noticed. Will do.
Hey Ghost,
um, could you please not take the list into CC when replying to github
issue discussions? It's pretty confusing.
Best regards,
Marcus
___
Discuss-gnuradio mailing list
Hey Ghost,
um, could you please not take the list into CC when replying to github
issue discussions? It's pretty confusing.
Best regards,
Marcus
On 28.04.2017 16:07, GhostOp14 wrote:
> I was just looking at that tutorial for something else. May take me a
> couple weeks to dig into it but
I was just looking at that tutorial for something else. May take me a
couple weeks to dig into it but I'll tackle that one next and see what I
can do with it.
-- Forwarded message --
From: sdrgpu
Date: Fri, Apr 28, 2017 at 9:51 AM
Subject: Re:
Hi everyone, been a busy week on OOT modules. While working on some
other signal decodes I made a number of enhancements in the CorrectIQ
OOT module. First, doing some testing I was seeing inconsistencies in
the plotted waveforms due to inheriting from "block" instead of
sync_block so that was
I can definitely take a look at it. Is it the block that comes up as
"Polyphase Clock Sync" in the block search?
-- Forwarded message --
From: sdrgpu
Date: Fri, Apr 28, 2017 at 8:28 AM
Subject: [ghostop14/gr-clenabled] PFB Clock Recovery Block (#1)
To:
Hi Mehmeto,
in my opinion and in my experience with LEO sats, it's usefull to retune
the receiver using doppler correction info coming from external app.
In the past I used to query old beloved Predict via socket to control a
ICOM PR1000 receiver with a little utility that I wrote ( google
Hi Vamsi - it looks like you're not linking with Volk directly; indirect
linking (via one of the GR libraries) doesn't work. Check out any of the
various OOT modules that do that linking for specifics. - MLD
On Fri, Apr 28, 2017 at 12:12 AM, vamsi krishna wrote:
>
> I get the following error when
Hi,I'm trying to compile gr-burst and I'm getting an error. I've opened an
issue in Github but I'm hoping to get a wider audience
here.https://github.com/gr-vt/gr-burst
I'm using Ubuntu 16.04 with GNURadio 3.7.9, Volk 1.2.1, SWIG 3.0.8 and libgsl2
2.1.
I have installed python-bitarray and
If you want to change the default size you can look in
/usr/local/etc/gnuradio/conf.d/grc.conf and change the line
`canvas_default_size = 1280, 1024`. The path might be different on your
system. You can run `find / -name grc.conf 2>/dev/null` to hunt it down.
On Fri, Apr 28, 2017 at 5:05 AM,
Dear All,
I have a situation where I need to demodulate a wide bandwidth signal (70
Mbps QPSK modulated, having 35 MHz IF bandwidth and sampled at 105 MSPS ) in
our lab. However, the signal generator will also add some amount of doppler
shift at a rate of 1 kHz/s. Which PSK demodulation blocks
Hello,
I am having some communication reliability problems with
'benchmark_tx/rx.py' files. I came to know that these files are outdated
and one should use 'ofdm_txrx.py' instead. As 'ofdm_txrx.py' uses sync
words unlike benchmark files (or modules connected to
'benchmark_tx/rx.py'), I hope it
In the „Options“ Block, there is a parameter named „Canvas Size“. Enter
there WIDTH, HEIGHT, e.g. "1280, 1024“.
Regards,
Sebastian Müller
gse...@gmail.com
Am 28. April 2017 um 08:56:42, Fernando (ferna...@samara.com.es) schrieb:
Is it possible to change the "sheet size" in GRC?
I'm working on
Hi All,
First of all: I'm a newbee
I'm into the example of gr-digital: rx_ofdm.grc and tx_ofdm.gr.
I have 2 Questions:
1. My goal is to check the time between 2 recieved packets. I realized that
the TAG_DEBUG-Block outputs some rx_Time.
Offset: 1035 Source: n/a Key: rx_time Value: {2523
Is it possible to change the "sheet size" in GRC?
I'm working on a big diagram and it does not fit well.
regards
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
21 matches
Mail list logo