Re: GNU Radio (Companion) bug
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
Re: GNU Radio (Companion) bug
The error I'm seeing has something to do with gui hints. If no gui hint is give, there is no error. On Mon, May 3, 2021 at 4:42 PM Jeff Long wrote: > Using GNU Radio 3.8.3.0 on Linux, I do not see anything about disconnected > ports. But, there is a rather ugly error message that comes up about > comparing NoneType vs int. No ideas at the moment. > > You may also add an issue to https://github.com/gnuradio/gnuradio/issues, > where it will be tracked. > > On Mon, May 3, 2021 at 3:10 PM Ralf Gorholt wrote: > >> 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 >> >
Re: GNU Radio (Companion) bug
Hi I made a partial test: removed the osmosdr source (I don't have installed gr-osmoSDR at present) and replaced it with a dummy.dat file/file source removed the missing block dvbtx_ofdm_sym_acquisition (my be this is your OOT block ?) the flowgraph runs, and I'm able to change block parameters before running and at runtime (bandwidth, ...). It looks like the error come from your OOT block On 03/05/2021 21:07, Ralf Gorholt wrote: 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
Re: GNU Radio (Companion) bug
Using GNU Radio 3.8.3.0 on Linux, I do not see anything about disconnected ports. But, there is a rather ugly error message that comes up about comparing NoneType vs int. No ideas at the moment. You may also add an issue to https://github.com/gnuradio/gnuradio/issues, where it will be tracked. On Mon, May 3, 2021 at 3:10 PM Ralf Gorholt wrote: > 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 >
GNU Radio (Companion) bug
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
options:
parameters:
author: Laurent F4FDW
category: '[GRC Hier Blocks]'
cmake_opt: ''
comment: ''
copyright: ''
description: Flow Graph de reception DVB-T 1 MHz de BW sur 70cm avec un
stick
RTL-SDR
gen_cmake: 'On'
gen_linking: dynamic
generate_options: qt_gui
hier_block_src_path: '.:'
id: dvbt_rx_udp
max_nouts: '0'
output_language: python
placement: (0,0)
qt_qss_theme: ''
realtime_scheduling: ''
run: 'True'
run_command: '{python} -u {filename}'
run_options: prompt
sizing_mode: fixed
thread_safe_setters: ''
title: RX DVB-T en low BW sur 70cm
window_size: ''
states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [16, 16.0]
rotation: 0
state: enabled
blocks:
- name: center_freq
id: variable
parameters:
comment: ''
value: ui_center_freq
states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [328, 564.0]
rotation: 0
state: enabled
- name: freq_corr_ppm
id: variable
parameters:
comment: ''
value: ui_freq_corr_ppm
states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [208, 564.0]
rotation: 0
state: enabled
- name: if_gain_db
id: variable
parameters:
comment: ''
value: ui_if_gain_db
states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [528, 564.0]
rotation: 0
state: enabled
- name: rf_gain_db
id: variable
parameters:
comment: ''
value: ui_rf_gain_db
states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [432, 564.0]
rotation: 0
state: enabled
- name: samp_rate
id: variable
parameters:
comment: ''
value: (25 * 8) / 7
states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [856, 564.0]
rotation: 0
state: disabled
- name: samp_rate_chooser_0
id: variable_qtgui_chooser
parameters:
comment: ''
gui_hint: 4,0,1,1
label: Bandwidth
label0: 200khz
label1: 250khz
label2: 1Mhz
label3: 2MHz
label4: ''
labels: '[]'
num_opts: '4'
option0: '228571'
option1: '285714'
option2: '1142857'
option3: '2285714'
option4: ''
options: '[0, 1, 2]'
orient: Qt.QHBoxLayout
type: real
value: '1142857'
widget: radio_buttons
states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [16, 408.0]
rotation: 0
state: true
- name: ui_center_freq
id: variable_qtgui_range
parameters:
comment: ''
gui_hint: 2, 0,1,1
label: center freq.
min_len: '0'
orient: Qt.Horizontal
rangeType: int
start: '43000'
step: '1000'
stop: '44000'
value: '43400'
widget: counter
states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [352, 20.0]
rotation: 0
state: enabled
- name: ui_freq_corr_ppm
id: variable_qtgui_range
parameters:
comment: ''
gui_hint: 2, 1,1,1
label: Freq. ppm
min_len: '0'
orient: Qt.Horizontal
rangeType: int
start: '-100'
step: '1'
stop: '100'
value: '11'
widget: counter
states:
bus_sink: false
bus_source: false
bus_structure: null
coordinate: [216, 20.0]
rotation: 0
state: enabled
- name: ui_if_gain_db
id: variable_qtgui_range
parameters:
comment: ''
gui_hint: 1, 1,1,1
label: IF gain
min_len: '0'
orient: Qt.Horizontal
ran
