discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: Pluto sink power issues


From: Marcus Müller
Subject: Re: Pluto sink power issues
Date: Wed, 16 Nov 2022 13:58:03 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.1

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: <gnuradio.iio.iio_python.fmcomms2_sink_fc32 object at 
0x7f93d09f29f0>, 1.0

is displayed and attenuation does not change

George SV1BDS

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


reply via email to

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