discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU Radio (Companion) bug


From: Volker Schroer
Subject: Re: GNU Radio (Companion) bug
Date: Tue, 4 May 2021 10:49:04 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1

As 'm just working on the feature/gr-iio branch, I used this branch for
testing your grc file.
But I think this does not concern grc.


I can load your flowgraph and make changes to your sampe_rate_chooser
block. Everything works fine. If I disable your dvbtx.... block and
enable OFDM symbol I can generate your flowgraph.

But if run this flowgraph I get

AttributeError: module 'osmosdr' has no attribute 'ALL_MBOARDS'

but this may depend on my Osmocom implementation.

-- Volker



Am 03.05.21 um 21:07 schrieb Ralf Gorholt:
Dear all,

I have spent several hours before my PC trying to get my new OOT block
running, but in vain. Now I have got the impression that one of my
problems is due to a bug in GNU Radio (Companion). I have attached a
working graph (using Qt GUI) to this email. I am not used to report bugs
but in the wiki I have read that I should send an email to this list.

The problem is, that in certain cases when I change the value of a
parameter in a combo box, GRC displays a message telling me that ports
are disconnected although they are not.

This behaviour can easily reproduced. In GRC, load the attached flow
graph and open the properties window of a block that has a combo box.
Then, change a parameter and click the "Apply" button. The value in the
block changes. Then change the value back. As soon as you select the
item in the combo box, a message is displayed telling you that the ports
are not connected and no more changes are accepted, even when you click
on "Apply".

I have verified this with GNU Radio version 3.8.2.0 on Linux (Python
3.8.5) and 3.8.0.0 on Windows (Python 2.7.10). GNU Radio 3.9 (checked on
Windows) does not show this behaviour but if I remember correctly, not
everything has been ported to version 3.9 yet and for this reason I
would like to keep version 3.8. Would it be possible to fix this bug
also in version 3.8?

Thank you very much for your help.

Kind regards,

Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]