Import error using an OOT
I have created an OOT which when I incorporate it in my flowgraph shows the
following error:
Failed to evaluate import expression ‘import ft8’
The yaml file is:
id: ft8_run_response
label: ft8
category: '[ft8]'
templates:
imports: import ft8
make: ft8.run_response(${ft8_button})
callbacks:
- set_ft8(${ft8_button})
# Make one 'parameters' list entry for every parameter you want settable from
the GUI.
# Keys include:
# * id (makes the value accessible as keyname, e.g. in the make entry)
# * label (label shown in the GUI)
# * dtype (e.g. int, float, complex, byte, short, xxx_vector, ...)
# * default
parameters:
- id: ft8_button
label: ft8_button
dtype: raw
default: 0
# 'file_format' specifies the version of the GRC yml format used in the file
# and should usually not be changed.
file_format: 1
I have developed and used an OOT before without an issue. I looked at the
previous OOT and reviewed the GNU Radio docs on OOTs without seeing anything
different.
I am using Python 3.92 with GNU radio 3.9.4.0 on a Raspberry Pi.
I hope someone can show me the error of my ways.
Jim
--
This email has been checked for viruses by AVG antivirus software.
www.avg.com
Re: Import error using an OOT
Hi Elmore - type
apt list | grep python3-pygccxml
and see if it's version 1.x.
If it's not installed, then
apt install python3-pygccxml
will install it.
Version 1.x only works with python code - it may be all you need.
If you need version 2, then it's easy to upgrade the system from
bullseye to bookworm.
-- Cinaed
On 12/9/22 18:33, Elmore's wrote:
I have created an OOT which when I incorporate it in my flowgraph
shows the following error:
Failed to evaluate import expression ‘import ft8’
The yaml file is:
id: ft8_run_response
label: ft8
category: '[ft8]'
templates:
imports: import ft8
make: ft8.run_response(${ft8_button})
callbacks:
- set_ft8(${ft8_button})
# Make one 'parameters' list entry for every parameter you want
settable from the GUI.
# Keys include:
# * id (makes the value accessible as keyname, e.g. in the make entry)
# * label (label shown in the GUI)
# * dtype (e.g. int, float, complex, byte, short, xxx_vector, ...)
# * default
parameters:
- id: ft8_button
label: ft8_button
dtype: raw
default: 0
# 'file_format' specifies the version of the GRC yml format used in
the file
# and should usually not be changed.
file_format: 1
I have developed and used an OOT before without an issue. I looked at
the previous OOT and reviewed the GNU Radio docs on OOTs without
seeing anything different.
I am using Python 3.92 with GNU radio 3.9.4.0 on a Raspberry Pi.
I hope someone can show me the error of my ways.
Jim
Virus-free.www.avg.com
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Σχετ: Re: Σχετ: Re: Pluto sink power issues
Hello,A workaround that seems to work is to amplify signal before feeding to Pluto sink by a factor of 20-25.Best regards Στάλθηκε από το Ταχυδρομείο Yahoo σε Android Στις Τρί, 22 Νοε, 2022 στις 0:14, ο χρήστηςCinaed Simson έγραψε:Hi George - it may be a bug which may have been fixed in May of this year. See https://github.com/gnuradio/gnuradio/pull/5860 gr-iio: fix grc pluto sink attenuation callback #5860 merged in 3.10 on May 19, 2022. They may be able to help you. -- Cinaed On 11/20/22 21:24, George Katsimaglis wrote: Hello again, I have not seen any reaction yet. Is this a bug or a misconfiguration of me? Best regards George SV1BDS Στάλθηκε από το Ταχυδρομείο Yahoo σε Android Στις Τετ, 16 Νοε, 2022 στις 15:59, ο χρήστηςGeorge Katsimaglis έγραψε:Hello, Via desktop environment, not by hand. Best regards Στάλθηκε από το Ταχυδρομείο Yahoo σε Android Στις Τετ, 16 Νοε, 2022 στις 14:59, ο χρήστηςMarcus Müller έγραψε:It looks like your call to set_attenuation() is missing the channel argument. Now, this could be a bug on the GNU Radio end or your end: How did that PlutoIMD.py get created? Best, Marcus On 16.11.22 12:08, George Katsimaglis wrote: > > Hello, > > I have two issues about Pluto sink attenuation (Tx power) for 3.10.1.1. > In previous versions with attenuation 0 it produces about 0 dBm output for a single > frequency output. > Now it gives about -22 dBm. > Also when I try to change attenuation from 0 to 1 using a QT range : > > File "/usr/lib/python3/dist-packages/gnuradio/qtgui/range.py", line 240, in changed > self.notifyChanged(self.rangeType(value)) > File "/usr/lib/python3/dist-packages/gnuradio/qtgui/range.py", line 316, in counterChanged > self.notifyChanged(self.rangeType(value)) > File "/home/sv1bds/Documents/GNURadio/PlutoIMD.py", line 125, in set_txatten > self.iio_pluto_sink_0.set_attenuation(self.txatten) > TypeError: set_attenuation(): incompatible function arguments. The following argument > types are supported: > 1. (self: gnuradio.iio.iio_python.fmcomms2_sink_fc32, chan: int, attenuation: float) > -> None > > Invoked with: , 1.0 > > is displayed and attenuation does not change > > George SV1BDS >
