Thanks, Marcus. Of course it will not throw now after about 20+ attempts.
(Does that smell like mis-aligned memory?).
The display is still not showing the data traces until at run time I change
the FFT size.
I will continue playing with it until it gets back into the mode where it
throws all the
This may be related to https://github.com/gnuradio/gnuradio/issues/2407
Best regards
Christoph
On Fri, Apr 26, 2019 at 6:42 PM Marcus Müller (GNU Radio maintainer)
wrote:
>
> Hi Tom,
>
> shoot, that sounds like we half-fixed a bug :(
> How proficient are you with GDB? Could you get a backtrace?
Hi Tom,
shoot, that sounds like we half-fixed a bug :(
How proficient are you with GDB? Could you get a backtrace? (maybe
based on [1]?)
Thank you!
Marcus
[1] https://wiki.gnuradio.org/index.php/TutorialsGDB
On Fri, 2019-04-26 at 09:25 -0700, Tom McDermott wrote:
>
> I've had this problem inter
I've had this problem intermittently for about a year. On starting the
flowgraph it will terminate
with QT Throw : Bad Alloc. Building different versions from about 3.7.10
ish to 3.7.latest will change
whether or not it happens 100% of the time or 30% of the time.
Today, I noticed that disablin
Instead of a UChar to Float block, you want to use a Chunks to Symbols
block (with 1, 3, -1, -3 in the Symbol Table and Dimension = 1).
Ron
On 4/26/19 06:46, Batu Kaplan wrote:
Dear Marcus,
Thanks for your response. First of all, it is been a while
for answering your response and I am sorry
Dear Marcus,
Thanks for your response. First of all, it is been a while for answering
your response and I am sorry about that. I could not try your solution
until these days. Unfortunately, I still couldn't get over my problem on
M-FSK modulation. When I try your solution, "bits to symbols and aft
Hello Kyeong,
Thanks for the info; I will check more. It seems that some hardware
modifications are required.
Regards
On Fri, Apr 26, 2019, 06:01 Kyeong Su Shin wrote:
> Hello YENDstudio,
>
> I know that USRP 1 can take two RF daughterboards, but the effective
> sampling rate of the device in
Hi,
You can use two (or more) copy blocks and have a variable enable or
disable each one. If a copy block is disabled then non of the blocks
after it will be run.
Regards,
Derek
On 26/04/2019 01:48, H.W wrote:
Thanks for your reply.
I have got the warning too.
I will find another way to do
N. Benes:
> what is the accepted best practice to have a source and a sink block
> share a common resource?
> In my case, the shared resource is a thread that does I/O and both
> source/sink use it to interface to GNU Radio.
[snip]
> Is there a commonly accepted pattern to apply in this situation
